Senior Backend Engineer

Primary responsibilities

• Own core services in the hiring platform — the application lifecycle, interview scheduling, offers, and the event flow that connects them
• Design the data model for multi-tenant workloads where isolation is a correctness property, not a configuration option
• Build the asynchronous machinery properly: exactly-once semantics where they matter, idempotent consumers, and reconciliation that can prove the ledger of applications is complete
• Lead schema migrations on live tables, including the backfill strategy and the rollback that has to exist before the deploy
• Set the API contract with the frontend and with integration partners, and own versioning and deprecation
• Diagnose production incidents from traces and query plans, and write the postmortem so the next person does not repeat it
• Raise the bar in review — on failure modes, on data integrity, and on what happens when the third-party call times out

Skills required

Day to day this role works with Node.js, PostgreSQL, Redis and API Design.

• Five or more years on backend systems, including schema design you still stand behind
• Practical experience with queues, idempotency and the failure modes of both
• Able to reason about a slow query from the plan, not from guesswork
• Five or more years on backend systems, including design you own the consequences of
• Deep relational database experience — schema design, query planning, and migrations on live tables
• Distributed systems fundamentals: consistency models, partial failure and what a retry actually means
• Queue and event infrastructure in production, with the exactly-once conversation you have already had
• API contract ownership across teams, including versioning and deprecation
• Production debugging from traces, metrics and plans rather than from a hunch
• Ability to write a design document that resolves disagreement before code is written
• Mentoring — a material part of the job is other people's code being better

Preferred

None of these are required. They are the things that would help, and a strong application is regularly missing all of them.

• Node.js, PostgreSQL and Redis
• Multi-tenant SaaS with hard isolation requirements
• Financial or other domains where correctness is not negotiable
• Experience with data residency constraints across regions

Working in Engineering / IT / Software

Small teams that own a surface end to end, from the migration to what a candidate sees on a slow connection. Code review is expected to teach, not just approve. On-call exists and is compensated, and the rotation is built so nobody is woken twice in a week.

The individual contributor ladder runs to Principal and Distinguished without requiring anyone to become a manager. Moving into management is a lateral choice made deliberately, not a promotion you fall into.

About Pune

Pune hosts backend engineering, data and part of the trade operations team, alongside a share of supply-chain work.

A shorter commute and a lower cost of living than Mumbai, with the same access to the western trade corridor. Many people here work with teams in Bengaluru and Mumbai rather than only locally.