Mat Wisner

A Technologist Who Chose the Conversation

Wisner went to college for a business degree in Management Information Systems, the discipline that mixes technology fundamentals with programming coursework. The plan was straightforward. Coding looked like the well paying career, and his peers agreed. Then he graduated into the job market and started interviewing for programming roles in the Pacific Northwest, reaching late stage rounds with Washington Mutual, the banking company that no longer exists.

Almost by chance, he also landed interviews for a technical recruiter role at a staffing agency in the same region. That path looked more interesting to him than heads down programming, because it sat at the intersection of what he had studied and the conversations he wanted to have with technologists and companies. He took the agency job as his first out of college, and the timing was extraordinary. The region was in a massive growth cycle, and the agency supported contract staffing for Microsoft, Expedia and many other companies scaling at once. What he hoped the role would give him, it gave him. Every branch of his career since traces back to that decision.

The Idea That Became Amazon Future Engineer

Years later, at Amazon, Wisner was leading recruiting inside the consumer business, spanning technical recruiting for multiple businesses and applied researcher recruiting. Sitting across from the company's technology leaders, he kept noticing the same structural problem. By the time a recruiter first meets a computer science student, that student is at the end of an undergraduate degree and effectively already formed. If the goal was to see more people, and different kinds of people, arriving at that moment, the intervention had to happen far earlier in the journey.

His recruiting leader backed him in pitching the idea, and it became Amazon Future Engineer, a program that still runs today. It started supporting high schools, focusing on the schools across America with the greatest need and no computer science offering, and worked with teachers to get them trained. To launch it, Wisner moved out of recruiting entirely and into a product management job family inside the business, a discipline he had never formally practiced, in a sector, public education, whose bureaucracy he had never navigated.

He is candid that doubt crept in. What carried the work was the same thing that has carried the rest of his career: persistence, and a refusal to abandon a good idea before it has been iterated into something that scales.

Two Leaders Worth Naming

Ask Wisner who shaped him and he names roles rather than resumes, but the lessons are precise. The first was his recruiting leader at Amazon, who broadened his horizons at the exact moment the idea started drifting outside his realm of expertise. Rather than pull him back to his lane, that leader said keep taking it forward, don't give up. Sponsorship, in other words, at the point of maximum uncertainty.

The second was the business leader he reported to once the program moved into its own unit, a technologist by trade who kept showing up for him across his time at Amazon and even as he moved on from the company. That leader offered encouragement and, just as importantly, straightforward feedback, and Wisner valued hearing it through a genuine technologist's lens at a time when he was learning a domain he did not own. Both leaders modeled the same thing: expertise given generously to someone who does not yet have it.

The Case Against Replacing Early Career

Few executives are better positioned to referee the argument about AI and entry level hiring, and Wisner thinks the early consensus was simply wrong. The first wave of commentary held that AI would wipe out junior developers by absorbing their tasks. He believes the field has advanced past that. The labor math does not work: junior engineers have to be hired and developed, because they are the only source of the principal and distinguished engineers every company is competing for. Investment in that development is not charity, it is supply.

There is a second dynamic that the doom narrative misses. Early career talent is far closer to generative AI native than many of the professionals now ramping up on it. What he has read and found most resonant is the reframe that today's junior engineer is starting to look like the mid level engineer of three or more years ago, thanks to what AI does across the software development life cycle, writing code faster, generating unit tests faster. The consequence is not fewer hires. It is appetite. As productivity rises, companies want ten times more, because work they could never get to before is suddenly in reach.

Inside the function, he sees recruiting as ripe for the same treatment. Sourcing tasks and much of the candidate life cycle can be made faster and clearer, and there is real opportunity to delight candidates through speed, efficiency and clarity. But he is honest about the state of play. It still feels like early days. Peers are exploring emerging tools, things work in pockets, most companies are focused on one vendor area, and no one has yet assembled the whole life cycle into something beautiful end to end. The most interesting results he has seen so far have come from homegrown, organic activity by his own people.

Leapfrog, or Be Overtaken

Wisner's talent architecture and internal mobility teams recently built an algorithm for in demand roles that weighs labor need, external market supply, internal supply and exposure to each. Assembling the data sources and getting it all connected was a genuine accomplishment, and the team was proud of it. Then Walmart's chief talent officer delivered the challenge that Wisner now repeats as a discipline: you have to leapfrog and keep moving faster, because by the time everyone aligns on a static list, the list has already changed. Hence the algorithm, and hence the next build, a live system with all the data flowing in so the team can watch trends day to day. Even within the last year, the roles they were oriented toward have shifted.

The deeper shift he is tracking is that the buckets of skills sitting underneath job titles are rearranging. Software engineering and product management are merging at the edges, with product managers coding more and engineers building product requirement documents with AI. That has major implications for what talent leaders recruit, how they recruit it, and what advice they give business leaders.

His counsel to peers follows directly. Operational excellence, running the recruiting operation cleanly and smoothly, remains the baseline of most roles, but the weight is shifting toward strategy and forward looking judgment. Talent leaders who are not innately curious about where the future of work is heading with AI and skills risk losing the perspective that makes them credible advisors, and the field is moving too fast to recover it later. Be pragmatic, be disciplined, and keep looking forward.