Define and own the four-tier test framework: unit (per spec acceptance criterion), integration (within-layer composition), contract (cross-layer schema and behaviour), and acceptance (end-to-end scenarios). Establish the conventions that distinguish them and the CI gates that enforce them
Establish the spec-to-test traceability standard. Every acceptance criterion in a unit spec must have at least one named test that verifies it; test names reference the AC ID by convention; CI enforces coverage. The traceability is regulatory-defensible by design
Establish synthetic test data conventions - no real PHI in fixtures; structured-but-synthetic patient names, identifiers, dates; reusable patterns for multi-source linkage scenarios; coverage of edge cases (NULLs, ECI merges, late-arriving data, validation failures)
Define performance SLOs and monitoring strategy. Every component has measurable latency, throughput, and freshness budgets. Build dashboards that operators use during incidents and that establish trend baselines over time
Build out test automation for FHIR profile validation - every Bundle published is validated against US Core 6.1 in CI and in the runtime path. Establish the FHIR validator deployment, the profile pack management, and the test patterns that prove conformance
Lead testing for the bidirectional FHIR flow - verifying loop prevention via origin tagging works under load, that the FHIR-Repository egress interceptor captures every client-originated change, that the loopback Flink job applies write-authority rules correctly, and that no echoes propagate
Establish testing patterns for MDM integration - synthesizing match/no-match/multi-match scenarios, validating ECI assignment correctness, validating ECI_MERGE and ECI_SPLIT handling end-to-end, validating DLQ routing for MDM failures
Lead validation of data quality at every layer - DBT test suites for CDM, freshness checks at every layer boundary, anomaly detection for ingestion patterns, governance integration for quality metric publication to Atlan
Mentor data engineers on test authorship under the spec-driven development framework. Tests are part of every PR; their quality is part of the PR review; the QA lead sets the bar
Participate in in
Benefits
Health insurancePaid time off
Additional Information
While technology is the heart of our business, a global and diverse culture is the heart of our success. We love our people and we take pride in catering them to a culture built on transparency, diversity, integrity, learning and growth.
If working in an environment that encourages you to innovate and excel, not just in professional but personal life, interests you- you would enjoy your career with Quantiphi!
QA Architect / Lead
Exp Range : 8 - 13 Years
Job location : Mumbai , Bangalore, Trivandrum
The QA Architect/Lead is responsible for the testing strategy and infrastructure across the entire platform. You will define the four-tier test framework (unit, integration, contract, acceptance), establish the conventions that ensure every spec-defined acceptance criterion has a verifying test, build out the validation infrastructure for parallel-run cutover from the existing Health Data Engine, and lead the load testing campaign that validates the platform's high-volume
capacity claims.
This role is technical-lead calibre. You will design test frameworks that data engineers consume, set the CI/CD gating policies that determine what merges and what doesn't, and lead the validation that determines when the platform is ready for production traffic. You will work in close partnership with the architect on spec-derived test conventions and with the data engineering team on the operational maturity of every component.
Quantiphi · Mh Mumbai Eureka, India