5 Things World-Class Engineers Do That You Don't

Steve Huynh · Capital Gains · Jul 1

World-class engineers distinguish themselves not through raw intelligence or effort, but through strategic habits that prioritize continuous growth and organizational impact. Instead of waiting for annual reviews, elite engineers assess their progress on a monthly cadence, focusing on acquiring new, practical capabilities. They also recognize the limits of individual output by actively amplifying the work of those around them and absorbing technical complexity to deliver simplified, user-focused "packaged engineering" to their clients.

Furthermore, top-tier engineers separate themselves from the crowd by tackling unglamorous, non-consensus problems that peers overlook, rather than competing on the same tasks as everyone else. They also transform personal failures into institutional assets by developing tools or workflows that prevent the team from repeating their mistakes. Ultimately, the career trajectory of these engineers is defined by their ability to scale their influence and turn setbacks into lessons for the entire organization.

6 mins read · 1,562 words

Highlights from this article

“People wait until they are not getting promoted to realize, ‘Oh, I’m not growing.’ That is a very lagging indicator. The way I could tell I was not growing was by asking myself, ‘What did I do this month that I couldn’t do last month?’”
And he keeps shortening the loop as the field speeds up: “Given how fast things are moving now, people should continue to compress that time frame.”

Jul 15 View on Readwise ↗
Do this instead: Look back at the last month and name one new skill or capability you picked up and can already put into practice. If nothing comes to mind, choose one thing this week that you will commit to learning and using before the month ends. Make it concrete enough to apply, for example, a technique or a workflow you can take into a real task.

Jul 15 View on Readwise ↗
learned the hard way: raw individual output has a ceiling, and the way up past it runs through other people.
Helping people is one of the few real win-win-wins in this job. The person you help levels up; the company ends up with a stronger engineer; and you get the credit for scaling past your own two hands.

Jul 15 View on Readwise ↗
The engineers wanted to expose the system’s real structure. Bezos wanted the complexity hidden so the customer never had to feel it.
Christopher calls what AWS sells “packaged engineering,” and that phrase is the tell. The best engineers treat the messy internals as their own problem to absorb, so the person on the other side of the interface gets something simple.

Jul 15 View on Readwise ↗
Smart and hardworking is the price of entry, and almost everyone in the building has paid that fee. If everybody, including you, is out-grinding everybody else, and if the people around you are every bit as capable as you are, that makes you average.
Separation from the average comes from working on something different.
The best engineers will find the non-consensus bet or the unglamorous problem that nobody else wants to tackle, and they will plant their flag there.

Jul 15 View on Readwise ↗
Do this instead: Name the one thing your most talented peers are all competing on, then find the valuable problem next to it that none of them have claimed. Kun Chen did exactly this at the start of his career at Bing. While everyone else worked the roadmap they were handed, he used his spare cycles to build a tool that let the search team see where users clicked on the results page. Nobody had asked for that tool, but that work carried his first promotions.

Jul 15 View on Readwise ↗