You'll be one of the most experienced individual contributors on the engineering team. Expect to own end-to-end design and delivery of significant systems — infrastructure primitives (auth, billing, audit, multi-tenant data, queues) or partner integrations with insurance, fleet, and government APIs. You'll work closely with a Tech Lead but be expected to drive your own work, set up your own quality bar, and mentor mid-level engineers around you.
This is a hands-on senior role, not a manager role. Expect to write production code most days.
- Design and build high-leverage backend systems — API contracts, schemas, jobs, integration layers
- Own end-to-end delivery: scoping design doc implementation tests observability rollout on-call
- Be a force multiplier on code reviews — raise the bar, not just rubber-stamp
- Mentor 2–3 mid/junior engineers without being their manager
- Drive technical decisions in design reviews; push back when the design is wrong
- Carry a meaningful share of on-call and own postmortems for things you built
- Partner with product on what's worth building vs not — your judgment matters here
- Languages: TypeScript
- Backend: NestJS, Prisma
- Databases: PostgreSQL, MySQL, Redis
- Async / Jobs: BullMQ
- Infra: Coolify on GCP / AWS
- Observability: DataDog, Sentry
- APIs you'll touch: insurance (Bajaj Allianz, ALD), government e-challan endpoints, payment gateways, voice infra (LiveKit / Pipecat) where relevant
- 5–8 years of backend / full-stack engineering with strong production track record
- Strong TypeScript + Node.js; strong relational DB skills (indexing, query plans, schema design — you should be able to read an EXPLAIN output and know what to do)
- Has built and owned a real production system with paying users
- Comfortable with async / queue-based systems (BullMQ, SQS, Kafka — any)
- Writes design docs before code; thinks in terms of failure modes and SLAs
- Can debug a tricky production issue without panicking
- NestJS + Prisma specifically
- Integration-heavy work — webhooks, retries, idempotency, dead-letter queues
- Some exposure to AI / LLM systems
- Indian regulatory familiarity (GST, DPDP, e-challan, Pure Agent / Rule 33)
- 30 days — Onboarded; submitted a few PRs; have a working mental model of your domain
- 90 days — Owning a meaningful subsystem; one mid-level engineer is visibly better because of your reviews
- 6 months — You've shipped at least one significant new system end-to-end; you're the go-to person for it
- 12 months — Trusted for the hardest problems in your domain; clear path to staff / lead
Send CV + GitHub + a short note on why Lawyered to [email protected] with subject
[FY27] Senior SWE — Your Name . Bonus points for something we can play with.
