Checkly Senior Product Engineer role focused on building AI-powered DevTools for software reliability. Engage directly with users to understand their workflows and improve product reliability through pragmatic solutions.
Responsibilities
Build and ship with AI
Talk to our users
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 focus on real developer pain: flaky tests and flaky checks, unclear failures, noisy alerts. 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 shaping the initial idea, through implementation and rollout, to watching how it behaves in production. You will take part in on-call and help support customers when things don’t work as expected.
What you should have
Qualification
You can hold a product conversationFULLY 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 first
Required
You can hold a product conversation, not just a technical one. You can look at a customer problem and reason about whether the thing we are about to build actually solves it.
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.
FULLY remote role, within the UTC-3 to UTC+3 time zones. You need to be able to travel to (other) European countries without having to wait for a visa appointment, for our annual kickoff, a team meetup or a conference.
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.
