Get a reply from this employer
Your resume and cover letter, tailored to exactly what they’re hiring for.
Massive Mobility Pvt. Ltd. in Gurugram is seeking a hands-on, AI-native Head of Software Engineering to own all software, decide what to build, and lead a small team.
The role focuses on reliability of a live charging platform with thousands of chargers and payments. You will write code, review others, and shape releases and incident response. Experience: 7–10 years in software, strong backend, data modelling and cloud infrastructure, and comfort with AI-assisted coding.
Massive Mobility is one of India’s leading electric mobility startups, building the infrastructure that powers the country’s clean transport revolution.
We run 3,000+ EV chargers across North India for e-autos, e-rickshaws, delivery two-wheelers and cars. Every session runs on software we built ourselves: our charging management system (CMS), driver app, wallet, billing and partner dashboards. Our CMS also powers other operators’ networks.
We’re looking for a hands-on, AI-native Head of Software Engineering to own all of our software: what gets built, what gets cut, how it is released, and what happens when it breaks.
The software is live and has grown faster than the team behind it. The challenge is reliability, not scale: chargers on mobile networks drop, reconnect and resend, and every rupee still has to match a session. You will write code, review code and lead a small team that already knows the system well.
Experience: 7–10 years
Location: Gurugram (work from office, full-time)
Reporting to: Founder & CEO
Charging Platform
The CMS and its OCPP 1.6J connections to thousands of chargers from several hardware makers, plus OCPI links with partner networks.
Uptime, session success rate and data integrity are yours.
Money
UPI payments, wallet and passes, refunds, holds, and settlement with franchisees and partners.
Every rupee in should reconcile to a session.
The driver app (Android and iOS), fleet operator dashboards, and white-label CMS deployments for partner operators.
Monitoring & Support Tooling
Remote monitoring, alerting and the ticket system, so a failed session is caught by us, routed to an owner and closed.
Releases, code review, on-call, incident write-ups, access control and documentation, so no system depends on one person.
Set how the team builds with AI: tools, review rules, testing, and where AI-written code never merges without human review.
Roadmap & Team
Decide which products we double down on, merge or stop. You bring the case; the CEO decides with you.
Lead the current engineers, raise their bar, and run hiring for the next ones.
Own the protocol boundary with our hardware team (charger hardware and firmware sit with them).
By day 30: every live system, its owner and its failure modes are mapped. You run releases and on-call, the team works with AI coding tools under written guardrails, and every production incident gets a written root cause.
By day 60: session failures and payment reconciliation are on a live dashboard. Every customer issue reaches a named owner with a deadline.
By day 90: a written 12-month product and technology plan, including what we stop building. At least one key hire is in process.
7–10 years in software, including designing a production system end to end, running it, and leading at least 3 engineers through real incidents.
Built and ran a backend with long-lived connections (WebSockets, MQTT or similar) to thousands of devices or clients that drop, reconnect and resend, and kept the data correct through it.
Owned a system where money or billing had to reconcile exactly.
Strong in backend engineering, data modelling and cloud infrastructure; able to read a mobile codebase.
Still write code every week, and can show us something you built recently.
AI-native: ship production code daily with agentic coding tools (Claude Code, Cursor or similar), have redesigned how a team writes, reviews and tests code with AI, and know where it fails, especially in payment and billing code.
Think small team, big output: you would rather make five engineers do the work of fifteen than hire fifteen.
Make calls with incomplete information, write them down, and change them when the data says so. Can say no to the CEO, with reasons.
Short application → Online assessment → Technical round → Assignment & defence → Founder round → Paid work trial. We check references independently, so every claim in your application should be one we can verify.