SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Clay is a $5B-valued SaaS platform for go-to-market data enrichment and workflow automation, serving customers like Anthropic, Notion, Google, and Ramp. The company raised $100M in Series C funding in 2025 and crossed $100M in revenue.
As a Backend Software Engineer on the Infrastructure or Platform team, you'll own the foundational systems that every Clay product depends on: execution and scheduling at scale, concurrency handling, data storage with predictable latency, and shared infrastructure that product teams extend rather than fork.
Key responsibilities include:
- Scale, reliability, and performance: Attack database contention, memory pressure, and throughput bottlenecks as concurrency climbs. Set performance targets that hold as load grows 10x.
- Build platforms for engineers: Define primitives, contracts, and extension points that let product teams ship on shared infrastructure. Migrate existing consumers onto new platforms.
- Own execution and orchestration: Evolve how work is defined, scheduled, retried, and observed across the product without breaking existing systems.
- System observability: Provide instrumentation so customers and engineers can see what runs did, where they failed, and why at scale.
- Handle system seams: Solve the hardest problems at integration points—input mapping, data access, credit and usage accounting—that are foundational to core UX.
- Technical leadership: Set direction other teams inherit, raise engineering standards through design and code review, and leave behind systems that compound value.
Success means product teams ship independently on shared infrastructure, systems stay predictable under 10x load growth, complex long-running jobs are reliable and debuggable, core systems can evolve without breaking dependent products, and scaling decisions are made on measured evidence.
You bring 8+ years of hands-on production systems experience, with deep expertise in either (1) scale/reliability/performance—fixing database contention, memory issues, throughput ceilings under real load—or (2) platform/frameworks—building internal platforms that engineers across a company build products on. You think about platforms as products with known consumers, design for their success, and treat confusing abstractions as bugs. You combine product thinking with engineering ownership, driving end-to-end decisions about what's worth building. You communicate nuanced ideas clearly across technical levels.
About Clay
SaaS / Enterprise Software; Sales — go-to-market data enrichment and workflow automation platform.
