May 22, 2026 · 58 min · 12 segments
Han-Shen Yuan — who led mobile engineering at eBay and Netflix and took Upwork to IPO as SVP of Engineering — explains why AI transformation is a constraint problem before it's a software problem…
Han-Shen YuanGuest
Meg BearHostAmy WilsonHost
things that I think puts you in a unique position in this moment where you're working with a variety of clients as opposed to a single mission is the opportunity to start and seeing patterns.
That's one of the things that I'm really enjoying about this point in my journey of being able to work with clients.
small startups and bigger companies and leaders in different seats and help them figure out what comes next.
But this is a moment where I am seeing so much emotional response and anxiety in very senior people because it's very easy to see that a lot of the toolkit that you have as a senior leader has to change.
And depending on your mindset, that can be invigorating or terrifying or both at the same time.
And so I just wonder, let's just stick within the software engineering discipline for now.
I'm curious if you're starting to generate any interesting thesis about how to think about for an individual, if they're strong in one kind of anchor and less in another, how should they think about becoming more comfortable in these blurred roles? And how should they think about structuring the work in a way that positions them in a better position for what the future jobs might look like?
But I wonder whether or not the answer is any different today versus like yesterday versus 10 years ago.
And I've noticed at least that the people sometimes that are the most successful professionally are those who are willing to embrace change.
And have a relatively loose grip on their identity in the sense that they're willing to do different things to get the job done.
And I got to think that that's got to be like a part of the recipe right in this moment.
It's just at this moment, there's a spotlight on it that makes it impossible to ignore that you have to be this way.
You know, we've talked about this as advantage to people that are high agency that see themselves as figuring out problems and applying, you know, whatever tools they need to solve them as opposed to seeing themselves as a very structured group.
But one of the things that I see is very different here is there really is a shift in power, the engineering side to the broader base of skills.
In a lot of organizations, there has been a very interesting tension, and I'll just focus on the product versus architect-engineer pieces because I think this is easier for most people to see.
things that I think puts you in a unique position in this moment where you're working with a variety of clients as opposed to a single mission is the opportunity to start and seeing patterns.
That's one of the things that I'm really enjoying about this point in my journey of being able to work with clients.
small startups and bigger companies and leaders in different seats and help them figure out what comes next.
But this is a moment where I am seeing so much emotional response and anxiety in very senior people because it's very easy to see that a lot of the toolkit that you have as a senior leader has to change.
And depending on your mindset, that can be invigorating or terrifying or both at the same time.
And so I just wonder, let's just stick within the software engineering discipline for now.
I'm curious if you're starting to generate any interesting thesis about how to think about for an individual, if they're strong in one kind of anchor and less in another, how should they think about becoming more comfortable in these blurred roles? And how should they think about structuring the work in a way that positions them in a better position for what the future jobs might look like?
But I wonder whether or not the answer is any different today versus like yesterday versus 10 years ago.
And I've noticed at least that the people sometimes that are the most successful professionally are those who are willing to embrace change.
And have a relatively loose grip on their identity in the sense that they're willing to do different things to get the job done.
And I got to think that that's got to be like a part of the recipe right in this moment.
It's just at this moment, there's a spotlight on it that makes it impossible to ignore that you have to be this way.
You know, we've talked about this as advantage to people that are high agency that see themselves as figuring out problems and applying, you know, whatever tools they need to solve them as opposed to seeing themselves as a very structured group.
But one of the things that I see is very different here is there really is a shift in power, the engineering side to the broader base of skills.
In a lot of organizations, there has been a very interesting tension, and I'll just focus on the product versus architect-engineer pieces because I think this is easier for most people to see.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.
