Quickeee — Junior Backend Support Engineer
Mumbai | 1–2 years | Full-time
About the role
Quickeee runs live 60-minute delivery operations in Mumbai — real orders, real riders, real warehouse sync. When something breaks — a stuck order, a failed webhook, a delayed rider ETA — ops and category teams need answers fast, and right now that falls on senior engineers. We're hiring someone to own the first line of that response: read the logs, find what went wrong, fix what you can, and flag clearly what needs a senior.
This is not a feature-shipping role to start. It's a find the problem before it becomes everyone's problem role — and it's the fastest way to learn how a real production system actually behaves under load.
What you'll do
- Investigate operational issues flagged by ops and category teams — stuck orders, failed payments, sync mismatches
- Read application logs (CloudWatch) and trace an issue back to its source across the stack
- Run basic database queries to verify what actually happened to a specific order or record
- Fix straightforward bugs independently; escalate complex ones with a clear writeup of what you checked
- Support minor feature work and bug fixes on the NestJS backend and Flutter app under a senior's guidance
- Learn our deployment pipeline (AWS ECS, CI/CD) well enough to check deployment status and basic service health
What you need
- 1–2 years of professional engineering experience
- Working knowledge of JavaScript/TypeScript; some exposure to Node.js or NestJS
- Comfortable reading logs and forming a hypothesis — you don't panic when something is broken and you don't have the full picture yet
- Basic SQL — can write a SELECT with joins and filters to verify data without being told the exact query
- Genuine curiosity about why something failed, not just whether you fixed the symptom
Good to have
- Exposure to Docker, AWS, or any cloud deployment process
- Some Flutter or React experience
- Any exposure to monitoring/observability tools (CloudWatch, Datadog, or similar)
This role is not for you if
- You want to write greenfield features from day one with no production exposure
- You get uncomfortable when a problem doesn't have a clear answer yet
- You're looking for a pure DevOps or pure backend-development role — this is investigative work first
How to apply
Send your resume to [Confidential Information] with a short answer: describe a time you had to debug something with incomplete information. What did you check first, and how did you narrow it down
