Senior Backend Engineer Mumbai · 4+ years · Full-time →

NyaayOS; Mumbai; On-site; INR 2,000,000 - 4,000,000; Full time

Job summary

NyaayOS in Mumbai invites a senior backend engineer to own the architecture and code of the product API and services layer, shaping how the platform scales, stays secure, and remains reliable under deadline.

You will design multi-tenant data models, ensure fast, cost-aware operations, and collaborate on authentication, billing, uploads, and notifications to support legal workflows.

Qualifications

• 4+ years of Python backend engineering experience.
• Experience with multi-tenant SaaS and data isolation.
• Strong API design and security practices.

Responsibilities

• Own architecture and code of the product API and services layer.
• Ensure fast, reliable AI feature integration for lawyers under deadline.
• Design multi-tenant isolation and data models for matters, drafts, versions.
• Oversee authentication, billing, uploads, exports, and notifications.

Skills

Python backend

FastAPI/Django/Flask

Multi-tenant SaaS

API design

Auth (OAuth/OIDC/JWT)

Job description

You own the platform every part of ParamAIQ is built on. The app, the AI features, the integrations for law firms: all of it runs through the API and services layer you build. When a lawyer trusts us with a confidential matter and expects it to be fast, correct, and private, your systems are what make that true. This is a senior, deeply hands-on role. You make the architectural calls, and you write the code that matters most. We want senior people who get the foundations right the first time, because in legal software a bug is not cosmetic: it is a confidential matter exposed or a filing that fails.

YOU WILL OWN

• The architecture and the code of the product API and services layer.
• The systems that make AI features usable in real work: long-running, sometimes-failing operations that still must feel fast and reliable to a lawyer under deadline.
• Multi-tenant isolation strong enough that one firm's matters are provably invisible to another. In legal, a cross-tenant leak is the worst thing that can happen.
• Data models for legal work (matters, drafts, versions, audit trails) that stay coherent as the product grows.
• Reliability, performance, and cost as the system scales.
• The rest of the product surface: authentication, billing, uploads, exports, notifications.

THE HARD PROBLEMS

• Making unreliable, slow AI operations feel dependable. Model calls fail, time out, and cost money. The orchestration, idempotency, and graceful degradation that hide all of that from a lawyer is a real systems problem.
• Isolation you can prove. Not just separating tenants but demonstrating and testing that separation across every path in the product.
• Getting the foundations right early. The data models, contracts, and access control you set now are the hardest things to change later, and the most expensive to get wrong once real client data is flowing.

WE ARE LOOKING FOR

• 4+ years of backend engineering in Python, with a framework like FastAPI, Django, or Flask.
• You design systems, not just features. You reason about scale, reliability, cost, and failure, and you defend your calls.
• You've built multi-tenant SaaS with real data isolation between customers.
• Strong API and service design: contracts, versioning, idempotency, rate limiting, backpressure.
• Real command of auth: OAuth, OIDC, JWT, sessions, RBAC.
• You write careful code and test the paths that matter, because you know what a mistake costs here.

NICE TO HAVE

• 0-to-1 and early scale: you've taken a system from first version to real load and know what breaks first.
• Performance and reliability work: profiling, load testing, and finding the failure before it reaches a user.
• Async and background job systems (Celery, RQ) at scale.
• Payments and billing systems (Razorpay, Stripe, or similar) and their failure modes.
• Legal-tech, regtech, fintech, healthtech, or another regulated, trust-sensitive domain.
• DPDPA, Indian data residency, and security practice.

THIS ISN'T THE ROLE IF

• You want tightly scoped tickets. You own architecture and tradeoffs, and much of the value is getting the foundations right before the product is big enough to make them expensive to change.