Platform Engineer

At its core, Replay was founded to help founders. We started by supporting startups through shutting down, but we have since expanded into unlocking a new revenue stream for all types of businesses.

In 2025, we had a unique insight: the data every company generates each day through collaboration, communication, and building is some of the most valuable training data in the world. Public and synthetic data can only get frontier models so far, so the next generation of model progress depends on real, proprietary data grounded in how actual businesses operate. We are a primary source of it, partnering directly with the frontier AI labs building what comes next.

• 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

Replay operates customer-facing SaaS products, connector and ingestion services, asynchronous workers, high-volume data pipelines, model-backed systems, review tools, and customer-delivery paths. These workloads have different shapes, but they need a coherent foundation for infrastructure, delivery, observability, recovery, access, and cost.

You will build and operate the shared platform that lets our product, data, and AI teams ship reliable, secure, observable, and cost-aware systems without manual infrastructure work or operational risk growing linearly. You will write software and infrastructure, improve real engineering workflows, lead through incidents, and create paved roads teams can use without waiting on you.

This is not a deployment-operator or internal-IT role. Product, data, and ML teams remain responsible for the systems they build. You will give them the runtime, delivery, visibility, recovery, and operating patterns to own those systems well. You will partner closely with our Security Lead, but you will not be expected to run the entire security or compliance program.

Create a small set of supported patterns for customer-facing services, connectors, scheduled jobs, data-processing pipelines, model-backed workloads, and evaluation runs. Define the contracts for environments, compute, state, networking, delivery, secrets, telemetry, failure handling, and recovery without forcing every workload into an inappropriate stack.

Make it straightforward for an engineer to create an environment, ship a safe change, understand a failed deploy or job, get the right access, recover a system, and know who owns the result. Build useful self-service and escape hatches while making unsupported paths and exceptions explicit.

Connect service, queue, job, pipeline, and model telemetry to the outcome that matters. Establish practical objectives, alerts, incident mechanics, replay and recovery paths, and reviews that remove recurring failure classes instead of only documenting them.

Expose cost and capacity in workload-relevant units, then improve them without hiding reliability, security, quality, or developer time. Work with Security to implement least privilege, secrets, logging, backup, deployment, and audit controls whose evidence comes from the systems that actually enforce them.

• Establish Replay's current platform, workload, reliability, ownership, toil, recovery, cost, and technical-control baseline

• Build reusable infrastructure-as-code modules, runtime templates, deployment workflows, environment contracts, and operational tooling

• Create supported paths for customer-facing services, asynchronous and batch jobs, data pipelines, and model-backed workloads

• Improve deploy safety, workload visibility, backup and recovery, incident response, replay, rollback, and durable remediation

• Work with engineering teams to define useful service and pipeline objectives, ownership, escalation, and recovery paths

• Build self-service for common infrastructure, environment, access, deploy, debugging, and recovery work without…