Qualification and Experience
- 4‒7 years of backend engineering experience with Node.js as your primary runtime
- Demonstrated experience owning backend features or services end-to-end, not just
contributing to them
- Experience working in product-driven or startup environments with evolving requirements
- Familiarity with API design as a discipline — understanding what makes an API goodto build
on, not just functional
- 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 — service decomposition, inter
service communication (REST or gRPC), and managing the operational complexity that
comes with distributed systems
- Exposure to GraphQL or Backend for Frontend(BFF)patterns
- Experience with feature flags, A/B testing infrastructure, or gradual rollout systems
- Understanding of mobile API consumption patterns —what makes an API genuinely good to
work with from a Flutter or React Native client
Technical Skills
- Strong proficiency in Node.js with production-grade TypeScript experience
- Solid experience with a Node.js framework (NestJS or Express) in a product environment
- Strong understanding of RESTful API design, versioning, and documentation (OpenAPI / Swagger)
- Hands-on experience with relational databases (PostgreSQL or MySQL) and caching layers (Redis)
- Experience with message queuing or event-driven systems (RabbitMQ, Kafka, or equivalent)
- Practical experience with containerization and deployment (Docker, Kubernetes, or cloud managed services)
- Working knowledge of observability practices: structured logging, metrics, and alerting
Engineering Collaboration Skills
- Ability to design API contracts collaboratively with mobile and frontend engineers before implementation begins
- Strong written communication —your technical decisions should be legible to both Product and Engineering
- Comfort raising technical concerns early, not after a feature has been built the wrong way
- Ability to work across team boundaries without needing to be directed at every step
- Self-directed: able to assess scope, flag risks, and make implementation decisions independently
a Necessity, not a Luxury