Quality Engineering Has an Identity Crisis… and AI Just Walked Into the Room

If you asked ten companies what Quality Engineering means today, you would probably get ten different answers… and at least three job titles nobody can properly explain.

For years, our profession kept reinventing itself: from manual testing, to automation, to Agile, DevOps, and now into a world where AI can generate code, write tests, and produce dashboards that look impressively complete.

And yet, despite all that progress, many teams still struggle to answer one uncomfortable question:
What exactly are we now?

Are we still the people who validate at the end? Or should we be shaping quality far earlier — influencing design, challenging assumptions, and protecting trust before software reaches users?

Now AI has entered the room, and with it comes a new kind of anxiety. Not because AI is replacing everything. But because it is exposing what was mechanical in our work — and forcing us to explain the parts that were always human. Across the strongest conversations shaping our industry right now, one pattern is clear: the future value of Quality Engineering is not speed alone.

It is judgment.
It is context.
It is heuristic thinking.
It is knowing when a system looks correct but still feels wrong.

Because AI can generate hundreds of test cases in seconds. But it still cannot imagine a frustrated customer at midnight, trusting a product that quietly fails them in exactly the wrong moment.

This keynote explores why Quality Engineering may be facing an identity crisis, why that is not a weakness but a turning point, and which future skills will matter most next: context engineering, trust architecture, strategic questioning, and the confidence to challenge what machines confidently declare complete.

For years we fought to prove testing was more than bug finding. Then just as we became quality engineers, AI arrived and asked us to explain ourselves all over again.

That may feel uncomfortable.

But perhaps this is exactly the moment our profession becomes most valuable. Because tools will continue to change. But people who understand risk, confidence, and human impact will always matter. And in an age of intelligent systems, that may become the most important skill in software delivery.