Senior GCP Data Engineer (R-19655) at Dun & Bradstreet
Hyderabad - India
—
Jul 19, 2026
Hyderabad - India
Jul 21, 2026
What this job asks for AI summary
A senior-level data engineering role focused on building and maintaining large-scale data pipelines, ETL/ELT workflows, and the underlying architecture for an identity graph and data platform. Day-to-day work involves ingesting and unifying data from multiple sources — including web, mobile, and third-party datasets — handling billions of records using Python, SQL, and cloud platforms such as GCP and AWS. Suits an independent, analytically minded engineer with 5–8+ years of production data engineering experience.
Senior level · 5+ years · Remote
“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 920 people nationally plausibly meet what this posting asks for (database architects). range 190–1,350
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 role is genuinely ambiguous between 15-1243 (Database Architects) and 15-1252 (Software Developers). The primary focus is designing and building large-scale data pipelines, identity graph systems, and data architecture — leaning toward data/pipeline architecture — but the strong emphasis on writing production Python code and delivering software end-to-end also fits Software Developers. 15-1243 was chosen as the primary code given the explicit architectural and data-modeling responsibilities.
GCP services (BigQuery, Dataflow, Pub/Sub, Cloud Storage, Cloud Functions) are listed together as a required block alongside AWS as an alternative cloud platform. The individual GCP services are extracted separately to reflect the specificity of the requirement.
AWS services (S3, Redshift, EMR, RDS) are listed as an alternative to GCP in the requirements section ('and/or AWS'), so they are marked preferred rather than hard gates — the JD gates on GCP or AWS, not both.
CI/CD, Docker, Kubernetes, and GitHub Actions appear in the requirements section under 'Familiarity with' — a softer qualifier — but remain in the required block. They are marked as required given their placement in the Key Requirements section; the 'familiarity' phrasing is noted as a mild softener.
No compensation range is stated in the posting.
No degree requirement is stated.
This posting reads as a fully-remote role, so it was scored against the national candidate pool rather than a single metro.
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.