[Hiring] Senior SQL and Data Engineer @Aubrant Digital

Role Description

As a Senior SQL and Data Engineer, you will own the data tier that everything else in this platform depends on. You will:

• Design the denormalized read models and snapshot tables that let a composed patient view resolve in milliseconds.
• Tune the queries and indexes that serve them.
• Build the refresh pipelines that keep them current against EHR, health information exchange, claims, and pharmacy feeds with clearly published freshness guarantees.
• Work at production data volume, with execution plans open, and be the person who can say what a query will cost before it ships.
• Own the de-identification path that lets offshore engineers work safely, designing synthetic data that is realistic enough to test against and provably free of protected health information.

Qualifications

• Bachelor's Degree in Computer Science or a related discipline, or equivalent experience.
• MUST be fluent in written and spoken English at a native or bilingual level; this role is client-facing daily.
• 6+ years of professional data engineering or database engineering experience on Microsoft SQL Server and Azure SQL.
• Expert-level advanced T-SQL, including window functions, set-based rewriting of procedural logic, and query plan-aware design.
• Expert-level index design across covering, filtered, and columnstore indexes, with demonstrated tuning results at production data volume.
• Strong execution plan analysis skills, plus practical use of Query Store, Extended Events, Resource Governor, and readable secondaries.
• Proven experience designing denormalized read models, snapshot tables, and materialized aggregates for low-latency read paths.
• Experience with Flyway or an equivalent versioned migration tool running inside a CI pipeline.
• Experience with healthcare data, including claims, HIE feeds, and pharmacy or Surescripts data, and with PHI de-identification technique.
• Working knowledge of .NET and C# sufficient to review and influence the data access layer.
• Experience with Redis or another distributed cache sitting in front of a relational read model is a plus.
• Experience with Azure SQL Managed Instance, Azure Data Factory, or Databricks is a plus.
• Excellent problem-solving skills, with the ability to analyze complex requirements and propose innovative solutions.
• Strong communication and collaboration skills, with the ability to work effectively in a cross-functional team environment.
• Able to build strong customer relationships and deliver customer-centered solutions.

Requirements

• Reasons about data volume and query cost before writing code, not after a performance incident.
• Rigorous about correctness: a risk score shown in two places has to agree in both.
• Able to explain a data lineage or freshness constraint to a clinician in terms they can act on.
• Treats migrations, rollback, and data quality checks as part of the deliverable.
• Comfortable owning a single critical seat and being the escalation point for it.

Responsibilities

• Data Modeling and Performance:
  • Design denormalized read models and snapshot tables that let a multi-source patient view resolve as a small number of indexed lookups.
  • Own index strategy across covering, filtered, and columnstore indexes, and tune queries using execution plans and Query Store at production volume.
  • Partner with the architect on SQL Server workload management, including Resource Governor and readable secondary routing.
• Pipelines and Integration:
  • Build and operate ETL, change data capture, and delta refresh pipelines across EHR, HIE, claims, and pharmacy sources.
  • Define and publish a refresh service level per data source, so the interface can show accurate as-of dates rather than implying real-time data.
  • Implement the shared cohort and risk scoring data layer so every consuming screen reports identical values.
• Data Governance and Quality:
  • Own the de-identification and synthetic data generation path that keeps the offshore development environment free of protected health information.
  • Deliver versioned, gated database migrations through Flyway or an equivalent tool inside the CI pipeline.
  • Build data quality and reconciliation checks that catch a broken feed before a clinician sees stale data.