Pay
In line with similar jobs
$110K–$168K against $127K–$189K, the middle half of what similar US postings state.
From 2,448 postings in the last year. Stated ranges, not salaries paid.
Birmingham, AL
Live, first seen by us 59 days agoDatabricks certification (Data Engineer Professional or equivalent demonstrated depth). • Unity Catalog at multi-team scale: catalogs, schemas, external locations, permissions, and lineage. • dbt at scale on Databricks, and Python-based modeling frameworks over Delta Lake. • Dagster and Dagster Cloud, including assets, asset checks, and branch deployments. • Practical experience with data contracts, ODCS, or data-mesh style data product ownership. • Experience with a declarative Python ingestion framework such as dlt (dltHub) or comparable. • Data quality and observability tooling such as Great Expectations, Monte Carlo, or similar. • Familiarity with MLOps practice — MLflow, model registries, and model serving — sufficient to design data products that ML systems can depend on. • Azure and Azure DevOps. • Financial services, insurance, or another regulated industry, including data access, lineage, and audit expectations. • Experience introducing AI-assisted development into a team’s normal workflow in a disciplined way. Protective’s targeted salary range for this position is $109,500 to $167,833. Actual salaries may vary depending on factors, including but not limited to, job location, skills, and experience. The range listed is just one component of Protective’s total compensation package for employees. This position also offers additional incentive opportunities through an annual incentive based on individual and Company performance.
Salary 109,500 – 167,833 USD per year Employee Benefits:Read the full posting
Work setup in the employer’s posting: remoteFrom the employer’s posting
Employment type Full Time
Employment type in the employer’s posting: Full TimeFrom the employer’s posting
Lead end-to-end design of data products across ingestion, conformance and Gold layers
Own dimensional modeling: grain, keys, Type 2 history and conformed dimensions
Own ODCS data contracts and make compatibility calls on proposed changes
Lead code review, catching modeling mistakes, missing tests and breaking changes
Own operational posture for pod pipelines, including on-call, backfills and root-cause analysis
Lead the design of data products end to end
Own dimensional design — grain, natural and surrogate keys, Type 2 history, facts, bridges, and conformed dimensions shared across the pod’s products.
Own the pod’s ODCS data contracts as real interfaces
Lead code review. Be the reviewer who catches the modeling mistake, the missing test, and the change that will break a consumer
Own the pod’s operational posture for its own pipelines: failure diagnosis, data-issue triage, backfills, cost and performance tuning, on-call coverage and escalation, root-cause analysis, and runbooks someone other than the author can execute.
Bachelor’s degree in Computer Science, Information Systems, Engineering, or a related field; equivalent practical experience considered. • 6+ years building and operating production data pipelines and consumer-facing data models, from source ingestion through to published data products. • Strong hands-on Python and SQL, with the credibility to make design calls and the willingness to still write and review code. • Hands-on experience with Databricks or a comparable Spark-based lakehouse, including Delta Lake, MERGE, incremental processing, and performance tuning. • Deep dimensional modeling experience — grain, keys, slowly changing dimensions, facts and dimensions, conformed dimensions. • Demonstrated technical leadership: setting standards, leading design, and raising other engineers’ work, whether or not the role carried a lead title. • Experience owning data that other teams depend on, including handling breaking changes and production data incidents. • Experience with orchestration (Dagster, Databricks Workflows, Airflow, or similar), Git-based collaborative development, code review, and CI/CD — Azure DevOps or comparable. • Experience setting observability and SLA/SLO expectations for data other teams depend on, and running the incident and communication path when they are missed. • Ability to explain trade-offs clearly to engineers, product owners, and business stakeholders, and to say no to a design that will not hold.
From the employer’s posting.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
In line with similar jobs
$110K–$168K against $127K–$189K, the middle half of what similar US postings state.
From 2,448 postings in the last year. Stated ranges, not salaries paid.
Day 59
Up longer than most. Similar jobs usually come down between day 6 and day 56.
From 14,770 similar postings that came down. Coming down is not always a hire.
4 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordAdd your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
Data contracts and consumer compatibility • Own the pod’s ODCS data contracts as real interfaces: named owners, named consumers, enforceable quality rules, freshness and update expectations, and an explicit breaking-change policy. • Make the compatibility call on every proposed contract change, and drive consumer notification when a change is genuinely breaking. • Represent the pod’s contracts in cross-domain conversations, where one pod’s Gold layer is another team’s dependency. Standards, quality, and operations • Set and hold the pod’s engineering standards for Python, SQL, dbt, testing, model structure, naming, and repository conventions — consistent with the platform’s paved paths and Azure DevOps CI gates rather than in competition with them. • Lead code review. Be the reviewer who catches the modeling mistake, the missing test, and the change that will break a consumer, and who explains why so the pod learns it. • Ensure quality rules are enforced in tests and asset checks rather than asserted in documentation, and that pipeline health is observable without someone going to look — freshness, volume, latency, and cost instrumented, and alerting set against the SLAs and SLOs the pod’s contracts commit to. • Own the pod’s operational posture for its own pipelines: failure diagnosis, data-issue triage, backfills, cost and performance tuning, on-call coverage and escalation, root-cause analysis, and runbooks someone other than the author can execute. • Keep the pod’s delivery inside the control expectations of a regulated carrier: change management through pull request and pipeline, segregation of duties between authoring and deploying, least-privilege access, and audit evidence that falls out of CI/CD rather than being assembled for an auditor. • Develop reusable frameworks, templates, and patterns that raise the pod’s consistency and delivery speed. Delivery leadership
Required Qualifications • Bachelor’s degree in Computer Science, Information Systems, Engineering, or a related field; equivalent practical experience considered. • 6+ years building and operating production data pipelines and consumer-facing data models, from source ingestion through to published data products. • Strong hands-on Python and SQL, with the credibility to make design calls and the willingness to still write and review code. • Hands-on experience with Databricks or a comparable Spark-based lakehouse, including Delta Lake, MERGE, incremental processing, and performance tuning. • Deep dimensional modeling experience — grain, keys, slowly changing dimensions, facts and dimensions, conformed dimensions. • Demonstrated technical leadership: setting standards, leading design, and raising other engineers’ work, whether or not the role carried a lead title. • Experience owning data that other teams depend on, including handling breaking changes and production data incidents. • Experience with orchestration (Dagster, Databricks Workflows, Airflow, or similar), Git-based collaborative development, code review, and CI/CD — Azure DevOps or comparable. • Experience setting observability and SLA/SLO expectations for data other teams depend on, and running the incident and communication path when they are missed. • Ability to explain trade-offs clearly to engineers, product owners, and business stakeholders, and to say no to a design that will not hold. Preferred Qualifications
Preferred Qualifications • Databricks certification (Data Engineer Professional or equivalent demonstrated depth). • Unity Catalog at multi-team scale: catalogs, schemas, external locations, permissions, and lineage. • dbt at scale on Databricks, and Python-based modeling frameworks over Delta Lake. • Dagster and Dagster Cloud, including assets, asset checks, and branch deployments. • Practical experience with data contracts, ODCS, or data-mesh style data product ownership. • Experience with a declarative Python ingestion framework such as dlt (dltHub) or comparable. • Data quality and observability tooling such as Great Expectations, Monte Carlo, or similar. • Familiarity with MLOps practice — MLflow, model registries, and model serving — sufficient to design data products that ML systems can depend on. • Azure and Azure DevOps. • Financial services, insurance, or another regulated industry, including data access, lineage, and audit expectations. • Experience introducing AI-assisted development into a team’s normal workflow in a disciplined way. Protective’s targeted salary range for this position is $109,500 to $167,833. Actual salaries may vary depending on factors, including but not limited to, job location, skills, and experience. The range listed is just one component of Protective’s total compensation package for employees.
We help protect our customers against life’s uncertainties. Regardless of where you work within the company, you’ll be helping provide protection and peace of mind when our customers need it most. Protective is looking for a Lead Data Engineer to set the technical direction for a delivery pod building data products on Voyager, our Databricks lakehouse on Azure. You will lead the design of data products through the full medallion architecture — Bronze ingestion, Silver conformance, and Gold consumption — and be accountable for whether those products hold up for the consumers who depend on them. This is a hands-on technical leadership role, not a people-management or project-management role. You will still write and review production code daily. What you own is how the pod’s data products are designed, modeled, contracted, and tested, and the standard the pod holds itself to. The Product Owner owns the backlog and the Scrum Master owns the sprint; you own the engineering.
Complete your application on jobs.lever.co. The employer’s form will show what is required.
Already applied? Track this application
109,500 – 167,833 USD per year
Full Time
New Data Engineer postings at the employers we follow are up 13% over the last 6 weeks compared with the 6 before.
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
We file this job under Data Engineer, by the work the posting describes.
Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.
Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.
An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.
The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.
Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
Salary 109,500 – 167,833 USD per year Employee Benefits:
More relevant text appears in the full description.
Birmingham, AL
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.