Senior Backend Engineer at Zensar
—
Jul 21, 2026
—
Jul 24, 2026
What this job asks for AI summary
A senior engineering role focused on building and maintaining the API and data-processing backbone of a document-processing platform called ATLAS. Day-to-day work involves designing Python/FastAPI microservices, wiring together Azure-native event-driven pipelines, securing service-to-service communication, and managing persistence across Cosmos DB, relational databases, and Blob Storage. Suited to a backend specialist with deep cloud-native and distributed systems experience.
Senior level · 7+ years
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 29, 2026. It is a model, not a headcount.
Why we read it this way (5)
The specific Azure services (App Services, Functions, Event Grid, Service Bus, Blob Storage, Key Vault) are named in the Responsibilities section as part of the team's implementation context rather than in the Required Skills block, so they are marked preferred. Azure broadly and Cosmos DB are called out explicitly in both sections and are marked required.
Microsoft Entra ID, OAuth2/JWT, and RBAC are listed in Responsibilities but the Required Skills block independently gates on 'API security, identity, access control, and secure secret management' — Entra ID, OAuth2, and JWT are the named concrete technologies for that gate and are marked required accordingly. RBAC is a methodology/concept rather than a named tool and is omitted per extraction rules.
Microservices and event-driven architecture are named as concrete design patterns in the Required Skills block; microservices is retained as a named architectural requirement. 'Event-driven' is a methodology concept and is omitted.
Agile appears only under the Preferred section and is marked preferred.
No compensation, employment type, or degree requirement is stated in the posting.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.