By Wave 1, HypeHaus has consumer iOS + god-web admin + Cartel iOS + careers-web + status-web + Hype Pass + Razorpay Route + Cartel SaaS. Backend complexity grows fast. This role scales infrastructure, ships features, and maintains quality past founder's solo capacity. Hands-on, owns features end-to-end.
02OUTCOMES · FIRST 12 MONTHS- Take ownership of the v1 API surface — auth, list management, payments, partner economics, content
- Ship the Cartel vendor SaaS billing flow (Razorpay subscription + Postgres migration + Next.js route + its tests)
- Wire payments end-to-end across consumer + partner — settlement, refund flow, reconciliation, observability
- Scale infrastructure for 5K → 500K MAU without rewrites — schema, indexes, caching, function regions
- Build the observability stack — structured logs, metrics, alerts — so we know what breaks before guests do
- Author the internal engineering docs every future backend hire reads on day one
- 5–9 years shipping production backend — TypeScript on Node.js, Postgres in production
- Strong Postgres — you've written and shipped migrations that touched live tables, with a rollback
- Payments experience — Razorpay, Stripe, or equivalent — settlement flows, not just checkout
- Comfortable owning the entire backend stack solo for the first version
- AI-first development workflow comfort (Cursor + Claude Code) — every line of code is debt
- Operator mindset — you ship, you measure, you iterate
- Founder-friendly (close collaboration with Aditya, no political games)
- Async-first remote — fast in writing, fast in code review, slow in meetings
- Quality bar matches the founder: production from day one, no half-finished implementations
DAY 30- Onboard onto the existing backend, Razorpay account, and Vercel project
- Ship the first meaningful feature end-to-end — schema → API → tests → deploy
- Pair with founder on architecture decisions for the next 6 months of roadmap
DAY 60- Own the payments flow — guest checkout, partner settlement, reconciliation — end-to-end
- First reliability/perf win shipped: query indexes, cache layer, or function region tuning
- Cartel SaaS billing flow live in staging with Razorpay subscriptions wired
DAY 90- Operating independently — founder no longer in critical path for backend decisions
- Observability stack live: structured logs + metrics + alerts in production
- Engineering doc set drafted — schema reference, deploy runbook, on-call playbook
- Zero production incidents caused by your code in the first 60 days
ROUND 1 · INTRO CALL · 45 MINBackground, why HypeHaus, prior production ownership, compensation framing.
ROUND 2 · CODE SESSION · 90 MIN SYNCLive coding — design a Cartel vendor SaaS billing flow (Razorpay subscription + Postgres migration + Next.js route + its tests). Founder evaluates trade-off reasoning.
ROUND 3 · ARCHITECTURE · 60 MINScale design discussion for 5K → 500K MAU. Schema design, partitioning, observability, deploy topology.
ROUND 4 · REFERENCE + FINAL · 45 MIN + 2 REFS2 tech-lead references from prior production work. 90-day expectations check-in alignment.
- Take meaningful feature ownership within 30 days
- Zero production incidents caused by your code in first 60 days
- Operate independently by day 90
- AI-first development workflow (Cursor + Claude Code comfort)
Compensation discussed in first call after match.
Engineering hires bypass the contract phase — direct full-time. 90-day expectations check-in instead of contract trial.
PROCESS3 rounds over 2–3 weeks: intro call with founder, craft session (role-specific), final with founder + reference check.
RESPONSEWe respond to every application within 5 business days.
REMOTE INDIA · ASYNC-FIRSTRemote India, async-first. We expect deep written communication, clean async hand-offs, and quarterly Nagpur onsites (company covers travel + stay).