We are building systems that operate at scale - high write volumes, real-time state sync, and burst traffic that doesn’t politely warn before it arrives. We are looking for engineers who love owning systems end-to-end, care deeply about performance and reliability, and want to build things that don’t just work - but last. This is not a ticket-execution role, its a system ownership role.

Responsibilities:

• Backend System Ownership:

• Design and evolve Node.js / NestJS services powering systems that operate at scale

• Take architectural decisions that balance scale, cost, and long-term maintainability

• API Craftsmanship:

• Build well-typed, thoughtful REST contracts for high volume flows

• Think in versioning, backward compatibility, and clean boundaries

• Data at Scale:

• Model and optimize MongoDB / Firestore schemas for high read/write workloads

• Design atomic updates and consistency strategies for distributed systems

• Scalability & Resilience:

• Implement queues, caching layers, and rate limiting to handle burst traffic gracefully

• Design for failure modes before they happen

• Frontend Integration:

• Ship modular Vue 3 UIs that efficiently consume APIs

• Optimize realtime updates and state management (Pinia)

• Improve Core Web Vitals and perceived performance

• Observability & Production Ownership:

• Instrument logs, metrics, traces, and alerts

• Participate in on-call

• Debug real production issues

• Drive post-mortems to meaningful closure (not just documents)

• Mentorship & Leverage:

• Review code thoughtfully

• Support junior engineers

• Raise engineering standards across the team

Requirements:

• 4+ years of professional engineering experience
• Strong backend-heavy fullstack background
• Deep comfort with Node.js + TypeScript
• Experience building and scaling microservices (NestJS / Express)
• Modern frontend experience (Vue 3 or similar)
• Strong understanding of: API design, Data modeling, Distributed systems tradeoffs, Concurrency & rate limiting
• Real production debugging experience
• Comfortable in cloud-native environments (GCP / AWS)
• CI/CD and containerization familiarity

Nice to Have:

• Pub/Sub or message queue experience
• Event-driven systems exposure
• Domain-driven design familiarity
• Performance optimization work
• Experience reducing infra costs