incident.io
As of 1 November 2026, incident.io has 34 open roles (12 new in 30 days), its sales team is hiring most, and its postings name Pylon, Terraform and CircleCI as the tools the team works in.
As of 1 November 2026 · refreshed daily · counts move as websites, DNS and career sites are re-read.
- Headquarters
- , , United States
- Employees
- 51-200 employees (linkedin)
- Sells to
- software engineering teams, sre teams, fast-growing companies
- Certifications on site
- SOC 2
- Site languages
- EN
- Career system
- Ashby
incident.io in one screen
Read from incident.io: what the company does, the customers it names, the buyers we can actually see, and the companies that sell the same thing.
incident.io is a software reliability platform that investigates, responds to and prevents incidents for software engineering and SRE teams. Its offerings include on-call management, investigations with agentic root cause analysis, response, status pages, and integrations with Slack and Microsoft Teams. It is used by large companies such as Zendesk, Netflix, Etsy, Airbnb and Fin.
Named on the site: software engineering teams, sre teams, fast-growing companies, fast growing companies.
Seen in buyers' own postings: technology & software, business & finance services, utilities & infrastructure; mostly 11-50 employees and 51-200 employees; United States (17) and United Kingdom (9).
Nearest companies by what they do, sell and whom they serve, 51+ employees. 582 scored.
Companies whose own job postings name incident.io as the system their team works in. Ideal-customer examples, not a reference list from the vendor.
What incident.io says it runs
Tools named in the company's own postings as the team's systems, with the sentence that says so. What the website and DNS show is listed separately.
Vendors whose code loads on incident.io or whose records sit in its DNS. Page plumbing (libraries, fonts, consent banners) is left out.
34 open roles, 27 opened in 90 days
Read hourly from the company's career system. Open roles and new roles in the last 30 days, by team. Companies hiring sales in United States →
| open · new 30 d | |
|---|---|
| Sales | 14 · 5 |
| Customer service & success | 11 · 6 |
| Engineering (non-software) | 1 · 0 |
| Human resources | 1 · 1 |
| Software engineering | 1 · 0 |
What is changing, read from the postings
Intents are events the employer states about itself, each with the sentence and the posting it came from.
No change signals read in the current postings.
Sales, marketing and IT leaders by function. Add incident.io to a monitor and get a webhook when a role opens, a tool appears or a signal is read.
Start free, no card. The first 20 are above; e-mails are verified at the mail server when you open them.
Companies like incident.io
Nearest by what they do, what they sell and whom they sell to, 51+ employees. 6 of 582 scored.
From the company's own website
Quote the sentence with the date and the link. The numbers change daily; the link always shows the current ones.
incident.io (, United States, 51-200 employees) has 34 open roles, 12 new in 30 days, and names 14 tools in its postings. (Breaknorm, 1 November 2026, https://breaknorm.co/company/incident.io)
Read from the source, not self-reported
Every number on this page can be traced to a page we crawled or a posting we read. Full methodology →
- ProfileBuilt from incident.io: summary, offerings, customers, certifications and contact points are extracted from its pages, with a confidence score per field.
- HiringRead hourly from the company's Ashby career site; reposts collapse into one record.
- Tech stackTools the employer's own text names as the team's systems, with the quote; website scripts counted separately.
- HeadcountLinkedIn where known, otherwise estimated from the site.
incident.io: questions
Does incident.io use Pylon?
Yes, by the company's own words: 2 postings name it, first seen 2026-09-10, in the customer service & success team.
Is incident.io hiring?
34 open roles as of 1 November 2026, 12 opened in the last 30 days and 0 closed. The largest team hiring is sales.
Where does this profile come from?
From incident.io itself: we crawled it on 2026-08-14, built the profile on 2026-08-16, and read its career site (Ashby) hourly since. Headcount is from LinkedIn.
Who should I write to at incident.io?
The people are behind the login: decision makers by function, verified at the mail server when you open them. 1 public role addresses from the site are there too.
Get this company your way
The same data as a search, over MCP and the API, as bulk files, or pushed to you as it changes.
incident.io and 41.5M more,
read from the source
Look up any company by domain, with its hiring, stack and signals. Start free, no card.