incident.io Interview Questions: Platform Setup (2027)

42 incident.io interview questions on platform setup: severities, alert routes, on-call schedules, escalation paths, Catalog, Workflows and Terraform.

Sep 24, 2025 - 12:20
Nov 10, 2026 - 23:37
 0  75
incident.io Interview Questions: Platform Setup (2027)

incident.io engineer interview questions focus on how you set up and run the platform: severities and incident types, roles, alert sources and alert routes, on-call schedules and escalation paths, the Catalog, Workflows, status pages, post-incident follow-ups, and managing all of it as code with Terraform and the API. This page has 42 configuration-focused questions.

This page is for engineers who will own incident.io as a platform: the person who wires alerts in, builds schedules and keeps the configuration clean. If you want to practise live incident situations instead, our keeper page, scenario-based incident.io interview questions, walks through 40 situations from first page to postmortem. Both connect to the wider SRE interview questions set.

Key takeaways

  • incident.io covers incident response in Slack or Microsoft Teams, on-call, alerting, status pages, the Catalog, Workflows, post-incident work and insights.
  • Interviewers for platform-owner roles ask how things are configured, not only what they are: how an alert reaches a person, how a workflow is triggered, how ownership data stays current.
  • Configuration as code matters. incident.io publishes a Terraform provider and a public API, and teams use them to review changes.
  • Expect questions about design trade-offs: one severity scale for all teams, how many incident types, who may declare private incidents.
  • Answers here describe features in general terms. Exact menu names change, so check the incident.io docs for current details.

How this page differs from the scenario set

This pageScenario-based keeper page
How to configure incident.ioWhat to do during a live incident
Data model: severities, types, fields, CatalogResponse steps, communication, escalation decisions
Terraform, API, permissions, rolloutPostmortems and follow-up behaviour
Best for platform, SRE tooling and admin rolesBest for on-call engineers and incident leads

Freshers: core concepts (questions 1 to 12)

1. What is incident.io?

incident.io is an incident management platform. It lets teams declare and run incidents from Slack or Microsoft Teams, page on-call engineers, update status pages, track follow-ups and review incident data later.

2. What happens when someone declares an incident?

incident.io creates an incident record and a dedicated channel, asks for basic details such as name and severity, and can assign roles and run workflows that invite people or post updates.

3. What is a severity?

A severity describes the impact of an incident, for example minor, major or critical. Organisations define their own levels, and severity often drives who is paged and which workflows run.

4. What is an incident type?

An incident type groups incidents by kind, such as product, security or data. Types can carry their own custom fields, workflows and visibility rules.

5. What are incident roles?

Roles give people clear jobs during an incident. The incident lead coordinates; other roles, such as communications lead, can be added. Roles appear on the incident so everyone knows who is in charge.

6. What are custom fields?

Extra fields on an incident, like affected product or customer impact. They make reporting useful later, because you can filter incidents by the values you captured.

7. What is an incident status?

A status shows where the incident is in its lifecycle, such as investigating, fixing, monitoring or closed. Status changes can trigger workflows and appear in timelines.

8. What is the incident timeline?

A record of what happened: updates, role changes, status changes and pinned messages. It is the raw material for the post-incident review.

9. What are follow-ups?

Follow-ups are actions agreed during or after an incident. incident.io tracks them and can sync them to issue trackers such as Jira or Linear so they are not forgotten.

10. What is a status page in incident.io?

A page where you tell customers or employees about current incidents and maintenance. incident.io supports public status pages and internal ones.

11. What is a private incident?

An incident visible only to invited people. It is used for security or HR-sensitive matters where the details must not appear in public channels.

12. Why use a dedicated tool instead of a shared Slack channel?

A tool gives every incident the same structure: roles, severity, timeline, follow-ups and data for reporting. A shared channel mixes incidents and leaves no reliable record.

2 to 5 years: alerting, on-call and automation (questions 13 to 28)

13. How does an alert reach an on-call engineer in incident.io?

A monitoring tool sends an event to an alert source. Alert routes match the alert by its attributes, decide whether to create or attach to an incident and which escalation path to use. The escalation path then pages people on the relevant schedule.

14. What is an alert source?

An integration point for alerts, such as Prometheus Alertmanager, Datadog, Grafana, CloudWatch or a generic HTTP webhook. Each source parses incoming payloads into alerts with attributes.

15. What are alert attributes and why do they matter?

Attributes are values pulled from the alert payload, like service, team or environment. Routes and escalation paths use them, so a missing or misnamed attribute is a common reason nobody gets paged.

16. What is an alert route?

A rule that filters alerts and decides what to do with them: page via an escalation path, create an incident, group alerts into one incident or do nothing for low-priority noise.

17. How do you build an on-call schedule?

Define rotations with members, a handover time and a length, such as weekly. Add layers for weekday and weekend splits or follow-the-sun coverage, and allow overrides for swaps.

18. What is an escalation path?

The ordered steps for paging: who to notify first, how long to wait for an acknowledgement and who to notify next. Paths can target schedules or named users and can repeat.

19. How would you stop low-priority alerts from waking people at night?

Route them to a path that notifies during working hours only, or send them to a channel without paging. Reserve high-urgency paging for alerts that need immediate action.

20. What is the Catalog?

The Catalog stores structured data about your organisation: services, teams, owners, customers and how they relate. Alerts, workflows and incident fields can look up Catalog entries, for example to find the owning team of a service.

