Page 1 of 1

Full-Stack Generalist - Integrations

Full-Stack Generalist - Integrations

Location & Work Schedule
Location: Indiranagar, Bangalore
Work Arrangement: Full-time, Work From Office

About M
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.

The Role
Build the agent that buys, pays, and talks in the real world.
This is where M's AI stops advising and starts acting: placing real orders, moving real money, and messaging real people and vendors, on its own. Almost no one has built agents that actually transact in the messy real world and stay safe doing it. That's the frontier and it's shipping here.

What you'll do
- Own an integration surface end to end - the code and the counterparties: build it, keep it alive, make it reliable against systems you don't control.
- Give M's agent a safe, dependable way to act in the real world - buy, pay, or message - not just suggest.
- Work directly with the platforms, payment providers, and telecom partners.
- Reverse-engineer and adapt when a platform changes without telling you.
- Build the guardrails that make autonomous actions - especially money - safe by design.

What We're Looking For
- 3-6 years full-stack; comfortable anywhere in the stack and owning a system on your own.
- You enjoy integrating and reverse-engineering external systems - APIs, automation, the undocumented parts.
- You own outcomes, not tickets.
- Pragmatic and reliability-minded: you build things that keep working unattended.
- Strong debugging instincts for flaky, real-world failures.

Bonus Qualifications
- Worked on payments, automation/scraping, or telecom/messaging.
- Fought bot detection or anti-automation and won.
- Built with LLM agents or tool-calling.

30 / 60 / 90-Day Expectations
- 30 days: you own your sub-track's surface and have shipped fixes and features.
- 60 days: M's agent acts through your integration measurably more reliably, with guardrails.
- 90 days: your surface is dependable enough that the rest of the team stops worrying about it.

Experience

What is your core skill area?

How many years have you spent as a full-stack engineer owning a system end-to-end (not just tickets on one), and what's an integration you built against an external API/platform you didn't control?

Describe a specific integration that broke because a third-party platform changed something without telling you — how did you detect it, and what did you do to fix it and prevent it from silently breaking again?

Tell us about a time you had to make an autonomous or unattended action safe — money, an order, a message sent on someone's behalf. What could have gone wrong, and what guardrail did you build so it couldn't (or so it failed safely)?

Show us the most interesting thing you've built outside of work — a side project, a scraper, an automation, a hack, anything. Link or describe it, and tell us why it mattered to you.

Are you comfortable owning outcomes with external counterparties (platforms, payment providers, telecom partners) — chasing them down, escalating, and following up until something is actually live?

Candidate Details

Name

Email

Phone Number

How soon can you join us?

Current CTC

Expected CTC

This is a strict 5-day work-from-office role. Is that a work style you genuinely enjoy?

A
B

Drop Your Resume

Your LinkedIn Profile