Principal Data Engineer (R-19440)
Dun & Bradstreet · Hyderabad - India
—
Jul 26, 2026
Hyderabad - India
Jul 28, 2026
What this job asks for AI summary
A hands-on Principal Data Engineer role focused on designing and building large-scale data pipelines, ETL/ELT workflows, and an identity graph platform that ingests and unifies billions of records from web, mobile, AdTech, and proprietary sources. The role spans end-to-end ownership — from architecture and data modeling through production deployment — and suits a deeply technical engineer experienced with distributed data systems on GCP and/or AWS.
Senior level · 8+ years · Remote
Advertised as Principal, but the requirements read as Senior.
Quick apply — this platform usually takes a CV and a few fields.
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 580 people nationally plausibly meet what this posting asks for (database architects). range 350–870
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $142,568 (middle half $111,775–$173,013).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (7)
The posting is titled 'Principal Data Engineer' but the requirements (8-12+ years, end-to-end ownership of a single platform domain) are consistent with a Senior-level role on a normal career ladder; 'Principal' here appears to be a title inflation common at smaller or growth-stage companies rather than a genuine org-wide technical authority scope.
SOC classification is a genuine toss-up: the role designs and architects data platforms (15-1243 Database Architects) but also writes substantial production Python code and builds distributed systems (15-1252 Software Developers). 15-1243 was chosen because data architecture, modeling, and pipeline design are the stated primary outputs.
GCP and AWS are listed together as an 'and/or' requirement in the Key Skills section. Both are captured as required with each other as an alternative, reflecting that deep experience in at least one is a hard gate.
The GCP sub-services (Dataflow, Pub/Sub, Cloud Storage, Cloud Functions) and AWS sub-services (S3, EMR, RDS) are named in the same Key Skills block but read as illustrative examples of the platform rather than individually gated requirements; marked as preferred accordingly.
Docker, Kubernetes, GitHub Actions, and CI/CD appear together under 'Familiarity with CI/CD, containerization, and orchestration tools (Docker, Kubernetes, GitHub Actions, etc.)' in the Key Skills section — the 'familiarity with' phrasing could suggest preferred, but the section is a hard-requirements block, so they are marked required.
Jira and Confluence are listed as examples of 'Agile tools' in the required section; Jira is used as the primary skill with Confluence as an alternative since they serve different functions but are grouped as one requirement.
No compensation, location, or employment type is stated in the posting.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.