Skills this job asks for
Testing / QAVueJavaScriptTypeScriptPostgreSQLAWSAgile
Add your CV (free) to see which of these your CV is missing.
Where you can work from
Location not specified
The listing does not say where you can work from. Missing information is not the same as worldwide: check before applying.
The company's headquarters is not the same as where you may work from. Visa sponsorship only matters if you would relocate; see below.
Visa sponsorship, if you would relocate
Sponsorship verdict
No sponsorship evidence yet
No government record and no wording either way. Not a refusal: ask the recruiter.
-
?
No government sponsor record hereThis employer posted directly and does not match a government sponsor register.
-
?
The posting doesn’t mention sponsorshipSilence isn’t a refusal — ask the recruiter before investing much time.
-
?
No salary bar for this routeH-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area.
-
✓
Confirmed live todayWhen a source last listed this job as open.
Details and sources
- No salary bar for this route
- H-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area. Cap-subject employers enter a lottery weighted by wage level. Source: https://www.federalregister.gov/documents/2025/12/29/2025-23853/weighted-selection-process-for-registrants-and-petitioners-seeking-to-file-cap-subject-h-1b, rules effective 2026-02-27.
US H-1B: cap-subject employers enter a lottery weighted by wage level — Level I gets 1 entry, Level IV gets 4 (DHS projected selection odds ≈15% at Level I to ≈61% at Level IV). Universities and non-profit research employers are cap-exempt. The $100,000 fee for new petitions from abroad is currently blocked by a court order (appeal pending).
A verdict summarises public evidence. It is not legal advice and never a guarantee: the employer and the immigration authority decide. Sign in to factor in where you can already work.
Before you apply
Sponsorship unknown
No register record and no sponsorship wording in the posting. Worth asking the employer before investing significant time.
These come from the posting’s own wording. Read the original listing to confirm. See better-fit alternatives →
About the role
(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 of teams, from AI companies like Mistral and resolve.ai to large engineering organizations like LinkedIn, Citi and 1Password, build with us. In 2024 we raised $20M in Series B 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 ju
View original listing ↗