Senior Backend Engineer

Requirements:

• 4+ years building production backend systems in Python, with depth in FastAPI, Django REST Framework, or Flask.
• Strong PostgreSQL skills. You design schemas that don't need migrating in 12 months, write efficient queries, understand indexing, and can reason about transactions and locking. You don't need to be a DBA-level expert; you do need to be the engineer who never gets called for a "this query is killing prod" page.
• Multi-tenant SaaS architecture. You have shipped a product where multiple customer organizations share infrastructure, but their data must never leak across boundaries. You understand row-level isolation, request-scoped tenancy, and the failure modes.
• Auth and RBAC patterns. You have implemented production auth flows (OAuth, OIDC, NextAuth, JWT, and session management) and role-based access control. You can describe specific decisions you made and why.
• REST or GraphQL API design. You have OpenAPI specs you're proud of. You understand versioning, idempotency, pagination, and rate limiting.
• Payment/subscription integration. Razorpay, Stripe, or equivalent: you've integrated billing, handled webhooks, designed for retry safety, and dealt with edge cases (failed payments, refunds, and plan changes mid-cycle).
• AWS proficiency. S3 SES, IAM, RDS, and secrets management. You can reason about cost.
• Pragmatic API instincts. You ship the endpoint that solves the product problem cleanly, not the perfect REST-purity one. You also know when to push back on PM specs that would create technical debt.

Strongly preferred:

• Prior 01 or early-stage startup experience. You have built the API layer for a product from launch through the first 10K users; you know what breaks in that journey.
• Indian compliance / DPDPA / equivalent regulated-domain experience (fintech, healthtech, govtech). Or strong instincts for data residency and privacy by design.
• Background job / async processing experience. Celery, RQ, or equivalent. PDF generation, exports, and notifications all live on async workers.
• Working knowledge of agentic / LLM-based systems. You don't need to build them, but understanding long-running tasks, streaming responses, and idempotency for LLM calls helps design the right API surface.