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 an open source developer to own parts of the e2e framework. the work happens in public on GitHub, in the issues, the pull requests and the releases. you’ll decide what to fix next as much as how to fix it, and all of your code ships in a public repository.

e2e is written in TypeScript. the web engine drives browsers through Playwright, the mobile engine drives iOS simulators and Android emulators through agent-device, and coding agents use e2e through its MCP server.

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

what you will do

• design and ship framework features and fixes, from the first issue to the release notes.
• review and merge pull requests from contributors, and answer issues and questions on GitHub and Discord.
• improve how e2e works inside coding agents: the MCP server, the skill that e2e init installs and the trace a failed test leaves behind.
• find and fix what makes runs slow or unreliable on web, iOS and Android.
• write the docs, examples and migration guides that ship with each change.

what you need

• you have real ownership of something in open source: you’ve shipped features, reviewed pull requests and kept a project alive after the hype.
• you pick up a vague issue and turn it into a merged pull request without waiting to be told what to do.
• you work in public: clear commits, good issues, docs you write yourself and decisions you explain to strangers.
• you care about the people using the code, so you read their issues and fix what actually hurts.
• you take a feature from idea to release yourself, and you don’t stop when it works on your machine.
• you ship fast without breaking things, with tests, small pull requests and clear notes on the trade-offs you made.
• you write strong TypeScript and know Node.js well.
• you’ve worked with browser automation such as Playwright, Puppeteer or the Chrome DevTools Protocol.

bonus if you

• have built a test runner, testing framework or cli that other developers use.
• know iOS or Android tooling: simulators, emulators, XCUITest, UIAutomator or React Native.
• have built with llms and agents: tool calling, MCP or the AI SDK.
• write or speak about the tools you build.

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