Do Server Engineers Not Write Code? — Another Face of Engineering I Discovered in a 200-Person Project

What!? Engineers who don’t write code are supporting the system—I encountered such a reality on the ground.

■ Behind a Massive Project

The project I was involved in had over 200 members. It was led by a core company supporting one of Japan’s central financial institutions. The mission was to transform one of its core systems from COBOL to Java—a true turning point of an era.

I joined as a configuration management engineer. My role was to maintain consistency across massive amounts of source code, versions, and releases. I had written some Java programs myself, but my main battlefield was “keeping things in order.”

 
 

■ The Unsung Hero Protecting the Environment

In this environment, the people I worked closely with were the server engineers. Developers can write code with confidence only when the environment is stable—and it was the server team that sustained that foundation.

As we naturally started talking more and grew closer, a question came to my mind one day.

“Since server engineers understand Java configurations so well, they must be great at programming too, right?”

■ An Unexpected Answer

The response I got was completely different from what I had imagined.

“Well… I actually can’t program.”

For a moment, my mind froze. I had started my career from programming—writing code, running it, and understanding systems through it. That’s why the idea of not being able to program didn’t quite connect in my head.

■ Different Entry Points, Same Goal

As I listened more, I began to understand the difference.

I had started from “things that move,” so it was easy for me to visualize logic and processing flows. On the other hand, he had started from the “foundation”—server architecture.

“I build it step by step, like blocks.”

That phrase stayed with me.

■ Digital LEGO

Indeed, I had seen him with a thick technical manual in hand, assembling environments piece by piece—servers, middleware, networks, configuration files—layering them to create a functioning world.

It felt just like digital LEGO.

At that moment, I realized that “creating” is not limited to writing code. Building environments is also a form of creation.

■ There Is No Single Career Path

What struck me most from this experience was that there is no single correct path for engineers.

Some start from code, others from infrastructure. Both support the same system and create value from different perspectives.

In fact, this diversity may be exactly what enables large-scale projects to succeed.

■ Business Insight

In the era of DX, what matters is not just “what you can do,” but “from which perspective you create value.”

Development, infrastructure, operations—rather than being siloed, deeper mutual understanding among these roles can significantly improve organizational productivity.

A server engineer not being able to program is not a weakness. It simply means they have mastered a different strength.

■ Where Will You Start?

If you are currently unsure about your career path, take a moment to reflect.

“From where do I understand the world?”

Code? Infrastructure? Or something entirely different?

What truly matters is not the entry point, but the value you build beyond it.

I can do it! I will take the first step starting tomorrow.