(Fully remote, async-first, DevTools SaaS, 32-40h/week, time zones: UTC-3 to UTC+3)
Help turn Checkly's incident response, on-call and status pages from a young product that customers already pay for into a core part of our platform. In 2027 agents will be on call and we want to be ready for that. You'll shape what we build in 2027, build it with AI coding agents, and talk directly to the teams who use it in the middle of an incident.
The best engineering teams don't wait for users to tell them something's broken. They build resilient, reliable systems to catch it first: in the pull request, in staging, or production at 3am, before a single customer notices. That instinct is Checkly's whole reason to exist.
Checkly gives developers, SRE teams and their agents the tools to own reliability the way they own their code: testing and synthetic monitoring defined as code, built on OpenTelemetry and Playwright. From pull request to post-mortem, in one place.
This role is about the post-mortem end of that line. We've built incident management, status pages and on-call into Checkly, and it's already bringing in revenue. Now we want to drive it strategically. Figure out together with us how to evolve incident management with clear signals and with agents being on call.
Thousands https://www.checklyhq.com/customers/ of teams, from AI companies like Mistral and resolve.ai http://resolve.ai to large engineering organizations like LinkedIn, Citi and 1Password, build with us. In 2024 we raised $20M in Series B https://www.checklyhq.com/blog/announcing-20m-to-enable-engineers-to-detect-and-r/ funding from Balderton, CRV and Accel.
Our stack is AI (Claude, Codex, use what you like best), Vue.js, TypeScript, Go, Postgres, ClickHouse and AWS. We don't filter on programming language. If you ship full-stack with AI, you'll pick ours up. We ship to prod all day, every day, practice Agile (not scrum), keep meetings low and take pride in good documentation and good looking products.
WHAT YOU'LL DO
•Shape a product from early stage to strategic. You'll be involved early in how we build incident response out as a platform, technically and on the product side. That means a lot of ownership, influence and visibility.
•Build the foundation first. Incident management, status pages, on-call, and tight integration with the rest of Checkly. For at least the first six months this is solid product engineering. AI-assisted incident response comes once the foundation is in place.
•Build and ship with AI. Coding agents are how you work: exploring solutions, scaffolding, refactoring, testing and debugging.
•Talk to the people on call. You'll be directly involved in customer conversations. You'll learn how responders work under pressure and turn that into what we build next.
•Find the right problems to solve. In a world where the cost of building software trends to zero, the hard part is picking what to build. You will favour pragmatic solutions that ship quickly, validate assumptions in production, and compound into long-term reliability improvements.
•Own your work end to end. From the first idea to rollout to how it behaves in production. You'll join the on-call and support rotations like everyone else.
WHAT YOU SHOULD HAVE
•You've built incident management, on-call, alerting or status page products before. You know what responders need from a tool when something breaks at 3am.
•You have shipped features with AI, not just experimented with them. You have taken work from zero to shipped with a comparable stack, made implementation decisions that held up, and put things in front of real users.
•You have built and run production software. You know the realities of operating software that people depend on: edge cases, incidents, regressions, and the need for observability and follow-up. You are not surprised when things break. You help fix them.
•You can drive a product area, not just pick up tickets. You make decisions without perfect information, and you ask for input when it counts. You have opinions about what we should build and why, and you change your mind when someone makes a better case.
•You work well without an office around you. You are autonomous and self-motivated in a remote setup, and you still enjoy getting to know your colleagues and helping other people get unstuck.
•You share work early. Drafts, rough MVPs and half-finished docs go out for feedback before they’re polished. In an async team, that’s how good ideas get better fast.
•FULLY remote role, within the UTC-3 to UTC+3 time zones. You need to be able to travel to (other) European countries without waiting for a visa appointment, for our annual kickoff, team meetups or conferences.
WHAT YOU WILL HATE ABOUT US
We would rather tell you now than have you find out in month two.
•We use AI for everything, and we mean everything. AI skepticism is not a thing here. If you have the slightest hesitation about working with AI every day, this is not the place for you, and that is completely fine.
•We write more than we talk. We are async-first, so a lot of decisions happen in documents and threads, not meetings. If you do your best thinking out loud in a room full of people, you will miss it here.
•We are lean, so you own the unglamorous parts too. There is no separate QA team, no ops layer to hand things off to, and you are on the support rotation and the on-call rotation like everyone else.
•We ship constantly and change our minds. Priorities move as we learn from customers. If you need long, stable planning cycles, this will feel chaotic.
•Customer signals come first, and most of the time they matter more than your instinct. We build what customers actually want, not the clever thing we dreamed up.
HOW WE BUILD WITH AI
Don’t take our word for it. Here’s what that looks like in practice, written by the team:
•Checkly and the agentic software layer https://checklyhq.com/blog/the-agentic-software-layer: Hannes on why the CLI is how agents use software, including running monitoring and incidents.
•Your software factory stops at deploy https://checklyhq.com/blog/your-software-factory-stops-at-deploy: Stefan on what happens after deploy, when a failing check should kick off the fix.
•We let AI agents rewrite a 92M-message-a-day service in Go https://checklyhq.com/blog/agentic-rewrite-nodejs-to-go: Eddie on porting a core service with an agent, and zero incidents.
•Why I built my own AI agent orchestration tool https://checklyhq.com/blog/agentic-crafting-table-ai-agent-orchestration: Immanuel on running 10 to 20 coding agents at once.
BENEFITS
•Transparent salary because your salary shouldn't be dictated by how good a negotiator you are. (more info below)
•Remote-first https://blog.checklyhq.com/we-scored-10-5-on-gitlabs-12-steps-to-better-remote-test/, flexible work hours https://app.notion.com/p/Remote-first-75c4fb08dc49400cabee6a3a9b827cc5?pvs=21, async-first https://app.notion.com/p/Async-by-default-Async-1-0-Checkly-b9dd37bec51d436bae6635ffce8c6730?pvs=21 (low meeting, high productivity) and transparent culture https://app.notion.com/p/Meetings-communication-transparency-b130664febf94ae9b320bd4a78370f2e?pvs=21
•Become part of a fast-growing, international, and remote team where your work matters, and your impact won't get lost in layers of bureaucracy.
•Stock options
•27 days of paid vacation + your local public holidays
•Paid sick leave & up to 14 weeks of paid parental leave
•Co-working budget or home office setup
•Annual company kickoffs
Find out more here https://app.notion.com/p/Benefits-Perks-ad474bec3a5d4d17bfbb43ebae3fec9c?pvs=21.
WHAT WE PAY
Fair, competitive, and transparent pay is very important for us. Therefore we work with a standardized salary calculator https://pay.checklyhq.com/ that includes several factors such as seniority level as well as location.
For this role, the range is
•€88k - €107k for someone in a similar cost of market as UK, Germany etc, + stock options
•€79k - €97k for someone in a similar cost of market as Spain, Poland, Ukraine etc, + stock options
APPLY
If this sounds interesting, please apply! Studies by several different sources have shown that on average men will apply for a job if they meet 60% of the application requirements. Women, non-binary people and POC will seek to match a much higher percentage of requirements before applying. If you're not sure you're the right fit, apply anyway and let us know what you bring to the table. We'd love to hear from you!
We're all about being transparent and setting clear expectations. That's why we've put together our hiring playbook https://app.notion.com/p/Checkly-Hiring-Playbook-54bc05178d3b4118a15effe885f96d1a?pvs=21 and open-sourced our employee handbook https://app.notion.com/p/Checkly-s-Employee-Handbook-f262e36a64d641af8588a1c09bc0ff48?pvs=21. There you'll find a sneak peek of who we are, how we work and what you can expect in our hiring process.