Get more replies from employers
Send a job-specific resume in minutes.
BookMyMentor is seeking a Senior Backend Engineer to design systems that are critical for B2B clients, emphasizing correctness, reliability, and security.
The ideal candidate will have 4-6 years in software development, possess a strong CS background, and be proficient in backend languages. Responsibilities include core service design, production debugging, and mentoring within the team. Join us to shape the future of our platform and client interactions.
Zenskar is building the operational backbone for how B2B companies run their business. As a Senior Backend Engineer, you will work on the hardest class of problems we have: systems where correctness is non‑negotiable, scale is unforgiving, and the edge cases never stop coming. This is not a feature‑factory role - you will design systems from first principles, make architectural calls that shape the platform for years, and push back when requirements are wrong. Design and build core platform services that handle complex business logic reliably at scale. Architect and own integrations with external enterprise systems - each with its own quirks, rate limits, and failure modes. Build APIs that enterprise engineering teams love integrating with, not just ones that technically work. Own production debugging end‑to‑end - diagnose issues across services using logs, traces, and metrics; make incidents boring, not fires. Work closely with product, implementation, and customer success - not as an order‑taker, but as the engineer who understands the system deeply enough to push back. Embed security and compliance thinking into your systems by default - not as a retrofit. Lead design reviews and code reviews, setting the architectural standard for your domain. Mentor engineers around you - raise the bar without slowing the team down.
Your systems will be the foundation that Zenskar’s enterprise clients depend on - correctness and reliability at this layer directly affects how they run their business. Architectural decisions you make now will define how the platform scales over the next several years. You will shorten the time from “new enterprise requirement” to “production‑ready system” - enabling the company to move faster without breaking things. You will raise the engineering quality bar for the team around you through the standards you set and the code you ship. You will work on problems that don’t have obvious solutions - and your judgment will determine the outcome.