This is a backend-leaning fullstack role with real ownership attached. You'll own a backend service or a product surface end to end, handed outcomes rather than tickets — the scoping, the design decisions and the trade-offs are yours to make and defend. You're responsible for how your systems behave in production, not just for merging your pull request. As the team grows, the patterns you set in the code you own become the patterns other engineers follow.
Location: Bangalore · Experience: 2-5 years · Type: Full-time
What you'll do
- Own one or more backend services end to end — design, implementation, deployment, monitoring and on-call.
- Take ambiguous problem statements and break them into a sequence of changes, each of which is independently safe to deploy.
- Make and document technical decisions around data modelling, API design, caching, background processing and observability.
- Build the full stack of the features you own, including a frontend you'd be happy to put in front of a designer.
- Carry the pager for what you build: investigate incidents, fix root causes, and write the postmortem.
- Improve the reliability, latency and infrastructure cost of the systems you own — query optimisation, indexing, retries, backpressure, the unglamorous work that keeps things standing.
- Partner closely with product and design, and push back with alternatives when you think the plan is wrong.
What we're looking for
- 2–5 years of experience building and operating production backend systems.
- Strong in at least one backend language, and able to work across the stack without waiting for a frontend specialist.
- Solid grasp of relational databases — schema design, indexing, query performance — plus practical experience with queues, caching and asynchronous processing.
- A track record of making technical trade-offs and explaining them clearly, in design docs and pull requests as well as in conversation.
- Real attention to user experience: you notice when a flow has one step too many, and you fix it rather than filing it.
- Fluent with AI coding tools, and thoughtful about where they help, where they reliably fail, and how review and testing have to change to keep up.