Retention Theatre or how to Engage your Developer Community

The honest answer is that perks like catered meals, gym memberships, and office goodies are retention theater. They're visible, they're photographable for the careers page, and they feel generous. But they operate at the wrong layer of the retention problem.

They address comfort, not meaning. An engineer who is bored, blocked, or underutilized doesn't become engaged because lunch is free. They just eat better while quietly job hunting.

The research on this is fairly consistent: extrinsic perks have a short hedonic half-life. They become expected within weeks, stop registering as positive, and only become salient again if removed — at which point they're a reason to leave. You're essentially paying a maintenance cost on something that was never driving retention in the first place.

A good developer experience compounds differently. Every hour of friction removed is an hour of engagement added, permanently. Every abstraction that lets an engineer ship faster raises their baseline satisfaction with the work itself. It improves the thing they actually care about — their craft.

The spending comparison is stark when you frame it this way. A catered lunch program for 15 people might run €50-80k per year. That same budget, invested in platform engineering or tooling, produces something that improves daily experience indefinitely and — in your case specifically — becomes a client-facing asset.

The one thing perks do well is signal culture during recruiting. A nice office and good food say "we take care of people here." But that signal needs to be backed by the actual experience of working there, or it becomes a source of cynicism very quickly.

The companies that retain developers well tend to spend less on visible perks and more on invisible ones — fast CI, good hardware, clear processes, time to do things properly. Engineers notice the invisible ones more, because they feel them every day.