Friday, Paweł’s last day at work - a Senior Developer with 4 years of tenure. HR conducts the exit interview. “Why are you leaving?” - “New opportunity, better offer.” “How do you rate the company culture?” - “Good, nice people.” “Is there anything we could have done differently?” - “No, everything was OK.” Paweł leaves, HR closes the folder. Case closed.
Two weeks later, on the alumni Slack, Paweł writes to a former colleague: “I couldn’t take that micromanagement anymore. Every PR reviewed by 3 people, constantly asking what you’re doing, no trust. Plus that legacy technology - 4 years on the same stack with no chance for development. And the hypocrisy about work-life balance - supposedly flexible, but messages at 10 PM from the manager.”
This is the gap between what departing employees say in exit interviews and what they really think. A gap that costs organizations millions in turnover because problems are never fixed.
Why do departing IT specialists lie in exit interviews?
They don’t lie maliciously - they lie rationally. An IT specialist who’s leaving calculates: what do I gain by telling the truth? What might I lose? The balance rarely favors honesty.
References and relationships. The IT world is small. That manager I’d like to criticize might be my client, business partner, or even boss at another company in a year. LinkedIn connections, industry events, shared open source projects - paths cross constantly. Burning bridges is risky.
Last impression dominates. Psychology talks about the “peak-end rule” - we evaluate experiences through the lens of the most intense moment and the ending. The exit interview is the ending. The departing employee unconsciously wants to end positively - for their own wellbeing and for the narrative they’ll tell at the new place.
No belief that anything will change. “Why should I put in effort when it won’t change anything?” If the organization ignored feedback for years, the departing employee doesn’t believe it will suddenly start listening. Energy invested in detailed feedback seems wasted.
Emotional distance. At the moment of the exit interview, the specialist is already mentally elsewhere. New job, new challenges, new chapter. Rehashing the old company’s problems is returning to the past, which doesn’t serve the future. Minimizing emotional engagement is healthy.
Fear of consequences even after leaving. Negative recommendations whispered in the industry, blocked if they ever want to return, strained relations with former colleagues who stay. The costs of honesty can be real and long-term.
What are the real reasons for IT specialists leaving, hidden behind diplomatic answers?
“Better financial offer” often means: “I was undervalued, I saw no growth path, I looked for alternatives - and found them.” Money is easy to give as a reason because it’s objective and doesn’t attack anyone personally. The truth is more complex - if everything else was ideal, would they really leave for 10% more?
“New challenges” can mean: “I was bored, stuck doing the same thing for years, asked for a project change and nothing happened, my ideas were ignored.” Lack of development and stagnation are top 3 reasons for developer departures according to Stack Overflow Survey 2025 - but at an exit interview it’s easier to say “looking for challenges” than “I’m not developing here.”
“Personal/family reasons” is sometimes a mask for: “The culture is toxic, the manager is a tyrant, I can’t take it anymore, but I don’t want drama.” When someone says “personal reasons” and doesn’t elaborate - red flag. The reason is probably very personal to the situation in the company.
“Relocation/remote” may hide: “Your return-to-office policy is idiotic, other companies offer full remote, I’m not going to commute 2 hours a day when I don’t have to.” Companies mandating office return see an exodus of talent disguised under “logistical reasons.”
“Changing industry/career direction” sometimes means: “Burnout, I don’t want to program anymore - at least not in conditions like yours.” Professional burnout in IT is an epidemic (76% report symptoms according to Blind Survey 2025), but few will say outright “you burned me out.”
How to conduct an exit interview that extracts real information?
Timing matters critically. Standardly, the exit interview is on the last day or during the notice period. By then, the departing employee is already mentally elsewhere and wants to close the topic quickly. Alternative: follow-up interview 3-6 months after leaving. Emotions have settled, the new job gives perspective, less fear about bridges.
The person conducting cannot be the direct manager or anyone the departing employee might “fear.” HR is neutral but often perceived as “the company’s side.” An external consultant can be more effective - a stranger, no relationship, easier to tell the truth.
Questions must be specific and behavioral, not general. Instead of “How do you rate the culture?” (answer: “good”) - “Tell me about a situation when you felt frustrated at work. What happened?” Instead of “Did the manager support you?” - “Describe what your 1:1s with the manager looked like. How often? What did you talk about?”
Normalizing criticism. “Every organization has problems, perfection doesn’t exist. From our previous conversations, we know people often mention X, Y, Z. Does any of these topics resonate with your experience?” Showing that we know about problems encourages sharing more.
Guarantee of anonymity in reporting - and keeping it. “Your specific words won’t go to anyone - we’ll aggregate feedback from many conversations and present trends, not quotes.” And actually do it - one case of revealing a source destroys trust for years.
Projective questions instead of direct ones. “What would you tell a friend who’s considering applying to us?” - easier to tell the truth talking “about the company” than “about myself.” “If you were CEO for one day, what would you change?” - allows expressing frustration as a “proposal.”
What questions to ask and which to avoid?
Open, behavioral, specific questions. “Tell me about a project you liked the most. What made it good?” - positive framing, but reveals what matters to the person. “Tell me about a project that was frustrating. What went wrong?” - negative experience, but specific. “If you were starting again, what would you do differently knowing what you know now?” - projection onto self, but about the environment.
“What did you like?” and “What would you change?” as a pair. Not just negatives - understanding what worked is equally valuable. Positive questions at the start build rapport and show we’re not just looking for criticism.
“How would you describe a typical workday?” - neutral, but reveals a lot about rhythm, stress, autonomy, breaks. “How much time did you spend in meetings vs. actual work?” - meeting overload is a common problem hidden behind “lack of efficiency.”
Avoid questions that suggest the answer. “Do you agree we have a great culture?” - of course they’ll say yes. “Did the manager support you?” (closed, suggestive) vs. “Describe your relationship with the manager” (open, neutral).
Avoid general, abstract questions. “How do you rate the company?” - too broad, you’ll get “good” or “varies.” “What do you think about communication?” - also too broad. Specific: “How did you learn about company strategy changes? Who communicated that to you and how?”
Avoid personal questions without purpose. “Do you have a problem with Adam?” - even if they do, they won’t say, because it’s an interpersonal conflict with consequences. Better: “How was collaboration in the team? Were there any frictions?” - more general, less personal.
How to analyze data from exit interviews and draw conclusions?
Aggregation and categorization of topics. A single exit interview is an anecdote. 10 exit interviews are a pattern. Categorize feedback: management/leadership, compensation/benefits, growth/development, culture/environment, work-life balance, technology/tools. Which categories dominate?
Quantify where possible. “3 of the last 5 departing employees mentioned manager X’s micromanagement” - that’s actionable. “People complain about management” - that’s too general. Create metrics: % of departing employees citing a given problem.
Cross-reference with other sources. Does feedback from exit interviews correlate with engagement surveys? With Glassdoor reviews? With retention rates per manager? Data triangulation builds a fuller picture and reduces single-source bias.
Time trend analysis. Are problems new or chronic? Did something improve after intervention? Tracking over time shows whether corrective actions are working.
Segment by role, team, tenure. Do juniors leave for different reasons than seniors? Does one team have disproportionately many departures? Do people leaving before 1 year say something different than those after 5 years? Segmentation allows targeting interventions.
Look for what’s NOT said. If no one mentions compensation - it’s probably not the main problem (or is acceptable). If no one mentions the manager positively - that lack of positives is information.
What actions to take based on exit interview feedback?
Quick wins for obvious problems. If 5 people in a row say the deploy process takes 4 hours and is frustrating - fix the deploy process. Doesn’t require deep analysis, requires action. Quick wins build credibility that feedback is taken seriously.
Structural changes for systemic problems. If many departing employees mention a specific manager’s micromanagement - is it a manager problem, not system? Does it affect other managers too? Maybe delegation training is needed, maybe changed expectations, maybe coaching, maybe - in extreme cases - a position change.
Communication loop - show you’re listening. Announce (anonymously) what you heard and what you intend to do about it. “Based on feedback, we’re introducing X, Y, Z.” People who stay see the company responds - this builds trust and reduces future turnover.
Preventive measures. Exit interview talks about the past - but the goal is the future. If the problem is lack of development opportunities - introduce learning budgets, rotation programs, internal mobility. If the problem is work-life balance - revisit policies, expectations, after-hours communication norms.
Manager feedback and development. If many exit interviews point to a specific manager - that information must reach them (appropriately) and there must be an action plan. Not blame game, but development opportunity. If the manager doesn’t respond - consequences.
Tracking effectiveness. A change was introduced - do subsequent exit interviews show improvement? Do engagement surveys show improvement? Did retention in the affected area improve? Close the loop - verify that actions work.
Why don’t most organizations act on exit interview feedback?
Lack of ownership and accountability. Who is responsible for acting on exit interviews? HR collects data but has no power to make changes in engineering. Engineering management sees only aggregated reports once a quarter. No one has it as a KPI, so no one prioritizes.
Data is too qualitative and “soft” for decision makers. The CFO wants numbers, not quotes. “People talk about bad culture” - what does that mean? How much does it cost? Without quantification in business language, feedback is ignored.
Defensiveness and denial. “That’s just one complainer,” “She always had a problem with X,” “He didn’t understand our culture.” It’s easier to discredit the source than face uncomfortable truth. Especially if feedback concerns senior leadership.
Change is difficult and expensive. Change a manager? Politically risky. Change the tech stack? Years of work. Change the culture? Decades. It’s easier to say “it’s not that simple” and continue as before.
No system for tracking and follow-up. Exit interview goes to a folder, folder goes to archive. No one returns, no one checks if problems recur. No systematic approach = no systematic actions.
Resignation that “it’s just how it is.” “Everyone rotates in IT,” “The young generation isn’t loyal,” “The market is overheated.” Externalizing causes relieves responsibility for fixing.
How to create a continuous feedback system, not just exit interviews?
Stay interviews - conversations with people who stay. “What keeps you here? What would make you leave? What could we improve?” Proactive, not reactive. Easier to fix when the person is still on board than after the fact.
Regular 1:1s with feedback focus. Manager asks at every 1:1: “What could I do better? What frustrated you recently? What would you change if you could?” Builds a culture of continuous feedback, not just exit.
Anonymous pulse surveys. Short, frequent (monthly or quarterly), 5-10 questions. eNPS (employee Net Promoter Score), questions about manager, workload, growth. Trend over time, segmented by team. Tools: Culture Amp, Lattice, 15Five.
Open door policy with actual follow-through. The declaration “my door is always open” means nothing without action when someone comes. People must see that feedback leads to changes - otherwise they’ll stop giving it.
Skip-level 1:1s - conversations between employee and their manager’s manager. Give perspective bypassing the direct supervisor. “How’s work in the team? How do you rate support from [manager name]?” Allows catching problems with managers.
External feedback channels. Glassdoor reviews, Blind posts, social media. Monitor what people say publicly. Often more honesty than internally. Respond professionally to negative reviews - shows the company listens.
What role does the manager play in retention and how to catch it through exit interviews?
“People leave managers, not companies” - old saying with solid research backing. Gallup reports that the manager accounts for 70% of variance in employee engagement. Exit interviews should explicitly explore the relationship with the manager.
Red flags about the manager in exit interviews: no specific positives about the manager, generalities (“was OK”), avoiding the topic, passive-aggressive comments (“did what he could within the system”), descriptions of situations without manager agency (“that’s just how it was”).
Green flags: specific positive stories, expressed regret about parting, offering as a reference, proactively stating “the manager isn’t the reason for leaving.”
Correlation between managers and retention. If one manager has 30% annual turnover when the company average is 15% - that’s no coincidence. Data from exit interviews + retention metrics = actionable insight.
Interventions for problematic managers: executive coaching, 360 feedback, explicit expectations and monitoring, ultimately - role change or separation. But first: clear communication about what the problem is and a chance to improve. People can change.
Manager training as prevention. Training in feedback, delegation, career conversations, difficult conversations. Especially for new managers (transition from IC to manager is hard). Investment in managers = investment in retention.
Table: Red flags in exit interview answers and their probable meaning
| Exit Interview Answer | Probable Hidden Meaning | Suggested Follow-up |
|---|---|---|
| ”Better financial offer” | Feel undervalued, no prospects | ”Did you discuss a raise/promotion before looking?" |
| "Looking for new challenges” | Stagnation, boredom, no development | ”What did your last year look like in terms of learning new things?" |
| "Personal reasons” | Don’t want to tell truth about problems | ”Did anything at work influence this decision?" |
| "Everything was OK” | Don’t see point in feedback | ”If you were advising a friend - what should they know about working here?" |
| "Relocation/work mode change” | Office policy is unacceptable | ”How do you rate our flexibility in this area?" |
| "Manager was OK” (without enthusiasm) | Manager was the problem | ”Describe a typical interaction with the manager. What were your 1:1s like?" |
| "Culture is good, nice people” | Problems are elsewhere than relationships | ”How do you rate processes, technology, leadership?" |
| "Want to try something new” | Burnout or deep frustration | ”What made you start thinking about a change?” |
| Short, curt answers | Don’t trust that feedback will change anything | Consider follow-up 3-6 months after departure |
| ”This isn’t the place to talk about it” | Something serious but afraid | Offer confidential channel or external conversation |
Exit interviews are a goldmine of knowledge about what’s really happening in the organization - but only if they’re conducted effectively and if actions are taken based on them. Most companies waste this opportunity, collecting diplomatic answers and archiving them without conclusions.
Key takeaways:
- Departing IT specialists lie rationally - they minimize risk to themselves
- Real reasons are hidden behind diplomatic answers - learn to decode them
- Timing, the person conducting, and questions determine feedback quality
- Aggregation and trend analysis reveal patterns that a single interview won’t show
- Acting on feedback is crucial - no action = no future feedback
- Continuous feedback (stay interviews, pulses) is better than just exit interviews
The real value of an exit interview lies not in the farewell ceremony - it lies in the ability to fix problems before more people leave.
ARDURA Consulting supports organizations in building a feedback culture and IT talent retention. We offer both specialist recruitment and HR consulting for technology teams. Let’s talk about how we can help retain your best people.