Back to jobs

Backend Engineer — Data Pipeline

New York · New York, United States

Live, first seen by us 76 days ago
Pay
Pay not listedSimilar roles state $127K–$189K
Work setting
On-site — work setting source
Location type: On-site
From the employer’s posting
Employment
Full-time — employment source
Employment type: Full-time
From the employer’s posting
Team
Replay › Engineering — team source
Department: Replay › Engineering
From the employer’s posting

What you’ll work on

Full posting
  • Design and ship backend systems for multi-stage, high-volume data processing

  • Define versioned contracts for manifests, artifacts, lineage, and state transitions

  • Build independent reconciliation and verification instead of trusting job success

  • Make retries, replays, backfills, and rollbacks safe and understandable

  • Turn escaped failures into fixtures, regression coverage, and release gates

From the employer’s posting
Design and ship backend systems for multi-stage, high-volume data processing
Define authoritative, versioned contracts for manifests, artifacts, lineage, and state transitions
Build independent reconciliation and verification instead of treating job success as proof of correct output
Make retries, checkpoints, partial failures, replay, backfills, migrations, and rollbacks safe and understandable
Turn escaped and recurring failures into fixtures, regression coverage, release gates, and durable recovery paths

About Replay

At Replay, we help businesses monetize their historical operating data by licensing it to the frontier AI and data labs for model training.

In the employer’s words · Read in context · Company website ↗

Apply at Replay

Posting record

Report an error
Status in our records
Live
First seen by us
Sep 6, 202676 days ago
Recorded sightings
48
Last seen by us
Nov 22, 2026
Employer says posted
Sep 4, 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–$189K is typical

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

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

Time since we first saw it

Day 76

Up longer than most. Similar jobs usually come down between day 6 and day 56.

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

Replay is hiring

3 open jobs

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

Hiring record

See how this role fits your experience

Add 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.

  • Python
  • AWS
  • DynamoDB
  • PostgreSQL
  • S3
  • Airflow
Where the posting names them
- Experience combining deterministic checks, synthetic fixtures, offline replay, model-based judges, and human review - Experience with Python, AWS, Airflow, Batch, SQS, S3, DynamoDB, PostgreSQL, or comparable systems

Your next step

Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.

Applying through Ashby

  • No account needed. “Autofill from resume” at the top of the form fills the key fields from your file.

Already applied? Track this application

Job description

View original posting ↗

About Replay

We are building the first-ever bank for enterprise data. There are over 35 million businesses in the US alone, many of which are sitting on an asset they don’t know they have. At Replay, we help businesses monetize their historical operating data by licensing it to the frontier AI and data labs for model training. Replay sits at the intersection of advancing the frontier of AI, while helping companies generate millions in growth capital without having to give up equity, take on debt, or lay off employees.

Why Join Replay Now

  • We have scaled from $0 to a multi-eight-figure run rate in a matter of months

  • We have raised from top-tier investors, including Floodgate, Afore, Ludlow, and Hustle Fund

  • We are small enough that you will carry outsized responsibility and grow as quickly as the company does

  • You will partner with and build for some of the fastest and most important companies in the world

  • You will help build a massive, category-defining business from the ground floor

The Role

We're hiring a backend engineer to make the pipeline that de-identifies sensitive enterprise data correct, replayable, operable, and safe to change.

This is not a conventional data-platform role where a successful job is enough. A pipeline can finish while silently dropping records, duplicating output, applying stale policy, losing lineage, or producing evidence that cannot establish whether a dataset is safe to release. You will own the backend systems and contracts that make those failure modes visible, preventable, and recoverable.

You will work across asynchronous orchestration, batch workers, queues, object storage, databases, many file formats, model-backed stages, deterministic verification, and human review. The role is backend-focused, but the outcome is a product and delivery promise: the team must know what ran, what changed, what remains uncertain, and what can safely happen next.

What You'll Own

  • Design and ship backend systems for multi-stage, high-volume data processing

  • Define authoritative, versioned contracts for manifests, artifacts, lineage, and state transitions

  • Make retries, checkpoints, partial failures, replay, backfills, migrations, and rollbacks safe and understandable

  • Build independent reconciliation and verification instead of treating job success as proof of correct output

  • Turn escaped and recurring failures into fixtures, regression coverage, release gates, and durable recovery paths

  • Expose trustworthy run state and safe controls to the products people use to investigate and release data

  • Diagnose production behavior across code, queues, stores, artifacts, data formats, and deployed versions

  • Improve correctness, throughput, and operating leverage without weakening privacy, security, or release confidence

  • Use AI deeply in development and in bounded verification systems, with explicit evaluation and independent checks

  • Partner with machine learning, applied science, full-stack product, platform, security, and data engineering teammates

What Success Looks Like

  • A high-risk pipeline boundary has an explicit contract, independent reconciliation, replayable coverage, and safe recovery

  • Missing, duplicated, stale, or incompatible work is detected before it becomes a customer delivery

  • Material pipeline state and release decisions are backed by queryable provenance and audit evidence

  • Recurring reruns, manual interventions, and diagnosis or recovery time decline

  • Adjacent engineers can add stages and checks through supported patterns instead of one-off scripts and implicit storage conventions

  • Pipeline changes can be rolled out, backfilled, quarantined, or reversed without delivery heroics

You Might Thrive Here If

  • You have at least three years of professional software engineering experience, including personal ownership of production backend systems

  • You are strong in asynchronous or distributed systems and can reason precisely about queues, concurrency, state, storage, idempotency, partial failure, and recovery

  • You have worked on systems where output could be materially wrong even when every service looked healthy

  • You define invariants and use reconciliation, control totals, diffs, replay, goldens, shadow paths, or independent sources to verify correctness

  • You can design versioned data and artifact contracts and migrate them safely in a live system

  • You debug from evidence across system boundaries and turn incidents into durable system improvements

  • You choose technical work based on operator and customer consequences, not architecture in isolation

  • You use modern AI engineering tools fluently, verify their output, and know when model-backed checks need deterministic guardrails and human review

  • You communicate clearly across product, ML, data, platform, security, and customer-facing teams

This Role May Not Be for You If

  • You want to focus primarily on frontend product development or visual craft

  • You treat pipeline success, uptime, latency, or a green dashboard as sufficient evidence that the output is correct

  • You prefer isolated infrastructure work without responsibility for data and delivery consequences

  • You solve partial failure primarily with retries and manual runbooks

  • You do not want AI tools to be part of your daily engineering workflow

Bonus

  • Experience with large-scale batch processing, workflow orchestration, event-driven systems, or data movement

  • Experience with schema evolution, manifests, lineage, CDC, migrations, reindexing, or backfills

  • Experience in payments, ledgers, reconciliation, claims, fraud, identity, search quality, observability, or another domain with delayed or weak ground truth

  • Experience with sensitive or multi-tenant data, least-privilege systems, auditability, quarantine, and fail-closed release paths

  • Experience combining deterministic checks, synthetic fixtures, offline replay, model-based judges, and human review

  • Experience with Python, AWS, Airflow, Batch, SQS, S3, DynamoDB, PostgreSQL, or comparable systems

Demand for Data Engineer roles

New Data Engineer postings at the employers we follow are up 13% 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 845, the most 1,344, and the latest week had 1,007.
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

New York, United States

Working pattern and location restrictions need checking in the full posting.

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.