The Training Tax: Why Irish Tech Companies Are Losing Institutional Knowledge
Knowledge that lives in one person's head is not an asset. It is a liability with a countdown clock.
Irish tech companies discovered this the hard way when the 2023 layoff wave hit. Entire teams were restructured, senior engineers walked out the door, and the juniors left behind found themselves holding codebases nobody had ever properly explained to them. The problem was not the layoffs themselves. The problem was that no knowledge transfer had ever happened in the first place.
The Salary Gap Is Doing Real Damage
Here is the situation on the ground. A senior software engineer in Dublin earns somewhere between €90,000 and €130,000 depending on the employer. The junior beside them earns €45,000 to €60,000. That gap is not unusual in any industry, but what is unusual in Irish tech right now is how visible that gap has become to the people on both sides of it.
Experienced staff know their market rate. They have watched colleagues move to new companies for 20% more. They have seen juniors hired on packages that, when share options and remote allowances are added, are closing the gap faster than anyone expected. And in that environment, many senior engineers have made a quiet, rational decision: mentoring a junior who might be earning nearly as much as them, for no additional compensation, is work they are no longer willing to do for free.
This is not cynicism. It is arithmetic. The senior engineer is being asked to produce their own deliverables, mentor two or three juniors, document processes for a company that has never properly funded documentation, and do all of this while watching their relative pay advantage erode. Something has to give. Mentoring is the thing that gives, because it is the least visible and the least immediately punished.
What Gets Lost When Mentoring Stops
Institutional knowledge is not the stuff in the wiki. The wiki holds the official version of how a system works. Institutional knowledge is the reason a particular API call is made in a specific sequence that nobody ever wrote down, because the engineer who built it had an argument with a product manager three years ago and the compromise they reached lives only in muscle memory and tribal lore.
The skills gap this creates is already showing up in how Irish CIOs are struggling to deploy AI agents. But AI deployment problems are just the visible edge of a deeper fracture. When experienced engineers stop transferring what they know, junior staff spend months rediscovering decisions that were already made, relitigating problems that were already solved, and making expensive mistakes that an afternoon of proper mentoring would have prevented.
The cost is not abstract. A single misunderstood architectural decision in a production system can cost a company weeks of engineering time to unravel. At €100 an hour for senior engineer time, a week of that is €4,000 gone before anyone has noticed. Multiply that across a mid-sized Irish tech firm with thirty engineers and a deteriorating mentoring culture, and you are talking about a six-figure annual drag that never appears as a line item anywhere.
The Four-Stage Knowledge Drain
Understanding how institutional knowledge leaves an organisation is more useful than simply knowing that it does. The process follows a consistent pattern.
Stage 1: Salary tension rises. Compressed pay bands or visible inequity make senior staff feel undervalued relative to what they know they carry.
Stage 2: Informal mentoring dries up. Nobody sends a memo. Senior engineers simply stop volunteering. They answer direct questions but stop asking juniors to come along for the ride. The corridor education ends.
Stage 3: Documentation stays poor. With no one translating tacit knowledge into written form, the wiki becomes a museum of outdated diagrams. New staff learn to distrust it, so they stop adding to it.
Stage 4: The expert leaves. They get a better offer, which they will, because they are good. And on the day they walk out, the organisation realises it owns none of what they knew.
The order matters because each stage makes the next one harder to reverse. By Stage 4, no retention bonus fixes the problem. The knowledge is already gone.
What Companies Are Actually Getting Wrong
Most Irish tech companies treat this as a culture problem. It is not. It is a structural compensation problem wearing a culture problem's coat.
Running a mentoring programme without addressing the pay gap underneath it is like putting a fresh coat of paint on a wall with damp. The paint looks fine for a month. Then the problem comes back worse.
The companies getting this right are doing three things that their competitors are not. First, they are paying for knowledge transfer explicitly. Not a vague bonus. An actual line in the compensation structure tied to the measurable output of a mentored colleague reaching a defined skill level. Second, they are making senior engineers producers of institutional value, not just technical output. The engineer who documents a critical system and brings a junior up to speed on it is not doing admin. They are creating a company asset. Treat it that way and price it that way. Third, they are tracking knowledge concentration the same way they track code quality. If one person is the sole owner of three or more critical systems, that is a risk register item, not a talent management footnote.
The Binary That Matters
There are two types of Irish tech company right now. The first type treats knowledge transfer as a soft skill, something HR mentions in the induction week and never revisits. The second type treats it as a balance sheet item, something that has a cost when it is absent and a return when it is built properly.
The way Irish research spin-outs have scaled by treating knowledge as a transferable asset offers a cleaner model than most tech firms are willing to admit they need to copy. Academic spinouts live and die by their ability to take what one researcher knows and make it institutional. Commercial tech firms have been lazier about this because the growth years made it easy to just hire more experts rather than develop what they already had.
Those years are over. Hiring budgets are tighter, senior talent is scarcer, and the juniors coming through are watching carefully how they are treated before deciding whether to stay or go.
The companies that build a real price into mentoring will keep their knowledge inside the building. The companies that keep asking experienced engineers to train their own replacements for free will keep losing to the ones that do not.
