The Rise of the Full-Context Technologist

A discussion came up at work recently that has been on my mind ever since.

The question was simple:

Will AI ultimately make Product Managers more valuable, or software engineers? And who will still have jobs 5 years from now?

Like many debates around AI, I think we’re asking the wrong question.

The future doesn’t belong to Product Managers- and it doesn’t belong to software engineers.

It belongs to people who can consistently solve business problems using technology.

Over the past year, I’ve noticed something interesting. AI isn’t just making us more productive, it is rapidly dissolving many of the boundaries that once defined our roles.

AI Is Blurring the Lines

Historically, software organizations were built around specialization.

Product Managers understood the customer.

Designers crafted the experience.

Frontend engineers built the interface.

Backend engineers built the services.

Platform and DevOps engineers managed infrastructure.

Data teams owned analytics.

Security teams protected the platform.

These distinctions existed for good reason. Modern software is incredibly complex, and each discipline developed deep expertise over many years.

But AI is changing how we work.

Today, a Product Manager can build functional prototypes, explore databases, generate technical specifications, and validate ideas before ever involving engineering.

A frontend engineer can scaffold APIs, generate database migrations, troubleshoot cloud infrastructure, and contribute to backend services.

A backend engineer can confidently build polished user interfaces or improve accessibility with AI assistance.

None of these people suddenly become experts outside their discipline.

But they become dramatically more capable.

The distance between these roles is shrinking - fast.

The Hidden Cost of Specialization

Specialization has always made sense.

But it comes with a cost we rarely talk about - communication. Every additional role introduces another handoff.

Requirements need clarification.

Architecture needs alignment.

Teams wait on each other.

Context has to be transferred.

Decisions require meetings.

As organizations grow, a surprising amount of engineering effort shifts away from building software and toward coordinating the people building the software.

That’s not a failure of the organization, it’s simply the cost of the (soon to be legacy) specialization model.

What’s changing is that AI reduces the amount of expertise required to contribute meaningfully outside your primary discipline.

Instead of work moving sequentially between Product, Design, Frontend, Backend, Platform, and Data, individuals are increasingly able to move ideas forward themselves, bringing in specialists when deep expertise is truly required rather than for every incremental decision.

Ironically, this reminds me of the industry’s long pursuit of the “full-stack developer.”

The idea was compelling: one engineer capable of building an entire product.

In reality, most developers naturally became stronger in one discipline than another.

AI doesn’t change that, depth still matters. What AI changes is the baseline.

It allows specialists to work far more effectively across adjacent disciplines, reducing unnecessary communication overhead and enabling smaller teams to deliver outcomes that once required much larger groups.

Business Understanding Becomes a Technical Skill

The best engineers I’ve worked with were never simply excellent programmers.

They understood the business.

They knew how customers behaved.

They understood how the company made money.

They could connect technical decisions to business outcomes.

When they proposed solutions, they weren’t solving engineering problems.

They were solving business problems.

AI can accelerate implementation, but it can’t replace judgment.

The same is true for Product Managers - the strongest Product Managers increasingly understand enough about technology to reason about architecture, complexity, tradeoffs, and feasibility.

Not because they need to become senior engineers, but because understanding technology allows them to ask better questions and make better decisions.

Context Becomes a Competitive Advantage

As AI becomes more capable, I think one of the biggest opportunities for engineering organizations has very little to do with coding, it’s more about context.

Every company has documentation but very few have shared understanding.

Most organizational knowledge lives inside people’s heads, buried in Slack or Teams conversations, old incident reports, architecture diagrams, and years of accumulated experience.

Imagine instead a living, domain-specific context repository.

This idea is exactly what I introduced at Visable - and it’s working really well for our teams.

It’s not just the same old documentation, but a continuously evolving knowledge layer containing:

• Business terminology and domain concepts.

• Product definitions and customer workflows.

• Frontend and backend service relationships.

• APIs, events, and data models.

• Service ownership.

• Architectural decisions and their rationale.

• Incident history and postmortem learnings.

• Engineering standards and operational runbooks.

Combined with AI, this becomes incredibly powerful.

A new engineer can onboard in days instead of weeks.

An engineer contributing to an unfamiliar team can quickly understand the surrounding systems.

A Product Manager can answer many technical questions independently before pulling engineers into discussions.

A data analyst can understand business terminology and service relationships without relying on tribal knowledge.

Engineers spend less time answering the same contextual questions and more time solving genuinely difficult problems.

If AI becomes the interface to software development, then organizational context becomes the fuel that makes it effective.

I believe in the future, context will become infrastructure.

The Rise of the Full-Context Technologist

For years we’ve talked about T-shaped professionals - people with deep expertise in one discipline and broad knowledge across many others.

AI is pushing us one step further.

The most valuable people won’t simply have breadth, they’ll have context.

They’ll understand customers, business strategy, technology, operations, and AI well enough to connect ideas across traditional boundaries.

Their career might begin in Product.

Or Engineering.

Or Data.

Or Design.

It won’t matter nearly as much as their ability to understand the entire system around them.

Depth will always matter, but pairing that depth with business understanding, technical curiosity, and the ability to work across disciplines will become an increasingly valuable combination.

Looking Ahead

I don’t think software engineering is disappearing.

I don’t think Product Management is disappearing either.

Both professions will continue to evolve.

What’s changing is the distance between them.

The organizations that thrive won’t necessarily be the ones with the most specialists.

They’ll be the ones that reduce communication overhead, capture organizational context, and empower small, AI-enabled teams to move quickly.

Likewise, the professionals who thrive won’t be defined by a single job title.

They’ll be defined by their ability to understand the business, leverage technology, and solve meaningful problems regardless of where those problems originate.

AI isn’t replacing our professions- it’s supercharging them.

I truly believe the people and organizations that embrace that shift early will have a significant advantage over the next five years and beyond.