Clay
Software Engineer, (Full Stack) Product
About this role
Clay is seeking a Software Engineer for its Performance team to solve large-scale systems challenges as the company scales rapidly. You'll optimize throughput and reliability across core infrastructure, focusing on performance observability and working with technologies like Postgres, Redis, and Node.js.
What you'll do
- Analyze systems to identify and resolve performance bottlenecks
- Create and monitor performance metrics across service components
- Advise engineering teams on scalable and performant feature design
- Address critical scalability challenges including database sharding and service decomposition
- Optimize API latency and resolve Node event loop blockages
What they're looking for
- API latency optimization
- SQL and Postgres expertise
- Query optimization and schema design
- Distributed systems and databases
- Performance profiling and monitoring
- Node.js and backend systems
- Redis experience
- AWS/ECS infrastructure knowledge
Benefits
- Work with world-class investors including Sequoia and CapitalG
- Access to free coaching in creativity and management
- Unique company culture with diverse team interests
- Exposure to high-impact growth problems at scale
- Community equity offering opportunity
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Clay
Clay builds go-to-market and developer experience infrastructure, including automation workflows, sales tools, and web experiences that help teams acquire customers and improve efficiency. The company is hiring GTM Engineers to build internal systems and automations, Web Developers to create conversion-focused experiences, and Software Engineers to improve developer tooling and AI integration.
View all jobs at ClayLikely interview questions
- Describe a time you identified and resolved a critical performance bottleneck in production—what was your approach and impact?
- How have you approached database optimization in high-throughput systems, and what tradeoffs did you consider?