The team is turning the incident response, on-call and status page parts of its developer tooling SaaS into a core part of the platform. Customers already pay for these features, and the product is already bringing in revenue.
The company expects AI agents to be on call by 2027. This role helps decide what gets built for that and involves talking directly with the teams who use the product during live incidents.
The company provides testing and synthetic monitoring defined as code, built on OpenTelemetry and Playwright, for developers, SRE teams and their agents, covering everything from pull request to post-mortem.
Thousands of teams use the product, including AI companies such as Mistral and resolve.ai and large engineering organisations such as LinkedIn, Citi and 1Password.
The stack is AI tools (Claude, Codex, or whichever you prefer), Vue.js, TypeScript, Go, Postgres, ClickHouse and AWS. Programming language is not a filter: full-stack engineers who work with AI should be able to pick it up.
The team ships to production every day, works in Agile rather than Scrum, keeps meetings to a minimum and values good documentation and polished products.
The team has published write-ups on working with AI agents: using the CLI for monitoring and incidents, triggering fixes when a failing check runs after deploy, porting a Go service that handles 92M messages a day with zero incidents, and running 10 to 20 coding agents at once.
Responsibilities
Shape incident response from an early product into a strategic platform area, both technically and on the product side, with wide ownership, influence and visibility.
Start with the foundation: incident management, status pages, on-call and tight integration with the rest of the product. For at least the first 6 months this is product engineering, and AI-assisted incident response follows once that foundation is in place.
Build and ship with coding agents for exploring options, scaffolding, refactoring, testing and debugging.
Talk directly with people on call, learn how responders work under pressure, and turn what you learn into the next things to build.
Pick problems worth solving. As building software gets cheap, choosing what to build is the hard part, so favour pragmatic solutions that ship quickly, test assumptions in production and add up to lasting reliability.
Own your work from the first idea through rollout and production behaviour, and join the on-call and support rotations like everyone else.
Requirements
You have built incident management, on-call, alerting or status page products and know what responders need when something breaks at 3am.
You have shipped features built with AI, not just tried it. You have taken work from zero to shipped on a comparable stack, made implementation choices that held up, and put working software in front of real users.
You have built and run production software. You handle edge cases, incidents, regressions, observability and follow-up, and you help fix things when they break.
You can lead a product area, make decisions with incomplete information, ask for input when it matters, hold clear views on what to build and why, and change them when someone makes a better case.
You work well without an office, are self-directed, and still enjoy getting to know colleagues and helping them get unstuck.
You share drafts, rough MVPs and unfinished docs early for feedback, because that suits an async team.
The team uses AI for everything, so you need to be comfortable working with it every day. Any reservations about that make this a poor fit.
Conditions
Fully remote, within the UTC-3 to UTC+3 time zones.
Working hours are 32 to 40 hours per week.
You must be able to travel to other European countries without waiting for a visa appointment, for the annual kickoff, team meetups and conferences.
The team is async-first, so most decisions happen in documents and threads rather than meetings.
Priorities change often as the team learns from customers, and customer signals count for more than instinct.
Applications from people who do not match every requirement are welcome: research suggests men apply when they meet about 60% of requirements, while women, non-binary people and POC often wait until they match far more, so if you are unsure, apply and tell us what you bring.
Benefits
Transparent salary, set with a standardised calculator that considers seniority and location.
Remote-first work with flexible hours, async working, few meetings and a transparent culture.
Join a fast-growing international remote team where your work matters and your impact is not lost in layers of bureaucracy.
Stock options.
27 days of paid vacation plus your local public holidays.
Paid sick leave and up to 14 weeks of paid parental leave.
Co-working budget or home office setup.
Annual company kickoffs.
Salary range of €88k to €107k for someone in a market with a similar cost of living to the UK or Germany, plus stock options.
Salary range of €79k to €97k for someone in a market with a similar cost of living to Spain, Poland or Ukraine, plus stock options.
Where you’d work
Fully remote
You can work from
Europe
Germany
About the company
Hidden companyCompany hidden
Industry: SaaS
Good
Your chances
Still hiring, not crowded yet, and you'd be among the first.
17 checks run
8 good signs
0 red flags
Still hiring?
11 checks
Actively hiring
StaleHiring
In its favour4
Still on the company's own careers site, checked 1 h agoModerate evidence
Found in the last 48 hours, before the big job boardsModerate evidence
Specific about the basics: pay, place, level, stack and contract all statedSlight evidence
1 moreFewer
States its salarySlight evidence
How crowded?
6 checks
Low
QuietCrowded
In its favour4
In its Early Window: not on the big job boards yetStrong evidence
Remote within Germany onlySlight evidence
Senior level: far fewer people qualifySlight evidence
1 moreFewer
Asks for ClickHouse, which fewer than 1% of open roles doSlight evidence
?
Fits Me
How well does this role fit you?
Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.