Page 1 of 1

Android Engineer

Android Engineer

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
Put M in every household's pocket. India runs on Android - across a thousand devices, price points, and network conditions. You'll build M's native Android app from scratch and make a real-time, AI-driven, conversational experience feel effortless.

What you'll do
- Build M's native Android app - daily-use, real-time, built to last.
- Make conversation feel instant: streaming replies, voice notes, well-timed notifications.
- Win on real-world Android - device sprawl, flaky networks, memory, battery.
- Own the craft bar: an app that feels fast and trustworthy on a budget phone.
- Ship for launch with Backend and Design, and shape the roadmap.

What We're Looking For
- 3-4 years building and shipping native Android apps (Kotlin) to the Play Store.
- You've fought and won the real-device, real-network battles.
- Comfortable with real-time data and messaging-style UIs.
- You own features end-to-end.

Bonus Qualifications
- Built chat, voice, or other real-time-heavy apps.
- Worked with AI or streaming responses on mobile.
- You treat performance on low-end devices as a feature, not an afterthought.

30 / 60 / 90-Day Expectations
- 30 days: shipping to production; multiple features merged.
- 60 days: you own a major slice of the app, and it's in customers' hands.
- 90 days: the craft bar and architecture in your area are yours.

Experience

How many years have you spent building and shipping native Android apps (Kotlin) to the Play Store, and what's the Play Store link to the most recent one you owned end-to-end?

Describe a specific bug or failure you hit on a low-end device or flaky network (memory pressure, ANRs, battery drain, poor connectivity) — what was broken, why, and how you fixed it?

Making an app feel fast and trustworthy on a ₹8,000 phone is a different problem than on a flagship. Tell us about a time you optimized specifically for a budget device or constrained network — what did you have to give up or rethink to make it feel good anyway?

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

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