Senior Quality Engineer
Imperial Brady is building a single enterprise data platform out of the merged Imperial Dade and BradyPlus data estates. The EDW team delivers that platform on Microsoft Fabric, and every change we ship moves through Dev, UAT, and Prod on a three-week sprint cycle.
We are hiring our first dedicated Quality Engineer, at a senior level. This is an engineering role. The person in this seat writes and runs automated tests that prove our pipelines, transformations, and architecture changes behave correctly before anything is handed to the business. Their work happens during the development weeks, inside the code and the deployment pipeline, not at the end of the sprint.
To be explicit about the boundary: this role is not UAT testing, and it is not data quality validation. The business units own data quality and acceptance during the UAT week, and they produce the reconciliation evidence that gates a release. This role exists so that by the time a Story reaches UAT, the business is evaluating whether the numbers are right, not discovering that the build is broken. There is no test framework, no automated regression suite, and no QA function today. You are being hired to build them.
Compensation Range:
$120,000 to $140,000 + Bonus
Salary range reflects the Jersey City, NJ market & compensation may vary based on geographic location
You Will: Build automated tests that exercise Fabric pipelines, notebooks, and transformation logic, proving that a pipeline runs end to end, handles failure and retry correctly, and produces the expected result from controlled test input.
Build automated checks that validate structural changes to materialized lake views (MLVs), lakehouse tables, and semantic models: expected columns and data types, key definitions, dependency chains, and view refresh behavior after a change.
Test the incremental load behavior our pipelines depend on: watermarking, idempotency, restart and rerun safety, late arriving records, and full reload versus delta paths.
Automate environment parity verification across Dev, UAT, and Prod, covering object inventory, schema, configuration, and dependency structure, and report drift as soon as it appears rather than at reconciliation time.
Act as the technical authority on testing for the team. Mentor developers on writing their own tests and set the direction the function follows as it grows beyond one person.
Help stand up the testing and deployment practice against the Fabric Well-Architected Framework, which the team is adopting as its governance baseline. Much of that alignment is still ahead of us and this role contributes to defining it.
Report on engineering quality with real numbers: automated coverage, test pass rate, build failure rate, and defect escape rate by stage.
You Have: Five or more years in test automation, software engineering in test, or data engineering with a heavy testing component, including time spent building a test framework rather than only working inside one. Manual QA experience alone is not a fit for this role.
Strong Python, including building and maintaining real test suites with a framework such as pytest, and comfort working in PySpark or notebook-based data processing.
Strong SQL, at the level of writing the query that proves a transformation produced what the specification called for.
Demonstrated experience testing ETL or ELT pipelines and dimensional models, with a working understanding of fact and dimension tables, grain, incremental loads, and slowly changing dimensions.
Practical Git and CI/CD experience: branching, pull requests, and building automated checks that run inside a deployment pipeline.
Experience defining and enforcing technical acceptance criteria as part of an Agile sprint process, including holding a release gate when a change is not ready.
Clear written communication, since a large part of this role is documenting what is covered by automation and what is not.