21. How do you keep Catalog data current?

Sync it from a source of truth, such as a Backstage catalog, a YAML file in Git or another system, using incident.io's catalog importer or API, and run the sync from CI rather than editing by hand.

22. What are Workflows?

Workflows automate steps when something happens, such as an incident being declared or its severity changing. Actions include inviting a team, posting a message, creating a ticket or updating a status page.

23. Give an example workflow you would build.

When an incident's affected service is in the Catalog with a database dependency, invite the database team's channel and page their on-call if severity is critical.

24. How do you test a new workflow safely?

Scope it to a test incident type or use conditions that only match test incidents, run it, check the actions, then widen the conditions.

25. How does incident.io connect to your issue tracker?

Through integrations that export follow-ups or create tickets in tools such as Jira, Linear or GitHub, keeping status in sync so follow-up work stays visible.

26. How do you migrate from another paging tool?

Map schedules and escalation policies, move alert integrations one service at a time, run both tools in parallel for a short period, and test pages to every responder before switching off the old tool.

27. Which permissions would you restrict?

Changing severities, schedules, workflows and integrations should be limited to owners. Viewing private incidents should be limited to invited responders. Use roles rather than giving everyone admin rights.

28. How do you get incident data into a BI tool?

Use the incident.io API or available exports to pull incidents, fields and timestamps into a warehouse, then build reports there.

Senior: platform design and governance (questions 29 to 36)

29. How would you manage incident.io configuration as code?

Use the official incident.io Terraform provider for resources such as severities, incident types, custom fields, schedules, escalation paths, workflows and catalog types. Changes go through pull requests and a plan before apply.

terraform {
  required_providers {
    incident = {
      source = "incident-io/incident"
    }
  }
}

provider "incident" {}  # reads the API key from the INCIDENT_API_KEY environment variable

30. How do you store the incident.io API key for automation?

Create a key with only the scopes the job needs, keep it in a secrets manager or CI secret, rotate it and never commit it.

31. One severity scale for everyone, or per team?

One shared scale defined by customer and business impact. Teams can add types and fields, but severity must mean the same thing across the company so reports and paging are consistent.

32. How many incident types should you create?

Few. Add a type only when it needs different fields, workflows or visibility, such as security. Too many types confuse the person declaring.

33. How do you roll incident.io out to many teams?

Start with one or two teams, agree on severities and roles, import the Catalog, connect alert sources per service, then onboard teams in waves with training and a short runbook.

34. How do you make sure every alert has an owner?

Require a service attribute on alerts, map services to teams in the Catalog and add a catch-all route that notifies a platform channel when an alert matches no team.

35. Which metrics would you report from incident.io data?

Incident count by severity and service, time to acknowledge, time to resolve, pages per on-call shift, out-of-hours pages and follow-up completion rate.

36. How do you audit configuration changes?

Keep the configuration in Terraform so Git history shows who changed what and why, and review the platform's audit log for changes made in the UI.

Scenario questions (questions 37 to 42)

37. A critical alert fired but no incident or page was created.

Check that the alert reached the alert source, that its attributes were parsed, that a route matched it and that the route points to an escalation path with people on call. A renamed label upstream is a common cause.

38. The wrong team gets paged for a service.

The Catalog ownership is probably out of date. Fix the source of truth and the sync, then check that routes use the Catalog owner instead of a hard-coded team.

39. A workflow posted an internal update to the public status page.

Remove the update, then fix the workflow conditions and add a manual approval step for public status page changes.

40. Someone edited a schedule in the UI and Terraform now wants to revert it.

Decide which version is correct. If the UI change was right, put it in code before the next apply. Then agree that schedule changes go through code or that overrides are used for swaps.

41. Security wants incidents hidden from most staff.

Use a security incident type that defaults to private, limit who can view private incidents and keep its workflows from posting in public channels.

42. Pages per shift doubled after onboarding a new team.

Group alerts by route to find noisy sources, fix thresholds with the owning team, group related alerts into one incident and move non-urgent alerts out of paging.

How to prepare

FAQ

What does an incident.io platform owner do?

They configure severities, incident types, alert routes, schedules, escalation paths, the Catalog and workflows, keep the configuration in code and help teams onboard.

How does an alert page someone in incident.io?

An alert source receives the event, an alert route matches it by attributes and sends it to an escalation path, which notifies people on the linked schedule.

Can incident.io be managed with Terraform?

Yes. incident.io publishes an official Terraform provider, incident-io/incident, for resources such as severities, custom fields, schedules, escalation paths and workflows.

What is the incident.io Catalog?

It is structured data about services, teams and other entities. Alerts and workflows use it to find owners and related systems.

Does incident.io work with Microsoft Teams?

Yes. incident.io supports running incidents in Microsoft Teams as well as Slack. Check the docs for which features differ.

How is this page different from the scenario-based incident.io questions?

This page covers configuring and governing the platform. The scenario page covers how to respond during live incidents.

Official references

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 0
Funny Funny 0
Angry Angry 0
Sad Sad 0
Wow Wow 0
Mridul I am a passionate technology enthusiast with a strong focus on DevOps, Cloud Computing, and Cybersecurity. Through my blogs at DevOps Training Institute, I aim to simplify complex concepts and share practical insights for learners and professionals. My goal is to empower readers with knowledge, hands-on tips, and industry best practices to stay ahead in the ever-evolving world of DevOps.