I have been involved in hiring decisions for IT service management roles across several organisations over the past decade. The patterns I have learned about what predicts success in these roles are different from what most candidates seem to think the hiring criteria are. The candidates who do well in interviews and subsequently in the roles share specific characteristics that the standard hiring advice doesn't always emphasize.
This is the honest version of what I actually look for, in case it helps anyone preparing for ITSM interviews.
Specific examples beat general capability claims
The single most important thing in interview performance is the candidate's ability to discuss specific situations in detail. Not "I have experience with incident management" but "in March 2024 we had an incident where the payment processor went down for forty minutes during peak shopping hours and here's specifically what we did and what I learned from it."
The specific examples reveal whether the candidate has actually done the work or has only generic familiarity with how the work is supposed to be done. Candidates with actual experience can describe the messy details — what went wrong, what decisions were made under pressure, what was learned that changed subsequent practice. Candidates without actual experience tend to fall back on framework descriptions or general statements that don't reveal real engagement.
For candidates preparing for ITSM interviews, the most useful preparation is to develop a portfolio of specific situations you can discuss in detail. Pick five or six situations from your actual work. Be ready to describe each one with specifics — what happened, what you did, what worked, what didn't, what you learned. The specifics are much more compelling than rehearsed answers to generic interview questions.
Honest engagement with what didn't work
I pay particular attention to how candidates discuss things that didn't work. Candidates who only describe successes are less credible than candidates who describe both successes and failures honestly. The willingness to engage with what didn't work suggests that the candidate has actually been doing the work and has developed real perspective on it.
The pattern that concerns me most is candidates who attribute failures entirely to other people or to circumstances outside their control. The pattern usually indicates either lack of self-awareness or a defensive posture that will create friction in the role. Either way it predicts difficulty.
The pattern that impresses me most is candidates who can discuss their own contribution to things that didn't work without being defensive about it. This requires both self-awareness and confidence in their overall capability — the candidate is secure enough to acknowledge specific failures because their broader competence isn't in doubt.
For candidates preparing for interviews, prepare honest accounts of things that didn't work as well as things that did. The honest accounts are more credible and more compelling than purely positive narratives.
Demonstrated continuous learning
The IT service management field has changed substantially over the past decade and will continue to change. Candidates who have demonstrated continuous learning across their career are more likely to remain effective as the field continues to evolve.
The continuous learning evidence I look for includes specific examples of how the candidate has updated their practice in response to new developments. Not just "I keep up with the field" but "I noticed that our incident response was getting bogged down by manual triage so I researched how other organisations were handling that and we ended up implementing X which produced Y outcome."
The candidates who can show this pattern have a better track record of continued effectiveness than candidates whose practice has remained static across years of unchanging environments. The unchanging environments don't always remain unchanging, and candidates who have practiced learning are better positioned for the changes that will eventually come.
Cross-functional working capability
ITSM roles are inherently cross-functional. Service management work requires coordination with development teams, business stakeholders, vendor partners, and various other groups whose interests don't always align with the service management function's interests.
I look for evidence that candidates have actually navigated these cross-functional relationships effectively. The evidence shows up in specific examples of negotiating with stakeholders whose preferences differed from the service management view, building working relationships across organisational boundaries, and managing through the political dynamics that inevitably affect service management work in larger organisations.
Candidates without this evidence are often technically competent but struggle in roles that require cross-functional capability. The technical capability alone doesn't translate into role effectiveness when the role requires the broader competencies.
Communication clarity
I assess communication capability carefully throughout the interview process. ITSM roles produce enormous amounts of written and verbal communication — incident reports, change documentation, stakeholder updates, vendor management, business cases. The candidates who can communicate clearly will be effective in these roles. The candidates who can't won't be, regardless of their technical credentials.
The communication assessment happens implicitly across the interview rather than through explicit communication tests. How does the candidate respond to questions? How do they structure their answers? How do they handle clarifying questions when their initial response wasn't clear? How do they describe complex situations to listeners who may not share their technical background?
The candidates who consistently communicate clearly across these implicit assessments are usually the ones who will be effective in the role. The candidates whose communication is muddled or who can't adjust their explanations to the listener's level usually struggle in roles where these communication demands are significant.
For candidates preparing for interviews, paying attention to your own communication clarity matters more than rehearsing specific answers. Practice explaining complex situations to listeners who don't share your background. Notice when your explanations are unclear and figure out how to make them clearer. The communication capability built through this practice will serve you in the interview and in the role.
Operational realism
I look for candidates who have a realistic understanding of how service management actually works in operational environments rather than candidates whose framework is primarily theoretical.
The realistic candidates know that the textbook processes don't always work the way they're documented. They know that organizational politics affects what's actually feasible. They know that specific stakeholders have specific preferences that have to be navigated. They know that resources are finite and that prioritization is hard. They know that not all problems get fixed and that triage decisions require judgment.
The unrealistic candidates speak as if the textbook were directly applicable, as if the right framework would resolve organizational politics, as if all problems could be solved with sufficient resources. These candidates struggle when they encounter the messy realities that experienced practitioners take for granted.
For candidates preparing for interviews, demonstrate operational realism through how you frame your experiences. Acknowledge the messiness rather than presenting your work as if it followed clean textbook patterns. The realism is more credible and more attractive than the polished framework rehearsal.
Specific technology depth
ITSM roles increasingly require specific technology depth in addition to framework capability. Candidates who can speak credibly about specific tool implementations, integration patterns, automation approaches, and data analysis techniques have a meaningful advantage over candidates whose capability is purely framework-level.
The specific technology depth doesn't have to be exhaustive. It does have to be credible. Candidates should be able to discuss the specific tools and technologies they have actually worked with in detail rather than generally referencing technology categories they have heard about.
For candidates preparing for interviews, identify the specific technology areas where you have genuine depth and be ready to discuss them in detail. Don't claim depth you don't have — interviewers can usually identify the difference between actual depth and rehearsed talking points. Your actual depth is what you should highlight.
What I don't weight as heavily as candidates seem to think I do
Some factors candidates emphasize in interviews matter less than they seem to think.
Specific certifications matter at the foundational level (ITIL Foundation as a basic credential) but don't strongly differentiate candidates beyond that level. A candidate with multiple advanced certifications and limited experience is generally less attractive than a candidate with foundational certifications and substantial experience.
Years of total experience matters less than the depth and quality of the experience. Five years of substantive cross-functional service management work in a complex environment typically beats fifteen years of repetitive operational work in a stable environment.
Specific company prestige matters less than what the candidate actually did in those companies. A candidate who did substantive work at a smaller company is generally more attractive than a candidate who held a comparable title at a more prestigious company but did less substantive work.
For candidates preparing for interviews, don't lean primarily on the things that interviewers don't actually weight as heavily as you might think. Lean on the things that actually matter — specific examples, honest engagement with what worked and didn't, demonstrated learning, cross-functional capability, communication clarity, operational realism, and specific technology depth.
What this means for career investment
The hiring patterns I have observed suggest specific career investment priorities for ITSM professionals.
Build operational depth. Get the experience that produces specific examples you can discuss in interviews. The depth comes from sustained engagement with actual service management work, not from credential accumulation.
Develop self-awareness. The honest engagement with what didn't work that interviewers value develops through deliberate reflection on your own practice, not through reciting standard framework material.
Practice writing and speaking clearly. The communication capability that determines effectiveness in ITSM roles develops through practice. Build the practice into your work routinely rather than waiting for interview preparation.
Cultivate cross-functional working relationships. The cross-functional capability that interviewers look for develops through actually navigating cross-functional work. Volunteer for opportunities that build this capability.
Develop genuine technology depth in specific areas. Pick a few technology areas to develop deeply rather than maintaining surface familiarity with everything. The depth is more valuable in interviews and in the role than the breadth.
The career investment pattern that produces interview success and role effectiveness is consistent. The pattern develops over years rather than through last-minute interview preparation. Investing along these lines from earlier in a career produces both better interview outcomes and better role outcomes than the alternative investment patterns that some career advice suggests.
