Software Engineer III - Analytical Data

ZoomInfo is where careers accelerate. We move fast, think boldly, and empower you to do the best work of your life. You’ll be surrounded by teammates who care deeply, challenge each other, and celebrate wins. With tools that amplify your impact and a culture that backs your ambition, you won’t just contribute. You’ll make things happen–fast.

ZoomInfo (NASDAQ: GTM) is the Go-To-Market Intelligence Platform that empowers businesses to grow faster with AI-ready insights, trusted data, and advanced automation. Its solutions provide more than 35,000 companies worldwide with a complete view of their customers, making every seller their best seller.

Our mission is simple but ambitious: deliver the most accurate and comprehensive B2B data to power modern go-to-market strategies. We continuously innovate to help businesses identify ideal customers, reach key decision-makers, and accelerate growth through data-driven insights.

The Opportunity

We're looking for a Software Engineer III to join the Analytical Data team - the team that builds and runs the lakehouse for ZoomInfo's Data organization.

ZoomInfo's data about people and companies is produced by many teams and used by many more: analysts, data scientists, product managers, and, increasingly, AI agents. We are building one governed source of that data for all of them. Each dataset is written once as Apache Iceberg tables, kept on both Google Cloud Storage and Amazon S3, and queried in place by BigQuery, Snowflake, and Starburst/Trino - no separate copy or export pipeline per engine. The goal is that anyone in the Data organization, person or agent, can query fresh, trusted data without an engineer in the loop.

This is a hands-on data engineering role. You will work across streaming and batch ingestion, Iceberg table management, multi-engine access, data contracts with producer teams, and the observability that shows the data is fresh and complete. Datasets run to hundreds of millions of records, and most refresh daily.

What You'll Do

• Build and run Kotlin and Apache Beam pipelines on Google Cloud Dataflow that load data from Kafka and cloud storage into Apache Iceberg tables.


• Keep large Iceberg tables correct, fast, and cost-efficient with good partitioning, Spark maintenance jobs (compaction, deduplication, snapshot expiry, orphan-file cleanup), and reconciliation against the source.


• Make each dataset queryable from BigQuery, Snowflake, and Starburst/Trino through Iceberg catalogs and stable consumer views.


• Work with producer teams on schemas and data contracts, and keep publishing a new dataset simple and documented.


• Build the observability that shows each dataset is fresh, complete, and within budget: Datadog dashboards and monitors today, AI agents for alert triage next.


• Own your pipelines in production, from incident response to the fix that keeps the problem from coming back.


• Ship through code review, CI/CD, staged releases, and unit, integration, and end-to-end tests, with infrastructure managed in Terraform across GCP and AWS.


• Work daily with data consumers, producer teams, and platform teams, and help shape the platform's technical roadmap.

Must-Have Qualifications

Data Engineering and Distributed Systems

• 3+ years of professional software engineering experience, with a focus on data engineering or distributed systems.


• Strong programming skills in Kotlin, Java, or Python. Our ingestion pipelines are written in Kotlin and our table maintenance and orchestration in Python, so you will work in both.


• Hands-on experience with Apache Beam (ideally on Google Cloud Dataflow) or Apache Spark.


• Experience with Apache Kafka or a similar streaming platform in production pipelines.


• Experience with very large datasets and distributed systems, including designing data models and storage layouts that handle large volumes efficiently.

Lakehouse, Query Engines, and Cloud

• Understanding of lakehouse architecture and open table formats, ideally Apache Iceberg.


• Strong SQL and working knowledge of at least one of BigQuery, Snowflake, or Starburst/Trino.


• Experience with Protobuf or Avro schemas and evolving them without breaking downstream consumers.


• Experience with GCP or AWS. We are GCP-first, with storage and catalogs on AWS as well.

Engineering Practices and Operations

• Good understanding of the SDLC for data pipelines, including unit, integration, and end-to-end tests.


• Experience running pipelines in production with metrics, dashboards, and alerts (for example in Datadog), and a strong ownership mindset: you take responsibility for production incidents end-to-end.


• Practical, everyday use of AI coding assistants such as Claude Code or Codex, with the judgment to review and test what they produce.

Collaboration and General

• Experience in cross-team collaboration: working directly with producer teams on schema changes and daily with data consumers (analytics, ML) and platform/infrastructure teams, with the ability to navigate different contexts and technical vocabularies.


• Bachelor's degree in Computer Science, Software Engineering, or a related field, or equivalent practical experience.


• Pragmatic engineering judgment with the ability to balance quality, speed, and business impact.

Nice to Have

• Production experience with Apache Iceberg: table maintenance, partition and schema evolution, and Iceberg catalogs such as BigLake metastore (now Google's Lakehouse runtime catalog), AWS Glue, or Project Nessie.


• Experience with metadata catalogs and data governance tooling such as OpenMetadata.


• Experience building AI agents that watch pipelines, triage alerts, or investigate data issues.


• Experience serving the same data to several query engines, or running data infrastructure across GCP and AWS.


• Experience negotiating data contracts between producer and consumer teams.


• Experience contributing to technical strategy or a roadmap for data processing infrastructure.


• Experience with Terraform, Apache Airflow (Cloud Composer), or dbt.

Why This Role Matters

Without a shared layer, each dataset gets copied into each warehouse, and every copy brings its own export pipeline, access process, and definition. Data becomes slow to reach, expensive to keep, and easy to disagree about. The lakehouse replaces those copies with one governed source that every team and every engine reads.

You will join a small team early in this work, with ownership of production systems and a direct say in the architecture, in the standards producer teams follow, and in how the Data organization uses its data.

#LI-AR2

#LI-Hybrid