Quickeee — Senior Backend Engineer
Mumbai / On Site | 4–5 years | Full-time
About Quickeee
Quickeee is India's first 60-minute fashion and sneakers delivery platform, live in Mumbai with real users and real orders. Our stack: NestJS + TypeScript, PostgreSQL, Redis, AWS ECS Fargate, Flutter. We integrate with Unicommerce, Pidge, and PayU in production.
Every line of code you write ships within days and directly impacts delivery SLA and revenue. No ticket queues. No waiting for approvals. You own it.
The role
We're hiring a Senior Backend Engineer who thinks before they code — someone who hears a problem and maps the full solution, edge cases, failure modes, and rollback strategy in their head before writing the first line. This is not a stability role. It is for someone who wants to own a live backend end-to-end and move fast.
What you must have
- 4–5 years of backend engineering experience, SDE2 level
- Strong Node.js fundamentals — event loop, async patterns, memory model, not just framework knowledge
- TypeScript proficiency — generics, utility types, discriminated unions; any is not in your vocabulary
- NestJS — modules, DI lifecycle, guards, interceptors, pipes; you can design a new bounded context from scratch
- PostgreSQL depth — you read EXPLAIN ANALYZE, you've fixed N+1 queries in production, you understand transactions and locking
- Redis — TTL strategy, cache invalidation, distributed locks, pub/sub
- Third-party integration experience — you've handled timeouts, duplicate webhooks, partial failures, and token expiry in production
- At least one real production incident you personally debugged and fixed end-to-end
Good to have
- Experience with AWS ECS, Fargate, or equivalent container deployments
- Distributed scheduler/cron design — multi-replica safety, advisory locks
- Zero-downtime migration patterns on live databases
- Structured logging, correlation IDs, CloudWatch or equivalent observability
What you will own
- Order management, inventory sync, and delivery pipeline
- Third-party integrations — WMS, last-mile delivery, payments
- Scheduler and background job infrastructure
- Database performance and migration safety
- API design for mobile and web frontend teams
This is not for you if
- You need fully scoped tickets before you can start thinking
- You've never been first responder on a production incident
- You're optimising for work-life balance over ownership and impact
- You've only worked on internal tools or greenfield projects with no real traffic
How to apply
Send your resume to [Confidential Information] with a 3–5 sentence answer to this question:
Tell us about a production incident you personally fixed. What broke, what was your first hypothesis, what did you check, and what was the actual root cause
No answer = no review. We read every response.
