Engineering Head
SuperLiving is a Series A consumer-AI company building a personalized wellness ecosystem for Indian families, and we've grown into a real multi-system product. A Flutter app on iOS and Android, a Node.js backend for auth, payments and entitlements, a Python AI backend running every coach, course and memory system, a set of admin dashboards, and an API gateway tying it all together.
Each of these moves fast on its own. What we need now is one person who makes them move fast together.
This is not a keep-the-lights-on role, and it's not a pure people-management role. This is the person who takes ownership of the entire engineering system and is accountable for how fast it ships, how reliably it runs, and how well every part of it stays in sync.
What you'll own
The whole stack, end to end. You are the single owner of engineering across every vertical:
- Flutter app - one codebase, both platforms, the whole mobile experience
- Node.js backend - auth and login flows, payments, entitlements
- Python AI backend - the AI layer including chat, courses, skills, memory, the async worker fleet
- Admin dashboards & internal tools - the surfaces the rest of the company runs on
- API gateway & infrastructure - the edge, the routing, the cloud underneath
Making the verticals move as one. The hard part isn't any single system, it's the seams between them. You set the sprint cadence, run prioritization across teams, and make sure frontend, backend and AI ship in lockstep instead of blocking each other. When Product and Growth want three things at once, you're the one who sequences them so the whole org moves, not just one team.
Product ↔ engineering as a partnership. You sit between the founders, Product and Growth and turn "what we want" into "what we're building this sprint," with honest trade-offs on speed vs. long-term health. You protect velocity without letting the platform rot.
The numbers that actually matter.
You don't manage engineering by vibes. You watch and drive
- Payment success rate across gateways (Razorpay / PhonePe / Juspay), and you know why an SR drop is a rail problem vs. a code problem
- Login / auth conversion - the mobile sign-in funnel is a metric you own, not a black box
- Infra health - latency, error rates, cost per service, and where the money is being spent
- Security & compliance - attack surface, alerts, and the discipline to keep them tight
- Growth instrumentation - the Meta and Google Ads events the app fires, and the Mixpanel pipelines Growth and Analytics depend on being correct
Alerting and reliability as a habit. You keep the alerts meaningful, the on-call sane, and the team responding to real signal, not drowning in noise or missing the one that mattered.
An AI-native engineering org.
We build with AI coding tools (Claude/Codex) as a part of how we work, and with a shared, version-controlled knowledge base that keeps every repo and every engineer working from the same source of truth. You champion that, you keep context synced across teams (our "ops-sync" discipline, Obsidian + Claude workflows, per-repo context), so a new engineer, a new repo, or a hand off between verticals doesn't lose the thread. Getting more leverage per engineer out of AI is part of the job, not a side experiment.
Who you'll work with
- Founders - direct, daily, high-trust
- Product - to ship fast without mortgaging the platform
- Growth - to support rapid experimentation and keep the event/attribution data honest
- Analytics - to make sure tracking and pipelines are robust enough to mak
What we're looking for
- Real experience owning engineering across multiple systems at once - mobile, backend and infra, not deep in one and blind to the rest
- A track record building and scaling consumer products/apps that real users pay for
- Genuine breadth: comfortable reasoning about a Flutter build, a payment CT, and a cost/latency graph in the same afternoon
- Hands-on with payment gateway integrations (Razorpay / PhonePe / Juspay or similar) and what makes success rates move
- Solid grip on mobile login/auth flows, cloud infrastructure, and observability
- Fluency in product analytics and growth instrumentation - Mixpanel, ad-platform event tracking, and how to tell whether an experiment actually worked
- You hire, structure and lead engineers, and you run a real sprint process accross teams
- AI-native by default - you already build with tools like Claude Code and want to push how far an org can get with them
- High-ownership, founder-mindset operator who is comfortable setting direction from first principles on imperfect systems
What this role is not
- Not a "keep the lights on" engineering head
- Not a pure people-manager who's lost touch with the systems
- Not a specialist who only understands one vertical
- Not someone who over-architects and slows the product down
We need someone who can ship fast, scale responsibly, keep every vertical in sync, and think 2–3 years ahead while executing today.
This role is hosted on the company's careers site.