software engineer

about e2e

e2e is the open source verification layer for the agentic coding era. you describe what should work in plain language, and e2e checks it the way a user would, on web, iOS and Android. tests run in your terminal, in ci and inside coding agents such as Claude Code, Codex and Cursor. once an action passes its check, later runs replay it from cache without calling the model.

the code is Apache-2.0 and lives on GitHub, where developers from around the world report bugs, propose changes and add support for new platforms.

about the role

we’re hiring a software engineer to own the core of e2e: the agent that turns a plain-language goal into actions, the engines that drive browsers, simulators and emulators, and the cache that replays verified steps without calling the model. you’ll decide what the agent and the engines should get better at next, and then you’ll build it.

part of the job is working with companies that roll e2e out across their teams, and turning what their test suites need into framework features.

we look at your GitHub profile first, so make sure it shows work you are proud of.

what you will do

• build and improve the agent behind agent.act, agent.assert, agent.waitFor and agent.extract, and measure each change before it ships.
• make runs faster and cheaper with better caching and replay and fewer model calls per test.
• extend the web and mobile engines and the api that lets users write their own.
• work with engineering teams adopting e2e, from their first suite to running it in ci on every pull request.
• own what you build after it ships, including the bug reports.

what you need

• you take full ownership of features from idea to production, and you don’t stop when it works on your machine.
• you pick up vague problems and turn them into shipped code without needing a spec or someone to manage you.
• you ship fast without breaking things: tests, small pull requests and clear communication about trade-offs.
• you care about the user, so you notice what’s broken in the product and fix it without being asked.
• you write strong TypeScript, know Node.js well and have shipped and run production systems.
• you’ve built llm features with tool calling, and you know the trade-offs between cost, speed and accuracy.

bonus if you

• have worked on browser automation, testing infrastructure or developer tools.
• know iOS or Android internals, simulators or emulators.
• have contributed to open source projects that other developers depend on.
• have built evals for an llm feature.

if you match most of this but not all of it, apply anyway.