Backend Engineer (Python/TypeScript) - Bengaluru
- Compensation
- Not disclosed
- Location
- Bengaluru, Karnātaka, India
- Work setup
- Onsite
- Seniority
- Not specified
- Employment
- Not specified
- Experience
- 4+ years
- Category
- Backend
- Posted
Skills
Must have
- 4 to 6 years in backend and distributed systems, including real architecture ownership.
- You've designed systems that stayed correct and affordable under scale and concurrency.
- Deep judgment on data modelling, consistency, isolation, and failure modes.
- You've made a fast-growing team better through standards, review, and mentorship.
- Calm with ambiguity; you bring order to it.
Nice to have
- Worked on agentic/AI systems, event-sourced architectures, or high-stakes transactional systems.
- Tamed a runaway cost or reliability problem in a complex system.
- Opinions on where automated systems need hard limits and human confirmation.
Full description
Design the system a household bets its day on.
Company Details
At M, we’re early, ambitious, and moving fast. We’re building a new category in how urban households function. We help households run smoothly through trained professionals, operational excellence, and technology-driven support systems. Backed by Peak XV Partners, Blume Ventures and CRED, we’re reimagining how homes run, so people never have to think about chores again.
Website:
The Role
Design the system a household bets its day on.
M is agentic software in production, and agentic systems are unforgiving: a loop that doesn't converge burns money, a weak boundary corrupts a tenant's data, a slow write makes a household wait. As we scale, you'll take over architecture ownership and set the foundations: the boundaries, the safety, the scale, the standards.
Requirements
- 4 to 6 years in backend and distributed systems, including real architecture ownership.
- You've designed systems that stayed correct and affordable under scale and concurrency.
- Deep judgment on data modelling, consistency, isolation, and failure modes.
- You've made a fast-growing team better through standards, review, and mentorship.
- Calm with ambiguity; you bring order to it.
Bonus Qualifications
- Worked on agentic/AI systems, event-sourced architectures, or high-stakes transactional systems.
- Tamed a runaway cost or reliability problem in a complex system.
- Opinions on where automated systems need hard limits and human confirmation.
Responsibilities
- Own backend architecture as the team and product scale several-fold.
- Design the boundaries and safety that keep autonomous, AI-driven systems correct, bounded, and affordable.
- Get multi-tenant isolation, reliability, and performance right.
- Make the hard design and build-vs-buy calls, and write the standards the team builds against.
- Raise the bar through review and mentorship.
30 / 60 / 90-Day Expectations
- 30 days: you've absorbed the architecture, found the sharpest risks, and are already shaping decisions.
- 60 days: you own architecture for core systems and have led a foundational design the team is building on.
- 90 days: you're the architecture owner, standards, boundaries, and the bar are set by you.