Checkly Senior Product Engineer at Checkly to develop incident response, on-call, and status page products into a core platform component. Build with AI coding agents and engage directly with users during incidents.
Responsibilities
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.
Qualification
You can drive a product areaYou share work earlyFULLY remote roleWhat you will hate about usWe use AI for everythingWe write more than we talkWe are leanWe ship constantly and change our mindsCustomer signals come firstHow we build with AI
Required
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.