Software Engineer, Backend (Infrastructure & Platform)
$170,000–$300,000 year
RemoteUnited States
United StatesRemoteFull Time$170,000–$300,000 yearTechnologyMedium
Full TimeMediumTechnology
Job Summary
Scale, reliability, and performance by attacking DB contention, memory pressure, and throughput ceilings as concurrency climbs. Build platforms other engineers build on by defining primitives, contracts, and extension points that let product teams ship on shared infrastructure instead of forking it. Own execution and orchestration by evolving how work is defined, scheduled, retried, and observed across the product without breaking existing systems. Make the system legible by providing instrumentation to see what a run did, where it went wrong, and why at scale. Handle the seams where two systems meet, including input mapping, integrations, data access, and credit accounting. Raise the bar around you by setting technical direction other teams inherit and pulling engineering standards up through design reviews and code review. This role requires 8+ years of hands-on engineering experience with a proven track record of execution. We are a cross-site engineering org split between NYC and SF, working in two-week sprints with async planning in Slack, weekly cross-functional team meetings, and Linear as the source of truth for everything we're building.
Required Qualifications
- 8+ years of hands-on engineering experience building and operating production systems at scale
- You have a proven track record of execution
- You think about platforms as products
- You know who your consumers are
- You design for their success
- You treat a confusing abstraction as a bug
- You are an empathetic communicator
- You express nuanced ideas clearly at different levels of abstraction for different audiences
- In disagreements, you prioritize curiosity over confrontation
- You make sure everyone feels heard and understood
- You love to collaborate with others to ship high quality, thoughtful features
- You care about craft
- You translate the solution into bug free, easily understandable code
- You raise the engineering bar for those around you
- Having a diversity of perspectives is important to you
- You believe that having people with different backgrounds and perspectives creates a better team and a more holistic product
- You're comfortable reasoning about distributed systems
- You're comfortable reasoning about concurrency
- You're comfortable reasoning about queuing
- You're comfortable reasoning about backpressure
- You're comfortable reasoning about failure recovery
- You're comfortable reasoning about the data models underneath them
- You're familiar with our current tech stack
- You can learn unfamiliar technologies quickly
- React
- Typescript
- Python
- Node.js
- AWS services
- Aurora (Postgres)
- Elasticache (Redis)
- Elastic Container Registry (ECR)
- ECS (Fargate)
- Lambda
- OpenSearch
- Terraform
- CircleCI
- Netlify
- Playwright
- Cloudwatch
- Datadog
- Mezmo
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
- how the shared foundations are built so that product teams extend them rather than route around them
- You'll be one of the people deciding what that foundation looks like
- You'll work on the systems every Clay product depends on
- how work gets executed and scheduled at scale
- how services hold up under concurrency
- how data is stored and served with predictable latency
Hiring someone like this?
Get your role in front of qualified candidates on Sorce.