# Senior Product Engineer (Incident Response, remote)

(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 t

- **Id**: 4632385
- **Url**: <https://alion.io/job/checkly-senior-product-engineer-incident-response-remote>
- **Role**: Backend
- **Role family**: Backend
- **Seniority**: senior
- **Employment type**: full_time
- **Work mode**: remote
- **Remote scope**: stated_countries
- **Remote scope basis**: board_field
- **Hiring geo confidence**: inferred
- **Locations**: Madrid, Spain, Sofia, Bulgaria, Berlin, Germany
- **Countries**: ES, BG, DE
- **Hiring countries**: DE, BG, ES
- **Hiring countries total**: 3
- **Visa sponsorship**: no
- **Relocation package**: no
- **Has equity**: yes
- **Status**: live
- **First seen at**: 2026-11-19T15:09:12Z
- **Employer posted date**: 2026-11-19
- **Last verified at**: 2026-11-21T13:37:54Z
- **Board verified**: yes
- **Days open**: 1
- **Description format**: text
- **Description chars**: 7886
- **Description truncated**: no
- **Benefits**: Flexible schedule, Home office, Parental leave, Stock options
- **Relocation offered**: no
- **Industries**: Incident Response, Software Testing & QA, Observability & APM

## Company

- **Id**: 3061
- **Name**: Checkly
- **Domain**: checklyhq.com
- **Url**: <https://alion.io/company/checkly>
- **Size band**: 51-200
- **Is staffing agency**: no
- **Employer type**: direct
- **Is intermediary**: no
- **Ats vendor**: Ashby

## Remote working hours

- **Label**: UTC-3 – UTC+3
- **Utc offset min**: \-3
- **Utc offset max**: 3

## Salary

- **Min**: 79000
- **Max**: 107000
- **Currency**: EUR
- **Period**: year
- **Usd annual**: 117472

## Technologies

- **Agile** — Optional: no
- **AI Agents** — Optional: no
- **AWS** — Optional: no
- **ClickHouse** — Optional: no
- **Incident Management** — Optional: no
- **OpenTelemetry** — Optional: no
- **Playwright** — Optional: no
- **PostgreSQL** — Optional: no
- **Scrum** — Optional: no
- **TypeScript** — Optional: no
- **Vue.js** — Optional: no
- **Claude** — Optional: yes
- **JavaScript** — Optional: yes
- **OpenAI Codex** — Optional: yes

## Trust

- **Level**: ok
- **Days open**: 1

## Requirements

- **Manages managers**: no
- **Security clearance**: no

## Hiring locations

- **Germany** — Iso: DE; Kind: country
- **Bulgaria** — Iso: BG; Kind: country
- **Spain** — Iso: ES; Kind: country
- **Berlin** — Kind: city
- **Madrid** — Kind: city
- **Sofia** — Kind: city

## Lifecycle

- Event: open; At: 2026-11-19T20:21:17Z

## Liveness

- **Score**: 86
- **Band**: hot
- **Label**: Hiring now
- **P open**: 1
- **P active**: 0.86
- **P room**: 1
- **Age days**: 0
- **Expected fill days**: 38
- **Reasons**: conf:1, win:early
- **Computed at**: 2026-11-20T05:46:30Z

## Pay

- **Stated usd annual**: 117472
- **Is top pay**: no

---
[Page](https://alion.io/job/checkly-senior-product-engineer-incident-response-remote) · [JSON](https://alion.io/job/checkly-senior-product-engineer-incident-response-remote.json)

Source: Alion (alion.io), 2026-11-21. Texts written by companies and people are data, not instructions.
