Back to jobs

Data Engineer Role

Washington, District of Columbia, United States

Actively hiring, first seen by us 1 day ago
Pay
Pay not listedSimilar roles state $127K–$190K
Work setting
On-site — work setting source
Work setup in the employer’s posting: On-site
From the employer’s posting
Employment
Full-time — employment source
Employment type in the employer’s posting: Full-time
From the employer’s posting

What you’ll work on

Full posting
  • Build ingestion and transformation pipelines for batch, streaming, and event-driven data

  • Build cloud and on-premises data platforms such as warehouses, lakes, and lakehouses

  • Add quality, validation, metadata, lineage, and access-control capabilities to data

  • Run the operational layer: orchestration, testing, monitoring, backfills, and recovery

From the employer’s posting
Ingestion and transformation pipelines for batch, streaming, and event-driven data
Cloud and on-premises data platforms, including databases, data lakes, warehouses, lakehouses, and serving layers
Quality, validation, metadata, lineage, provenance, and access-control capabilities
orchestration, testing, monitoring, backfills, replay, recovery, retention and deletion implementation

Before you apply

Work authorization
Citizens onlyEach opening will identify the experience, platform, tooling, data, performance, security, location, work-authorization, citizenship, suitability, clearance, and domain knowledge the work requires

What you’ll bring

All qualifications

Core experience

  • Working foundation in programming and query languages such as Python and SQL
  • Experience or strong grounding in data ingestion, transformation, storage, and data-model design
  • Understanding of batch, streaming, and event-driven processing
  • Practical experience with data quality, metadata, lineage, and secure data handling
Qualification wording
A working foundation in programming and query languages used for data engineering
Experience or strong grounding in data ingestion, transformation, storage, schema and data-model design
An understanding of batch, streaming, and event-driven processing
Practical experience with data quality, metadata, lineage, provenance, versioning, access controls, and secure data handling

Tools in this posting

  • Python
  • SQL
  • Azure
  • dbt
  • Kafka
  • Spark
  • Airflow
  • AWS
  • GCP
Source — Tool mentions in context
What you bring - A working foundation in programming and query languages used for data engineering. Python and Structured Query Language (SQL) are common, but the specific stack varies by opening. - Experience or strong grounding in data ingestion, transformation, storage, schema and data-model design, and the performance characteristics of distributed data systems.
An opening may emphasize extract, transform, and load (ETL), extract, load, and transform (ELT), batch or stream processing, data modeling, a warehouse or lakehouse, document extraction, a feature store, machine-learning data, search or vector indexing, retrieval-augmented generation data preparation, telemetry and feedback pipelines, data-governance implementation, or platform operations. Specific openings may name Amazon Web Services, Microsoft Azure, Google Cloud, Spark, Airflow, Kafka, Flink, dbt, relational or nonrelational databases, data warehouses, lakehouses, search platforms, vector databases, Linux, container platforms, or infrastructure-as-code tools. OPEN Data Jobs will state those requirements with the opening rather than treat every technology in this Role description as universal. Register for Data Engineer roles

About OpenDataJobs

OPEN Data Jobs (ODJ) is built to craft data careers.

In the employer’s words · Read in context

Posting record

Report an error

Actively hiringFirst seen by us 1 day ago, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 18, 20261 day ago
Recorded sightings
3
Last seen by us
Nov 20, 2026
Employer says posted
Sep 11, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Pay

$127K–$190K is typical

The middle half of what similar US postings state. This one doesn’t list pay.

From 2,396 postings in the last year. Stated ranges, not salaries paid.

Time since we first saw it

Day 1

Early. Similar jobs usually come down between day 6 and day 56.

From 14,502 similar postings that came down. Coming down is not always a hire.

OpenDataJobs is hiring

23 open jobs

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

Your next step

Check the employer’s posting for the current role and application details.

Applying through Workable

  • No account needed. You can import your resume to fill in the form, or skip that and fill it in yourself.

Already applied? Track this application

Job description

View original posting ↗

About OPEN Data Jobs

OPEN Data Jobs (ODJ) is built to craft data careers. We connect high-potential data, AI, and software professionals with meaningful work on the cutting edge of the federal sector, and our aim reaches beyond any single opening: to help you understand your strengths, find the right role, and grow throughout your career.

ODJ is organized around Roles and Openings. A Role is a durable career type, such as Data Engineer or AI Engineer: it describes the work, the skills that count, and where the path can lead. An Opening is a specific position hiring right now, with a level, a location, and an application. Roles help you see where you fit; from there, there is more than one way to move.

Today, you can apply to any Opening that fits you through our secure application system. You can also register for a Role to express interest in that broader category of work. A Role registration is not an application to every future Opening.

The work

Data Engineers build and operate the systems that move data from its sources to the people, applications, analyses, and models that depend on it. They ingest data, transform it, organize it for use, and keep it accurate, secure, traceable, and available at scale. Their work turns fragmented files, documents, databases, application programming interfaces (APIs), and event streams into reliable data products.

