Thuan Pham
Uber's first Chief Technology Officer, from 2013 to 2020; later CTO of Coupang and of Faire.
Thuan Pham did not write this page. What is this?
It collects the places they publish and what they have said there, each linked to the source. They have no account here. Is this you? Claim it, correct it, or ask us to remove it from ppll.
Where they publish
No channels checked yet. We list a place only once someone has opened it and confirmed it is theirs, so this stays empty rather than guessing.
Beliefs
Korrents What they believe 24 beliefs — each backed by an exact quote.
Each is a — compiled by korrents.com, not by them: the one-line wordings are korrents', the quotes are theirs.
Recent
A technology being right is never enough on its own: whether it wins turns on whether the world is ready for it and whether the economics work at that moment.
It's not about just a technology. It's about whether the world is ready for it, whether it's economically feasible.
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
Growth without profit is not yet a company: fast growth only makes a business durable once it has been converted into sustained profit.
There has to be sound business model that makes sustained profit, right? Growth and profit. Growth alone eventually burn, you know, money and that's not good.
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
Today's AI boom will end the way the dot-com boom did — consolidation, a wave of failures and a few genuinely great companies — and customers, not argument, will decide which is which.
There may be a lot of AI things that's going on right now, right? Uh eventually some of these things will consolidate, some will go under, some will become really awesome solutions and all that stuff. And so, but the the market will sort it out.
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
Show 21 more
A career is not built by searching for jobs but by accumulating a reputation slowly, so that when you become available the opportunities come to you.
if you try to do a really good job at every company you've been working well with all the people that you work with, including your own team, your peer, whatever it is. Over time, very slowly, you accumulate a decent reputation in people's mind.
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
How big a system will eventually have to be is not worth speculating about; the only useful question is how long the one you have has left before it hits the wall.
the question about how big it can possibly grow nobody knows really. But it's actually not fruitful to pontificate on that.
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
Repeated rewrites are the correct answer under fast growth, because a system specified to scale forever would take so long to build that the company would die before it shipped.
Let's say if my requirement for the engineer was build a system that will scale infinitely to the test of time, it might take a year. We never get there. We'll die before then.
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
The right way to specify a rescue rewrite is a couple of scaling constraints and no new features at all, so that hardware can absorb the growth the team has no time to design for.
No new feature necessary. Just make sure that we can do that. And then that allow the business the company to just pour a whole bunch of hardware behind that and it will scale.
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
A technical leader should let engineers find the flaw in their own design through leading questions rather than announce it, because a discovered flaw is acted on and a reported one is argued with.
pretty soon by asking those leading question, the engineer now discovered a flaw that this thing would not scale,
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
Launching the hardest case first beats the cautious order of smallest-to-largest, because after the hardest one everything that follows is downhill.
that was the most brilliant thing because by doing the hardest thing first once you launch that everything else is downhill from there
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
Uber's thousands of microservices were not an architectural preference but a survival decision: under that growth only independent, unblocked teams could build fast enough to stay alive.
none of us wanted to go through that extreme but lots of time when you are under a lot of pressure and no time to react other than just to survive that scale that keep on coming at you, you have to make uh decision that increase uh speed and velocity because speed and velocity allow us to build quick enough to survive
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
Breaking up a monolith takes years rather than months not because the work is hard but because the business keeps adding to it faster than you can pull pieces out.
had we freeze time, that piece of code could be decomposed in a matter of 3 to 6 months. But it took us 2 years to do that because as we peel out a piece of code, the business keep on going forward, right?
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
The organising rule under extreme growth is that no team may block another — even when honouring it means adding to the very monolith you are trying to dismantle.
the philosophy we all operate at the time was no one should be blocking anybody else. No one can block anybody else.
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
A functionally organised engineering team seizes up at around a hundred people, because every feature then has to be negotiated against every other team's bandwidth.
every feature that we want to put out has to be queued up on mobile development bandwidth dispatch bandwidth and it become impossible to navigate tradeoff because every feature you want to do you have to go negotiate with so many team
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
Depending on open source you cannot fix is the frightening kind of outage, because at your own scale there may be nobody in the world you can pay for an answer.
I don't mind if we think we can do something of our own problem it's terrifying when we have a major problem and we depend on somebody else
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
A company should manufacture fresh internal challenges for its best people, because the alternative is that they go and find those challenges at another company.
I look at um the talent base and I think it is best for us to create opportunity for people to keep on growing with fresh new challenges within the company because if we don't do that they would leave the company
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
A company's staff-engineer bar should be set against the best companies in the industry rather than against its own history, which is what makes title inflation a real cost.
we have a very clear definition and expectation of what it is at the staff engineer level because we benchmark ourselves to all the great company out there Google, Facebook and all that
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
Engineering offices abroad should be opened where world-class talent already lives, not where labour is cheap — you bring the work to the talent rather than moving the talent.
We didn't go to other places because of cost savings like that. We go there because we have need and we have world class talent
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
Directing a swarm of coding agents is a different, multi-threaded way of thinking that costs more cognitive load, and the engineers who make the switch have doubled their output.
it required a different way of thinking and the cognitive load might be a little higher but the output is dramatic and we have seen our best engineer double their output.
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
AI has already made sweeping mechanical changes cheap; the unsolved problem is getting the same productivity when adding features to an old, entangled codebase.
we're trying to crack the next frontier which is how we get that level of productivity increase and output building new features on top of a code base that are older,
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
AI tooling has not compressed the gap between great and average engineers: it is still two or three times, and for the same reasons as before — curiosity and appetite for the bleeding edge.
we see the difference between the great engineer and an an average engineer is still two 3x in terms of their capability. They're more inquisitive. they're at the bleeding edge more, they're more innovative,
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
Standing still is now falling behind: as the world speeds up, complacency is the one professional habit that is fatal.
Complacency is death. I mean like every the world will move faster and faster and the moment we stand still we are falling behind.
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
Talent density is self-protecting: once a team is made of A players it will only hire more of them and will not tolerate anyone who is not performing.
when you have team A, team A will just want to hire more A level players and yeah, they just intolerant of anybody who's not performing,
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
At every level of management your job is to see further ahead than the people who report to you, because they are busy with the near term and nobody else will do it.
your job is to see a little bit further out than your folks, right? Because your folks are busy working on the near-term things,
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
A company that stops hiring new graduates because AI makes juniors look unnecessary will have no senior engineers in a few years' time.
the best of the best still get offer from us because if we don't hire those folks today, what senior engineer will we have for yeah years from now, right? You have to feed the talent pipeline
Scaling Uber with Thuan Pham (Uber's first CTO) Said 1 Apr 2026
What is a korrent?
A korrent is a belief a person has stated in their own words: one sentence stating the claim, backed by a quote and a source, kept at korrents.com.
Under a name here, the quoted block is what they actually said. The korrent beneath it is the claim those words support, in korrents' wording — tap it to see the record, its source, and who else holds it.
Nobody here wrote their own korrents. They are compiled from public statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they do, this site shows a machine translation beneath the post, in this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the serif above is exactly what the person published, and it is what to quote them on. A translation can be wrong in ways that matter, especially about tone.
Only the post's own words are translated. A quoted post, a linked article and a belief on korrents.com are left in their original language.