Skip to content
Sunset

Backend Engineer — Data Pipeline

New YorkOnsite · United States
FullTime · Replay
POSTED 4 SEPTVERIFIED 22H AGO
Apply Ask
Role
76 days opentrue age
Posted 4 Sept
Payats field
$200kposted
● 0% vs market median $200k
$175k$235k
Market p25–p75
$175k–$235k
New York · n=75 · 365d to 19 Nov
CompanySunset →
12open roles
Opened · 30d
+0
Closed · 30d
−0
10d of snapshots · 30d window
Market
3,458open · Backend
Opened · 7d
+2577% of open
All backend
8,048open
All tracked boards · live 20 Nov · n=3,458
Distributed systems

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

Source · SunsetFirst seen 2 NovOriginal ↗