# Architect — Virtusa

- Location: New York
- Posted: Nov 2, 2026
- Status: open (checked Nov 21, 2026)
- Apply (employer's site): https://www.virtusa.com/careers/job-search/global/en/job/VIRVIRGLOBALP103191EXTERNALENGLOBAL
- Employer record: https://visajobs.io/company/virtusa.md

## Sponsorship history
- Tier: Strong history
- Occupation (SOC): Computer Systems Engineers/Architects (15-1299)
- Employer's certified LCAs for this occupation in NY, FY2024–FY2026: 26
- …in the whole US: 801
- With this exact title: 0
- Median DOL prevailing wage, level I / II: $58k / $90k
- Staffing / consulting firm: 76% of its H-1B applications place workers at client sites (FY2024–FY2026)

## Description
Data Modeler
Primary purpose
The Data Modeler defines how the organization represents its business concepts consistently
across events, Bronze, Silver, Gold, semantic models, and ontology.
The Data Modeler answers questions such as:
What is a member-month?
How is a delegated population represented?
How do contract, risk arrangement, product, and population relate?
How do we preserve restatements and historical versions?
What is the grain of each data product?
Which entity owns each business key?
Key responsibilities
Enterprise and conceptual modelling
Logical data modeling
Define entities, attributes, relationships, cardinality, and business keys.
Physical modeling
Work with Data Engineers to translate logical models into:
Bronze event tables
Silver conformed entities
Gold analytical data products
Lakehouse tables
Relational operational stores
Star schemas
Aggregate tables
Cube.dev models
Graph or ontology representations
Temporal and historical modeling
This is especially important for the program.
The Data Modeler must differentiate:
The Data Modeler works with the Cube.dev and ontology teams, but does not replace them.
The modeler ensures that:
Physical data structures support governed measures.
Cube.dev dimensions and joins reflect valid business relationships.
Ontology concepts map to identifiable data entities.
Data grains do not produce double-counting.
Business hierarchies are represented consistently.
Semantic definitions remain connected to source data and lineage.
Required skills
Conceptual, logical, and physical data modeling
Relational and dimensional modeling
Event and canonical-data modeling
Effective-dated and temporal modeling
Bitemporal modeling
Business-key and surrogate-key design
Master and reference data
Data normalization and denormalization
Lakehouse and warehouse modeling
Metadata and lineage
Model governance and versioning
Strong SQL knowledge
Modeling tools such as ER/Studio, erwin, Sparx, Archi, or equivalent
Preferred domain knowledge
Healthcare claims and encounter models
Membership and eligibility
Provider and organization hierarchies
Capitation and delegated-risk arrangements
Provider contracts and settlements
Finance and accounting data
Journals, subledgers, and GL
Actuarial and reserve data
Semantic layers and knowledge graphs

> History, not a promise: past H-1B filings do not mean an employer will sponsor you or a given role. Data: U.S. DOL OFLC LCA disclosure (FY2024–FY2026 for role counts, certified LCAs) and the USCIS H-1B Employer Data Hub. Not legal advice. Methodology: https://visajobs.io/methodology
