I spent twelve years in corporate IT — network engineering, infrastructure, eventually leading a team of fifteen at a Tier 1 manufacturing company in Germany. It paid well. The benefits were solid. And after year eight, I was bored out of my mind.
The move to agency work wasn’t planned. A recruiter reached out about a senior infrastructure consultant role at a mid-sized digital agency in Hamburg. I almost ignored the email. I almost made a very comfortable mistake. That was six years ago. Since then I’ve worked with more companies, on more varied problems, and learned more than I did in my entire corporate tenure combined.
What follows is what I wish someone had told me before I made the jump — and what I now tell people who ask me whether the move is worth it.
Why people actually leave
Corporate IT has real structural advantages: stable salaries, clear career ladders, generous benefits, predictable workloads. The problems that grind people down are equally structural. The most consistent one I hear — from people still in corporate and from people who left — is that learning stops. Enterprise environments move slowly by design. The security review for a new tool takes six months. The budget cycle for hardware is eighteen months. You spend more time navigating procurement than building anything. The Stack Overflow Developer Survey 2023 ranked “learning new technologies” in the top three factors developers consider when evaluating job opportunities; corporate IT roles score poorly on exactly this dimension.
The second problem is visibility. In a five-thousand-person company, the IT department is a cost center. You’re measured on uptime and ticket resolution time, not on business impact. The work matters — infrastructure is what keeps everything running — but the connection between what you do and what the company does is indirect enough that it rarely feels like it matters.
What agency work actually involves
It’s not “IT but faster.” The client model changes the fundamental nature of the work. In my first six months at the agency, I went from troubleshooting WooCommerce performance for a Berlin e-commerce brand, to presenting a cloud migration plan to a Frankfurt law firm, to specifying an MVP for a startup that had raised €2M and couldn’t quite articulate what they wanted to build. That context-switching is either energizing or exhausting depending on the person. I found it energizing. I’ve also watched people arrive from corporate with strong technical backgrounds and struggle badly with the ambiguity. Be honest with yourself before you make the move.
What agencies want: technical depth in at least one area — cloud infrastructure, full-stack development, security, data engineering — combined with the ability to communicate with clients and work at compressed timelines. The project that would take six months in corporate gets three months at an agency. The spec that would go through five approval cycles goes through two. This is the trade-off you’re accepting.
What corporate IT actually transfers
More than you’d expect, and not what you’d predict. The skills that transferred most directly for me were not the technical ones. Knowing what production systems look like under real load — what “this will break at 10x traffic” looks like before it happens — was immediately useful at an agency full of developers who’d never had to think about that question. Enterprise IT develops a specific kind of systems intuition that agency developers often lack.
Project coordination transfers directly if you reframe it. Managing IT rollouts, vendor relationships, and change control processes is stakeholder management. Rename it on your CV and put it prominently. Security background also transfers, in both directions — GDPR handling, access control, backup procedures — because many agency developers are casual about security until something goes wrong, and having someone in the room who’s been responsible for a breach in a regulated environment is more valuable than most agencies realize.
The gap that surprised me most was documentation. Enterprise IT enforces it. Most agencies are genuinely terrible at it. Being the person who writes decisions down and keeps records is valued and appreciated faster than you’d expect.
What you’ll need to build before the move
If your background is traditional infrastructure and you haven’t touched code seriously in years, invest three to four months in a modern web stack before applying. JavaScript, Python, and SQL cover the majority of what agency technical work requires at a senior level. You don’t need to be a developer — you need to be able to participate in technical conversations without slowing them down.
Docker and basic CI/CD understanding are worth adding. Not expert-level; enough to understand what’s happening and to set up a working pipeline if asked. DevOps has moved from specialization to baseline expectation in most agencies that do serious technical work.
The cultural gap is harder to close before you arrive. Corporate IT has a caution culture — for good reasons, because the cost of a mistake in a regulated manufacturing environment is high. That same caution reads as too slow in an agency. You’ll need to recalibrate your risk tolerance without abandoning your technical judgment. There’s a version of this that goes wrong: people who become reckless to compensate. The useful version is learning which risks are actually consequential in an agency context and which ones aren’t.
The job search
Corporate IT CVs list technologies and responsibilities. Agency CVs need to tell stories: what did you build, what problem did it solve, what was the measurable outcome? Rewrite every bullet point with that structure. The agency hiring manager reading your CV is thinking “would I put this person in front of a client?” and “can they talk about their work?” Make both answers obvious.
On agency size: my instinct, based on where I’ve seen corporate-to-agency transitions go well versus badly, is that fifty-to-two-hundred-person agencies work better for the first move than either extreme. Large agency networks often replicate the worst parts of corporate bureaucracy. Very small boutiques typically need people who are already comfortable with the chaos, not people who are learning to adjust to it. That said, the right agency is the one where the technical work matches your background — size is a proxy, not a rule.
Expect the interview to include a technical component and a client-scenario exercise. The scenario typically sounds like: “A client calls at 4pm saying the site is down, you have no access to the codebase, and the junior developer who built it left last month. Walk me through how you handle it.” The answer they’re evaluating isn’t technical. It’s how you communicate under pressure and whether you know what to prioritize.
The salary math
Entry-level agency roles often pay less than comparable corporate positions. Mid-senior roles can pay comparably or better, especially if you’re client-facing in a high-demand specialization. The trajectory in agency work is faster — but the base in year one may be lower. If money is the primary driver, this move may not make financial sense immediately. Six years in, I’ve never considered going back, but I made the transition from a position of financial stability and clear technical value. If neither of those conditions exists yet, fix them first.
For a starting point on European agencies worth researching, see the breakdown of notable European digital agencies — with notes on what each one actually looks like from the inside. Before that, it helps to understand what separates a well-run agency from a poor one — the signals that are hard to read from the outside.