back to top
July 21, 2026

We Predicted These Roles a Year Ago. Now Clients Are Asking for Them

mobile: We Predicted These Roles a Year Ago. Now Clients Are Asking for Them's image

For a long time, software teams operated with clear, separate roles. Product managers focused on business objectives and customer requirements. Engineering teams focused on turning those specifications into functional code. Each role had a specific scope, and success meant executing deeply within that single discipline.

AI changed that.

Now that AI handles much of the routine technical work, the boundaries between these disciplines are disappearing. The secret to a successful project is no longer being the deepest expert in one area. It's about connecting disciplines, understanding product strategy deeply enough to make technical decisions, and understanding code deeply enough to make product decisions.

A year ago, our leadership saw this coming. Because we saw it coming, we've been preparing. We believed AI would change what companies value in the people doing the work.

The professionals in highest demand today work across disciplines, combining product strategy, code, design thinking, and quality rigor. This integrated thinking is what elevates engineering into great products.

The two roles we're seeing emerge are the Technically Savvy Product Owner and the Product-Driven Full-Stack Engineer.

Technically Savvy Product Owner

The Technically Savvy Product Owner blends design, QA, and engineering knowledge to deliver solutions grounded in technical, strategic, and customer understanding. This is someone who has absorbed multiple disciplines and uses that understanding to ask better questions, make faster decisions, and close the gap between what clients say they need and what they actually need.

  • They drive design conversations: The Technically Savvy Product Owner understands user experience principles deeply enough to push back and ask: "Does this solve the real customer problem?" "Are we truly solving for the end user?" They ensure design decisions are grounded in customer reality.
  • They think like a business strategist: They sit in product meetings, map the business logic, and identify the discrepancies between a client's requests and their actual business needs. They ask: "What problem are we actually solving?" "Why does this specific feature matter to the business?"
  • They speak the language of engineering: They understand why a feature takes three weeks instead of three days, allowing them to manage client expectations accurately and protect the engineering team from unrealistic deadlines.
  • They anticipate edge cases like a tester: They've spent enough time in QA discussions to understand that the gap between a feature "working as designed" and "working in reality" is where actual product quality lives.

The Technically Savvy Product Owner is the voice of the customer. They sit across from clients and understand not just what's been requested, but what's actually needed. The gap between those two things is often where products succeed or fail.

How We Anticipated The Technically Savvy Product Owner

The growing demand for these roles isn't surprising to us because we've been investing in these capabilities for years. At Ballast Lane Applications, collaboration has always been a core part of how we work because teamwork is one of our core values.

As AI gave product managers the ability to prototype directly in code, we recognized that the designer's role was shifting from creating static mockups to interactive prototypes that could be validated immediately. We believe that strong products emerge from close collaboration between product, design, QA, and engineering teams, a philosophy you can explore more deeply in our article on prototyping in code and the changing role of design.

Product-Driven Full-Stack Engineer

The product-driven Full-Stack Engineer is a specialist across front-end, back-end, and DevOps, but stands out by applying product thinking as much as technical skill. This professional aligns every technical approach with product impact and user needs.

  • They measure business impact: When they suggest an optimization or a new technical approach, they evaluate how it affects the user experience and connects to the company's long-term business strategy.
  • They collaborate naturally with creative teams: They're completely comfortable sitting in design reviews and customer research sessions because they genuinely care about user outcomes. They ask questions about customer needs because they want to understand, not just because the process requires it.
  • They lead with strong communication skills: These engineers are great communicators who can easily break down complicated client requests and turn them into clean, reliable software. They can explain technical decisions in business language and business decisions in technical language.
  • They know when AI helps and when human judgment is essential: As part of BLA's 100% AI-certified engineering team, these engineers have developed a critical skill: recognizing the difference between tasks where AI accelerates the work and decisions where human judgment is non-negotiable.

How We Anticipated The Product-Driven Full-Stack Engineer

This is where our largest investment is paying off. At Ballast Lane Applications, our engineering team is 100% AI-certified. This allows us to have engineers with a shared baseline of AI competency, preventing inconsistency and mistakes.

Our engineers learn product thinking and understand why a feature matters before they build it. This approach is a core part of the three-pillar model we engaged in 2026, which our VP of Engineering breaks down in his explanation of AI as a core capability at Ballast Lane.

How Our Recruitment Team Looks for This Talent

Traditional tech interviews are designed to test how fast someone can code, which makes it incredibly difficult to hire for these new, cross-disciplinary roles. Recruiting for these roles requires a fundamentally different approach.

We sat down with Vera Spichka, our Senior Talent Acquisition Specialist, to understand how she identifies this talent in early conversations.

"For these two roles, I focus on identifying early in the conversation whether a candidate is a stronger fit for the Technically Savvy Product Owner position or the Product-Driven Full-Stack Engineer position, since the focus of each role is fundamentally different.

For candidates leaning toward the Product-Driven Full-Stack Engineer role, I focus on understanding how hands-on they are with software development, architecture, technical problem-solving, and delivering features end-to-end. I look for engineers who not only write code but also understand the impact of their work on the product.

For candidates who appear to be a better fit for the Technically Savvy Product Owner role, I assess their ability to bridge business and engineering teams, their understanding of product strategy, requirements gathering, prioritization, stakeholder management, and their level of technical fluency. While they need to be comfortable discussing technical concepts, their primary strength is driving product outcomes rather than being deeply involved in day-to-day development.

As we chat, I adapt my questions, and I can determine which role better aligns with the candidate's experience, strengths, and career interests, ensuring a more accurate match for both the candidate and the client."

The Future of These Roles

The demand for Technically Savvy Product Owners and Product-Driven Full-Stack Engineers highlights a permanent shift in software development. As AI execution becomes faster and more accessible, the real value lies in the ability to connect disciplines and find professionals who understand the product well enough to make technical decisions and understand the technology well enough to make product decisions.

Building a team capable of filling these roles requires a deliberate, long-term commitment to hiring and development. At Ballast Lane Applications, we made that strategic choice over a year ago. We're developing product thinking in engineers and technical fluency in product leaders. We're proving that the best software happens when disciplines team up.

Today, as the market scrambles for this exact talent, our clients are already seeing the benefits.