Senior Backend Engineer (3+ years exp)

Stack: Node.js (TypeScript) · PostgreSQL · Prisma · Redis · BullMQ · Razorpay · FCM · GitHub Actions · AWS

Experience : Minimum 3 years
Positions : 2
Budget : 6-18 LPA

We're building a quick-commerce startup in NCR focused on delivering construction and building materials to active sites within 60 minutes. Think Blinkit for builders and contractors — electricals, cement, paint, plumbing, hardware — delivered fast. We're pre-launch, moving quickly, and looking for the right people to build this right.
We're hiring our first dedicated backend engineer. Everything server-side is yours to own and build from scratch.

What you'll own

• Core APIs for multi-hub inventory management, order lifecycle, vendor procurement, purchase orders, and financial reconciliation
• Inventory consistency under concurrent orders — reservation locking, oversell prevention, stock ledger accuracy across multiple fulfilment hubs
• Payment integrations: Razorpay (UPI, card, COD, webhooks, settlements, refunds), OTP + SMS + WhatsApp (MSG91), push notifications (FCM)
• Full DevOps setup — CI/CD, staging + production environments, secrets management, deployments
• Observability: structured logging, error monitoring, uptime alerting, performance tracking
• Database design, indexing strategy, query optimization, backup and recovery
• Background job infrastructure: async processing, retry logic, dead-letter queues (BullMQ + Redis)
• GST invoice generation, vendor payout scheduling, COD reconciliation

What we're looking for

• 4–5+ years backend experience on a transactional system — e-commerce, logistics, fintech, or quick-commerce
• Strong Node.js in TypeScript — clean, typed, production-grade code
• PostgreSQL depth — relational modelling, transactions, row-level locking, indexing, query performance. Not a MongoDB CRUD role.
• Redis — caching, session management, rate limiting, pub/sub
• DevOps ownership — you've set up CI/CD, managed cloud infra (AWS / GCP / Railway), and don't need a separate DevOps person
• Payment gateway integration experience — idempotency, webhook reliability, failure handling
• Background job systems — BullMQ, Bull, Agenda, or equivalent
• Comfortable owning API contracts directly with a frontend engineer — no handoff ambiguity

What this is not

• Not a team of 20 with a DevOps engineer and a DBA doing the hard parts around you
• Not a maintenance role — you're building greenfield from day one
• Not for someone who needs specs handed down — you'll work directly with the technical founder on architecture decisions