Node Tech Lead

Position Responsibilities

• End-to-end technical ownership of the Node.js backend architecture: service design,

patterns, and long-term technical direction

• First technical review point for new product and feature requests — shaping what gets built

and how before implementation begins

• Definition and evolution of backend engineering standards: API design conventions, code

quality practices, testing approaches, and shared patterns

• Backend system health: reliability, latency, error rates, and the operational posture of

services under production load

• Cross-functional technical alignment with Product, Mobile, Frontend, QA, and DevOps
• Mentoring of backend engineers —raising the technical bar across the team, not just within

your own services

• Technical decision-making on service boundaries, data modelling, third-party integrations,

and infrastructure trade-offs

1.Required Technical Skills

• Deep production-grade expertise in Node.js with TypeScript — building, scaling, and

operating backend services

• Strong experience with Node.js frameworks (NestJS or Express) at product scale, not just in

side projects

• Proven ability to design RESTful APIs and event-driven systems that teams build on reliably

over time

• Strong hands-on experience with relational databases (PostgreSQL or MySQL) — schema

design, query optimization, and migrations under a live system

• Working knowledge of caching strategies and practical Redis experience
• Experience with message queuing or event-driven architecture (RabbitMQ, Kafka, or

equivalent)

• Practical experience with containerization and deployment (Docker, Kubernetes, or cloud

managed services)

• Strong awareness of observability: structured logging, metrics, distributed tracing, and

alerting at production scale

2.Required Leadership Skills

• Proven ability to drive technical alignment across Product, Mobile, Frontend, and QA without

relying on formal authority

• Experience mentoring backend engineers and raising team technical maturity — not just

reviewing PRs, but developing people's engineering judgment

• Ability to translate ambiguous product requirements into clear, actionable technical direction
• Comfort making architectural trade-offs under uncertainty and communicating the

reasoning clearly to non-technical stakeholders

• Track record of defining and maintaining backend engineering standards in a team

environment —establishing patterns others follow, not just following your own

• Outcome-driven mindset: success is the reliability, scalability, and developer experience of

the backend, not the elegance of the architecture in isolation

Qualification and Experience

• 7‒12+ years of backend engineering experience with Node.js as your primary runtime
• Demonstrated experience in a technical leadership role — Tech Lead, Principal Engineer, or

equivalent — where you set direction, not just delivered it

• Experience working in product-driven or startup environments where requirements evolve

and engineering constraints shift

• Track record of improving backend system quality: architecture decisions that held up,

services that scaled, and codebases that became easier to work in over time

• Experience building backend systems for high-transaction consumer applications (ordering,

payments, loyalty, or delivery)

• Background in F&B, logistics, or operational-heavy consumer businesses
• Hands-on experience designing or operating microservices at production scale — service

decomposition, inter-service communication (REST or gRPC), and managing the operational complexity of distributed systems

• Exposure to GraphQL or BackendforFrontend (BFF)patterns
• Experience with feature flags, A/B testing infrastructure, or gradual rollout systems at

product scale

• Understanding of mobile and webAPI consumption patterns—what makes a backend

genuinely good for high-frequency clients to build on

• Experience with platform or developer experience engineering: shared libraries, internal

tooling, or developer productivity initiatives

• Think about the backend as a platform other engineers depend on, not just a set of services

you happen to own

• Are uncomfortable watching the same classes of production problems recur —and

motivated to fix the root cause, not the instance

• Can have a direct conversation with Product about why a proposed feature needs more time

to build properly

• Take responsibility for what the backend team ships, even when you didn't write the code
• Want the Node.jsbackendtobesomethingengineersbuildonconfidentlyandproduct

teams rely on without second-guessing

a Necessity, not a Luxury