"Our Customer Was Also a Systems Engineer" — The Disappearing Boundaries of the IT Industry I Discovered in London

Where Did the Line Between IT Professionals and Business Users Go?

A Small Sense of Crisis I Felt in My Eighth Year as a Professional

Wow! My conversation with the customer felt more like a system design review than a business meeting!

It was my eighth year as a working professional.

I could already see my ninth year approaching.

By then, I had spent years building business applications as a systems engineer.

I listened to customer requirements, designed solutions, developed systems, and delivered implementations.

My role was to provide professional IT services to customers.

Then one day, a Japanese customer purchased an enterprise software package from a company in London.

I joined the implementation project and traveled to London for system training.

The training lasted two weeks.

It took place around Waterloo, an area known for its concentration of financial institutions and large corporations.

At the time, I thought I was there simply to learn a new system.

What I actually learned, however, was something entirely different.

I learned how the structure of the industry itself was changing.

Something Felt Strange About the Customer Conversations

The training sessions and project meetings began.

As a representative of the system vendor, I explained the architecture.

The data structures.

The operational design.

The interfaces.

Then the customer started asking questions.

And the questions were surprisingly sharp.

"How will this design support future scalability?"

"How will data consistency be maintained during migration?"

"What assumptions are being made in the performance testing scenarios?"

Wait a minute.

Something felt off.

These weren't business requirement questions.

These were questions that systems engineers ask.

I found myself slightly confused.

Why Did the Customer Know So Much?

After a while, I discovered the reason.

Many of the customer-side representatives had once been systems engineers themselves.

Some came from SI companies.

Some from software development firms.

Others had infrastructure backgrounds.

They had changed jobs and moved into business-side positions.

In other words, they were business professionals.

But they were also technology professionals.

This realization shocked me.

Until then, my mental model had been simple:

Customer = Business Expert

Vendor = Technology Expert

But reality was different.

The boundary between the two worlds was beginning to disappear.

Where Does the Value of a Systems Engineer Lie?

That experience forced me to think.

What exactly should systems engineers use as their competitive advantage?

Should we continue deepening our technical expertise as application specialists?

But there were server specialists.

Network specialists.

Database specialists.

Infrastructure vendors supporting every layer of the technology stack.

So where was the value of the application engineer?

Was it business knowledge?

Yet the customers often knew their business far better than we did.

And many of them had technology backgrounds as well.

They understood business.

They understood systems.

More and more people like that were emerging.

The Era of Vanishing Boundaries

Looking back, I believe the transformation had already begun.

Even before the term "Digital Transformation (DX)" became popular, business and technology were steadily converging.

In the past, responsibilities were clearly divided.

Business teams defined requirements.

IT teams implemented them.

Today, things are different.

Engineers are expected to understand business.

Business leaders are expected to understand technology.

Organizations increasingly seek people who understand both.

The boundaries separating different worlds continue to fade.

Reflections from My Eighth Year

Those two weeks in London were officially system training.

But for me, they became a period of career reflection.

Should I pursue deeper technical expertise?

Should I focus on learning business operations?

Should I move into management?

Should I remain a specialist?

In a world increasingly filled with people who understand both business and technology, what would become my unique strength?

Honestly, I did not find an answer.

But I learned one important lesson.

Do not fear change.

If boundaries are disappearing, perhaps the answer is to cross those boundaries yourself.

Not technology alone.

Not business alone.

But creating new value by understanding both.

Perhaps that is the type of professional the future requires.

It was my eighth year as a working professional.

My ninth year was just around the corner.

Looking back, the view I saw in Waterloo, London may have been a glimpse of the future of the systems industry itself.

I can do it! Tomorrow, I will take the first step forward.