ITIL and ITSM Interview Questions: 20 Questions With Model Answers

Interviews for service desk, service management and IT operations roles tend to test two things: whether you know the vocabulary and whether you can apply it. Use the model answers below as a pattern, not a script. Whenever you can, add a short example from your own experience; real examples are more convincing than definitions.

How to Answer

  • Start with a one-sentence definition, then a short example.
  • Keep answers to about thirty to sixty seconds.
  • If you have not done something, say so, and explain how you would approach it.
  • Link answers to outcomes: user impact, risk, cost, learning.

Concept Questions

1. What is ITIL, and why do organisations use it?

ITIL is a framework of good practice for IT service management. Organisations use it to get shared vocabulary and proven practices that help them deliver reliable services and value to users. It is guidance to adapt, not a rigid standard.

2. What is the ITIL service value system?

It shows how all the components of an organisation work together to turn opportunity and demand into value. It has five components: guiding principles, governance, the service value chain, practices and continual improvement.

3. Name the seven guiding principles.

Focus on value; start where you are; progress iteratively with feedback; collaborate and promote visibility; think and work holistically; keep it simple and practical; optimize and automate. I try to apply them to real decisions, for example removing an approval step that never rejects anything.

4. What are the four dimensions of service management?

Organisations and people; information and technology; partners and suppliers; and value streams and processes. They remind us that a service change involves more than technology.

5. What are utility and warranty?

Utility is what the service does, being fit for purpose. Warranty is how reliably it does it, being fit for use: availability, capacity, security and continuity. A service needs both to create value.

Practice Questions

6. What is the difference between an incident, a problem and a service request?

An incident is an unplanned interruption or reduction in quality; the goal is to restore service. A problem is the cause of one or more incidents; the goal is to remove the cause. A service request is a routine, pre-agreed ask, such as new software. Example: users cannot log in (incident); the disk filled up because logs were never rotated (problem); someone asks for a new mouse (request).

7. How do you prioritise incidents?

By impact and urgency. Impact is how many people or how much of the business is affected; urgency is how quickly it must be fixed. The combination gives a priority that drives response and resolution targets. I also check for known workarounds and whether a major incident procedure applies.

8. What is a major incident, and how is it handled?

It is an incident with significant business impact that needs a faster, coordinated response. It usually has an incident manager, a technical lead and a communications lead, regular updates to stakeholders and a post-incident review.

9. What is a known error and a workaround?

A known error is a problem that has been analysed and has a documented cause and workaround, but is not yet permanently fixed. A workaround reduces or removes the impact until a permanent solution is available. We share known errors with the service desk through the knowledge base.

10. Explain the three change types.

Standard changes are low risk, well understood and pre-authorised. Normal changes need assessment and authorisation based on risk. Emergency changes are urgent, usually to fix a major incident, and follow a fast-track approval. Converting frequent low-risk normal changes into standard ones frees up time for risky changes.

11. What is a CAB, and is it mandatory?

A change advisory board advises on high-risk changes. It is not mandatory. ITIL 4 recommends delegating authority to the lowest level that can judge the risk, and using automation and peer review for frequent low-risk changes.

12. What is the difference between an SLA, an OLA and an underpinning contract?

An SLA is between the provider and customer. An OLA is between internal teams. An underpinning contract is with an external supplier. They must align: a four-hour resolution promise needs matching internal and supplier commitments.

13. What is a CMDB and why does it matter?

It is a store of configuration items, their attributes and relationships. It speeds up diagnosis, helps assess change impact and links incidents to the things that failed. It must be accurate, so I would start with critical services and use discovery and change integration.

14. What is the difference between release and deployment?

Deployment moves a component into an environment; release makes a feature available to users. With feature flags, you can deploy code on Tuesday and release it to customers on Thursday.

Measurement and Improvement Questions

15. Which KPIs would you track for a service desk?

A balance: speed (time to respond and resolve), quality (first-contact resolution, reopen rate), experience (CSAT) and efficiency (self-service share, cost per ticket). I would avoid rewarding any single measure alone, since it invites gaming.

16. How do you calculate first-contact resolution?

Contacts resolved at first contact divided by total contacts, times 100. For example, 132 of 300 contacts gives 44%. I would compare that with our own trend and with the type of work we handle.

17. What is the continual improvement model?

A seven-step approach: what is the vision, where are we now, where do we want to be, how do we get there, take action, did we get there, and how do we keep the momentum going. I stress taking a baseline first and checking results afterwards.

Scenario Questions

18. Users report that email is down. What do you do?

Log the incident and check how many users are affected to set priority. Search for related incidents and recent changes, check monitoring and the knowledge base, and escalate to the messaging team if needed. Communicate status to users, apply a fix or workaround, confirm restoration with a sample of users and record the resolution. Afterwards, check whether a problem record is needed.

19. The same incident keeps happening. What would you do?

Raise a problem record, gather the incident data and look for patterns using techniques such as 5 Whys or Pareto analysis. Document a workaround and share it as a known error, then raise a change for a permanent fix. I would measure repeat incidents to confirm it worked.

20. How would you introduce ITIL practices in a team that sees them as bureaucracy?

I would start with a pain point they recognise, such as lost requests, and introduce the lightest practice that solves it. I would involve the team in design, pilot it, remove steps that add no value and share results. The aim is visible benefit, not a heavy process.

Questions to Ask the Interviewer

  • Which practices does the team use today, and which are you trying to improve?
  • Which tool do you use, and how do you measure success?
  • How do you handle major incidents and post-incident reviews?
  • What does the first ninety days look like in this role?

Common Mistakes

  • Reciting definitions without an example.
  • Claiming ITIL experience you cannot explain in detail.
  • Saying “ITIL is just a lot of process” in the interview.
  • Ignoring the user’s perspective in scenario answers.
Key takeaways
  • Define, then give a short example; real experience beats recitation.
  • Know the distinctions: incident vs problem vs request, release vs deployment, SLA vs OLA vs underpinning contract.
  • Be ready to calculate KPIs such as first-contact resolution and MTTR.
  • In scenario questions, show structure: log, prioritise, diagnose, communicate, resolve, learn.

Related Lessons