Data Architect at Virtusa
—
Jun 28, 2026
—
Jul 20, 2026
What this job asks for AI summary
A hands-on data architecture role focused on migrating data pipelines and consumers from legacy analytical platforms to modern cloud-based ones, primarily on AWS and Snowflake. Day-to-day work spans building APIs and components, developing proof-of-concepts for data integration patterns, evaluating technologies, and documenting cloud and event-driven architecture patterns. Suits an experienced data architect comfortable operating at both a strategic and practical engineering level.
Senior level · Hyderabad, India · Full-time
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
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $139,500 (middle half $109,370–$169,290).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (7)
This role is based in Hyderabad, India (explicitly stated as 'IN-AP-Hyderabad'); US compensation benchmarks do not apply.
The posting is a hybrid architecture + hands-on engineering role — the candidate is expected to both design data platform architecture AND build APIs/components. 15-1243 (Database Architects) was chosen as the primary SOC given the explicit 'Data Architect' title and architecture governance responsibilities; 15-1252 (Software Developers) is a credible runner-up given the hands-on API/component-building duties.
All named technologies (AWS services, Python, Snowflake, Tokenization, Encryption) appear in the opening requirements paragraph with firm language ('Hands-on experience on…'), so they are treated as hard gates. 'Cloud architecture' and 'event-driven architecture' appear only in narrative/context sections describing patterns to document and are treated as preferred.
No total years of experience, degree requirement, or compensation range is stated in the posting.
Cross-account data sharing on AWS is described as part of the required AWS hands-on experience; it is captured under the AWS Lake Formation and AWS IAM skills rather than as a separate entry, as it is a feature of those services rather than a distinct tool.
Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): Cloud architecture.
This role's work location reads as outside the US — the candidate pool, comp, and contention benchmarks here are US-only (BLS employment, Adzuna/USAJOBS demand, and certified H-1B wages), so treat them as a rough US reference, not a local market.
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.