You will be taken to EXL’s own careers page to apply. Job ID 21108.
Job description
Own the requirements-to-acceptance chain for the Entity Hub. This is a combined role: define what “correct” means for entity resolution and graph outputs, then prove it through structured testing. The position is pivotal because milestone payments are released against acceptance criteria — this role writes them, traces them and validates against them.
Responsibilities
Requirements & traceability — elicit, document and baseline functional and data requirements across ingestion, canonical model, entity resolution and graph serving; maintain a Requirement Traceability Matrix (RTM) from requirement through to test evidence.
Acceptance criteria ownership — translate SOW stage acceptance criteria into testable, measurable conditions; secure WK agreement on match-quality measures (precision/recall) and NLQ scenarios before build begins.
Test strategy & planning — define the overall test strategy, quality gates, entry/exit criteria and test data approach for each milestone.
Data quality validation — design and execute tests for data completeness, accuracy, transformation logic, standardization rules and identifier-spine integrity across all six sources.
Entity resolution validation — build and curate labelled/golden validation samples; evaluate match precision, recall and false-positive rates; validate clustering and Golden Record survivorship logic.
Graph validation — test node and edge accuracy, source traceability, and multi-hop traversal scenarios against expected paths.
Human-in-the-loop coordination — operate and coordinate the SME review workflow, manage the review queue, capture reviewer decisions and feed them back as training/tuning input.
Defect management — log, triage and track defects with reproducible steps; drive root-cause analysis on data discrepancies; maintain severity classification and closure evidence.
UAT & sign-off — plan and coordinate user acceptance testing with WK SMEs; assemble milestone acceptance packs and secure written sign-off within the agreed review window.
Required Skills & Experience
Skill Area Specific Requirements
Business Analysis Requirements elicitation, user stories, functional specifications, RTM, data dictionaries, source-to-target mapping documentation
QA / Testing Test strategy, test planning, test case design, regression suites, UAT coordination, defect lifecycle management
Data Testing Advanced SQL for reconciliation, source-to-target validation, aggregation and business-rule testing, data integrity and constraint checks
Domain (advantageous) Entity/master data concepts, match precision & recall, data quality dimensions, corporate hierarchy and ownership data
Tools Test management platforms (QTest/Jira/ADO), Excel, Postman for API validation, Power BI for validation reporting
Soft Skills Client-facing communication, stakeholder facilitation, precision in written acceptance language, structured escalation
Requirements
6+ years combined Business Analysis and QA experience on data platform or data warehouse programmes
Demonstrable experience writing acceptance criteria that were used for formal client sign-off
Strong SQL — able to independently write reconciliation and validation queries
Experience maintaining a Requirement Traceability Matrix on a regulated or enterprise client engagement
Experience coordinating UAT with external client stakeholders
Nice-to-Have
Exposure to entity resolution, MDM or data-matching projects
Familiarity with Microsoft Fabric or Azure data services
Understanding of graph data structures (nodes, edges, traversal)
Experience with statistical quality measures (precision, recall, F1)
Key Deliverables Owned
Requirement Traceability Matrix (RTM)
Test Strategy, Test Plans, Test Scenarios and Test Cases
Entity resolution evaluation results and match-quality reports
Node/edge accuracy validation evidence
Defect log, RCA reports and closure evidence
UAT sign-off and milestone acceptance packs
Dual Role / Complementary Skills
This is already a deliberate dual role (BA + QA). The pairing is intentional: the person who defines acceptance criteria is best placed to test against them, creating a tight traceability loop and removing hand-off ambiguity. Complementary overflow: this role can absorb a portion of project-coordination and documentation work alongside the Project Manager (who is at 75% FTE).
