Engineering Management in the Netherlands: Should You Stay Technical or Embrace Leadership?

After stepping into engineering management in the Netherlands myself, I found it surprisingly difficult to decide whether to stay technical or go full leadership. Here’s what I’ve learned and what I think others should consider.

As engineers rise into management roles, they often find themselves at a professional fork in the road:
Do they stay rooted in technology, sharpening their technical depth while guiding others from the trenches?
Or do they lean fully into people and organisational leadership, where strategic decisions, team dynamics, and cross-functional alignment dominate the job?

In the Netherlands, home to a thriving and mature tech ecosystem, this question is especially relevant. The market offers strong support for both paths, but there’s little room for ambiguity. In most Dutch companies, you’re expected to choose.

A Booming Market With Clear Career Tracks

The Dutch tech sector is booming. According to the Dutch Ministry of Economic Affairs and Climate Policy, ICT is one of the fastest-growing industries in the country, contributing over €50 billion to the GDP annually¹. Amsterdam consistently ranks among Europe’s top five tech hubs², and Dutch cities like Eindhoven, Rotterdam, and Utrecht are gaining ground as innovation centres.

This growth has created a wide array of roles for engineers, from early-stage startup builders to specialists in scale-up and enterprise environments. Dutch companies, both local and international (e.g., ASML, Adyen, TomTom, Booking.com), tend to offer structured career ladders inspired by Silicon Valley standards, think Individual Contributor (IC) tracks that go up to Staff and Principal Engineers, and Management tracks that scale to Head of Engineering, VP, and CTO roles.

The fork in the road: IC vs Manager

Option 1: The Technical Track

This path allows you to grow as a technologist. Your influence expands not by managing people but by making architectural decisions, mentoring other engineers, driving code quality, and leading high-impact projects. Titles might include:

• Senior Engineer

• Staff Engineer

• Principal Engineer

• Technical Architect

• Distinguished Engineer

The Staff Engineer model, as described in Will Larson’s book Staff Engineer: Leadership Beyond the Management Track³, is increasingly visible in Dutch firms. It acknowledges that engineering excellence doesn’t have to mean leaving the keyboard behind. Dutch companies like bol.com, MessageBird, and Picnic actively support these tracks, often with compensation and status on par with management.

Option 2: The Management Track

This track shifts the engineer into a leadership role focused on:

• Hiring and team growth

• Performance management and 1:1s

• Cross-functional collaboration

• Budgeting and resource planning

• Navigating organisational politics

As you move up the ladder, Engineering Manager → Head of Engineering → Director or VP—you gain more influence over strategy, product priorities, and company direction. However, technical involvement often fades.

In many Dutch companies, Engineering Managers are not expected to code regularly. The player-coach role may exist at early stages, but once you're managing more than 6–8 people, expectations shift. At this point, your primary deliverables become organisational health and delivery efficiency, not systems design.

Why Dutch engineers must choose

1. Clarity and focus are cultural norms

Dutch work culture values directness, pragmatism, and a focus on results. Trying to juggle people management and deep technical work is generally frowned upon. It dilutes both. The consensus is clear: if you’re splitting your time between tech and team, you’re likely underdelivering on both fronts.

2. The hybrid role doesn’t scale

While hybrid “tech lead manager” roles exist, they’re often transitional. Dutch companies, especially those in the scale-up and enterprise stages, prefer clear roles over blended responsibilities. Once you’re managing teams or multiple squads, staying technical often becomes impractical—even damaging.

That’s not a failure. It’s structural. Engineering leadership in the Netherlands demands operational maturity, not just architectural fluency.

3. Respect for the technical path runs deep

In some countries, engineers are nudged into management simply because it’s the only way to “move up.” That’s not the case in the Netherlands. Companies here increasingly recognise the value of senior ICs. Roles such as Principal Engineer or Tech Lead are explicitly mapped on job ladders and often carry influence that rivals (or surpasses) that of managers.

This aligns with the Dutch tendency to reward substance over status. Influence comes from impact, not hierarchy.

The risks of going full management

• Loss of technical edge:
  Once you’re out of the codebase for 6–12 months, it isn’t easy to return to the same level. If you decide to pivot back, you may face scepticism from hiring managers or struggle with confidence.

• Management isn’t just “soft skills”:
  Managing people in the Netherlands is a serious craft. You’ll need to handle conflict resolution, career development, org planning, and more. It’s not for everyone, and the expectations are high.

• Fewer short-term wins:
  Engineering offers the dopamine hit of shipping something. Management is slower, more abstract, and success is often indirect.

Questions to ask before you choose

1. Do I get more satisfaction from solving technical puzzles or enabling people to succeed?

2. Do I want to be responsible for hiring, performance reviews, and team culture?

3. Can I let go of the codebase and still feel valuable?

4. Am I comfortable stepping into politics, trade-offs, and product strategy?

Your answers should guide your next move, not job titles or salary ladders.

Conclusion: pick a lane and own it

In the Dutch tech ecosystem, you’re not punished for staying technical. You’re not pushed into management to grow. And if you choose to manage, you’re expected to go all-in—to commit to the business of building teams, not just systems.

Both tracks are respected. Both offer long-term career growth, especially in a market as balanced and rational as the Netherlands.

But sitting on the fence? That doesn’t scale. Not here.

References

1. RVO – ICT in the Netherlands (https://www.rvo.nl)

2. Startup Genome – Global Startup Ecosystem Report 2024

3. Larson, Will. Staff Engineer: Leadership Beyond the Management Track, 2021.