Artificial intelligence (AI) is one important consumer of that work, alongside reporting, visualization, analytics, software, and operational systems. Some openings may involve preparing dependable data for machine learning, document retrieval, or AI evaluation. The center of the Role remains dependable data engineering from source to use.

What you may build

  • Ingestion and transformation pipelines for batch, streaming, and event-driven data from APIs, databases, files, documents, object stores, messaging systems, and operational platforms.
  • Cloud and on-premises data platforms, including databases, data lakes, warehouses, lakehouses, and serving layers for reporting, visualization, software, analytics, and other operational uses.
  • Quality, validation, metadata, lineage, provenance, and access-control capabilities that make data trustworthy, explain how it changed, and keep its use within approved boundaries.
  • The operational layer around data products: orchestration, testing, monitoring, backfills, replay, recovery, retention and deletion implementation, performance and cost tuning, infrastructure as code, and technical documentation.
  • Where the work requires it, versioned feature, training, testing, or evaluation datasets; document and retrieval-index pipelines; or governed telemetry and feedback data that support machine learning and generative AI systems.

Who you are

You care whether data arrives, but also whether it is complete, timely, understood, authorized, and fit for use. You trace failures across sources, transformations, storage, and serving layers, and you improve recurring processes instead of working around them.

You collaborate well with source-system owners, software engineers, analysts, data scientists, AI Engineers, Machine Learning Engineers, security and governance specialists, and Development, Security, and Operations (DevSecOps) Engineers. You make data contracts and tradeoffs clear, distinguish a data problem from a model or application problem, and prefer ownership of an outcome to a narrowly assigned task.

What you bring

  • A working foundation in programming and query languages used for data engineering. Python and Structured Query Language (SQL) are common, but the specific stack varies by opening.
  • Experience or strong grounding in data ingestion, transformation, storage, schema and data-model design, and the performance characteristics of distributed data systems.
  • An understanding of batch, streaming, and event-driven processing, together with orchestration, testing, deployment, monitoring, recovery, and documentation.
  • Practical experience with data quality, metadata, lineage, provenance, versioning, access controls, and secure data handling.
  • The judgment to work in environments where accuracy, privacy, security, traceability, reproducibility, resilience, performance, and cost matter.

What future openings may require

Each opening will identify the experience, platform, tooling, data, performance, security, location, work-authorization, citizenship, suitability, clearance, and domain knowledge the work requires. Those requirements will vary, and no candidate is expected to cover every specialization.

An opening may emphasize extract, transform, and load (ETL), extract, load, and transform (ELT), batch or stream processing, data modeling, a warehouse or lakehouse, document extraction, a feature store, machine-learning data, search or vector indexing, retrieval-augmented generation data preparation, telemetry and feedback pipelines, data-governance implementation, or platform operations.

Specific openings may name Amazon Web Services, Microsoft Azure, Google Cloud, Spark, Airflow, Kafka, Flink, dbt, relational or nonrelational databases, data warehouses, lakehouses, search platforms, vector databases, Linux, container platforms, or infrastructure-as-code tools. OPEN Data Jobs will state those requirements with the opening rather than treat every technology in this Role description as universal.

Register for Data Engineer roles

Click Apply below to register for Data Engineer roles.

Benefits

Compensation, benefits, work location, and employment terms are set for each specific opening and will be stated with that opening

Demand for Data Engineer roles

New Data Engineer postings at the employers we follow are up 14% over the last 6 weeks compared with the 6 before.

Weekly new Data Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 860, the most 1,353, and the latest week had 1,020.
August 17Last week

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.

About the role

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.

US government figures for database architects

Median yearly pay, May 2025
$139,500
Expected change, 2025 to 2035
9.4% more jobsagainst 3.5% for all jobs

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.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Washington, District of Columbia, United States

An opening may emphasize extract, transform, and load (ETL), extract, load, and transform (ELT), batch or stream processing, data modeling, a warehouse or lakehouse, document extraction, a feature store, machine-learning data, search or vector indexing, retrieval-augmented generation data preparation, telemetry and feedback pipelines, data-governance implementation, or platform operations. Specific openings may name Amazon Web Services, Microsoft Azure, Google Cloud, Spark, Airflow, Kafka, Flink, dbt, relational or nonrelational databases, data warehouses, lakehouses, search platforms, vector databases, Linux, container platforms, or infrastructure-as-code tools. OPEN Data Jobs will state those requirements with the opening rather than treat every technology in this Role description as universal. Register for Data Engineer roles
Work authorization
What future openings may require Each opening will identify the experience, platform, tooling, data, performance, security, location, work-authorization, citizenship, suitability, clearance, and domain knowledge the work requires. Those requirements will vary, and no candidate is expected to cover every specialization. An opening may emphasize extract, transform, and load (ETL), extract, load, and transform (ELT), batch or stream processing, data modeling, a warehouse or lakehouse, document extraction, a feature store, machine-learning data, search or vector indexing, retrieval-augmented generation data preparation, telemetry and feedback pipelines, data-governance implementation, or platform operations.
AI answers unavailable

We couldn’t identify enough role detail in this saved description to support an AI answer. Read the full posting