About TestSprite

Be the technical lead for the AI agents that test software, whether people or AI coding tools wrote it. You'll own the architecture, write the hardest code, and help decide what we build next.

TestSprite builds AI agents that test software end to end. A developer or an AI coding agent points us at an app. Our agents explore it, write a test plan, run it in real browsers and against APIs, and report what broke and why.

Code now ships faster than anyone can review it, and we're building the layer that checks it. TestSprite plugs into Cursor, Windsurf, Claude Code and other coding agents through our MCP server and CLI, and it runs in CI. More than 100,000 users rely on TestSprite, from solo developers to enterprise engineering teams. We're backed by Trilogy Equity Partners, Techstars, Hat-Trick Capital, Jinqiu Capital, MiraclePlus, Baidu Ventures and EdgeCase Capital Partners.

The role

This is a hands-on IC role with tech-lead scope. You'll own the architecture of our agent platform, from how tests get planned to how they run, get judged and repair themselves. You'll set the technical bar for the team and work directly with the founders.

What we're looking for

  • 5+ years building production software
  • Deep understanding of AI and LLMs
  • Strong algorithms and CS fundamentals
  • Strong system architecture skills
  • Strong product sense
  • You iterate fast
  • Great technical taste
  • Passion for AI developer tools
  • Experience with software testing

Compensation

Top-of-market pay and meaningful equity.

How to apply

Apply here or email hiring@testsprite.com directly. Include a few sentences on the hardest AI system you've built and what you learned from it. We read that note before the resume.

TestSprite is an equal opportunity employer.

Apply Now

Please upload a document (PDF preferred) that walks us through one or more AI-related projects you’ve worked on. We’re not looking for a list of technologies — we want to understand how you think and make decisions as an engineer.

Specifically, please cover:

  • What the system was designed to do and why it mattered
  • Your role and what you were personally responsible for
  • Where you chose to use existing tools, frameworks, or off-the-shelf solutions — and why
  • Where you chose to build something from scratch — and why
  • What tradeoffs you made and what you’d do differently in hindsight

A candidate who can clearly articulate these decisions is exactly who we’re looking for. There is no length requirement — clarity and depth matter more than volume.