Senior Backend Engineer (Distributed Systems) - Bengaluru
Summary
Senior backend engineer to own the architecture of M's agentic, multi-tenant household-operations platform in Bengaluru (work from office). Day to day: set system boundaries, safety, scale and standards so AI-driven distributed systems stay correct, reliable and affordable as the product grows.
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+ 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.
Job Details
Bengaluru, work from office.
Interview Process
Technical Discussion
System Design Round
Founder Discussion
Important Note
ClanX is a recruitment partner, helping TellM hire a Senior Backend Engineer.
Skills
As published by recruitee · 17 questions · 6 written answers
Basics
Full name, Email, CV, Phone
Short answers (3)
- Please share your current CTC breakup, including Fixed, Variable, ESOPs, and other components, if any. Please stick to this format: Fixed: 15L, Variable: 3L, ESOPs: 5L with 4-year vesting
- What is your expected annual CTC? (INR)
- Help us with your LinkedIn profile link
Pick from a list (8)
- How many years of experience do you have as a Backend Engineer?
- Are you willing to relocate to Bengaluru?
- What is your notice period? (We are looking for candidates who can join within 30 days)
- Is your notice period negotiable?
- Do you have experience working at a product-based company?
- Are you a citizen of India and currently based in India?
- What does your current or most recent company mainly do?
- What is your current annual CTC range? (INR)
Written answers (6)
- Tell us about the product or services your current or most recent company offers. In 2–3 sentences, explain what it does, who uses it, and share the company/product website.
- [Mandatory] Share a Loom video walking us through a product or feature you personally built. Explain the problem it solves, your contribution, the backend architecture, and the key technical tradeoffs you made and why. Make sure the link is accessible.
- Describe one system you worked on where concurrency or scale threatened correctness or cost. What was your approach, why did you choose it, and how did you verify the result? Explain the relevant data modelling, consistency, isolation, or failure-handling decisions.
- What makes your experience relevant to owning architecture at TellM? Share a specific example of architecture ownership and how you helped a growing team through standards, reviews, and mentorship.
- Why do you want to leave your current role?
- Where did you find this job opportunity? (e.g., LinkedIn, Twitter, WhatsApp, etc). If someone referred you, please mention their name and contact number so we can thank them. (Write NA if not applicable).