The 10x Engineer Reality: Invisible Excellence and What Actually Matters

"How to be a 10x engineer" – interview with a standout dev

TLDR: An anonymous interview with "Sam," a top 3% Uber engineer with zero public GitHub activity and no social media presence, reveals that standout performance comes from task breakdown, stakeholder communication, boundary-setting, and relationship-building—not visibility or technical showboating.

Summary: The concept of the "10x engineer" is controversial and often dismissed as a myth, but this interview with "Sam"—a pseudonym for one of the top performers at Uber—challenges many assumptions about what makes an engineer truly exceptional. Sam's profile defies conventional wisdom: empty GitHub for the past 5 years, minimal LinkedIn presence (just company names, no technologies or projects listed), no social media footprint, and yet consistently rated in the top 10% of engineers, with one year in the "top, top" bucket reserved for the 3% best engineers at Uber.

Sam's job search experience reveals the power of reputation over visibility. When exploring new opportunities, Sam didn't apply for a single role. Instead, former colleagues reached out desperately trying to hire them. At the time of the interview, Sam had three warm leads, with one startup founder ready to create a new position specifically for him despite not actively hiring. This pattern—being recruited through relationships rather than applications—has defined Sam's career trajectory.

The interview covers practical strategies that separate standout engineers from the rest. Getting things done isn't about pulling all-nighters (though Sam did that early in their career); it's about high-level task breakdown, communicating delays as tradeoffs rather than failures, and maintaining stakeholder communication channels. When roadblocks appear, Sam presents options: "We can ship on time if we cut X and Y features" or "We need to push the date by 2 weeks, or 1 week if we're comfortable dropping this feature." This framing gives stakeholders agency and makes delays a shared decision rather than an engineering failure.

Boundary-setting emerges as a critical skill. Sam blocked out calendar time to leave for dinner with family during Uber days, sometimes working during commute or after kids' bedtime when necessary. The key is knowing your priorities—family first, work second—and making that clear to colleagues. Sam's advice: "Know your number one, number two, number three priorities, and arrange your workday so you do your top priorities. Don't compromise on the most important one!"

Office politics, often dismissed by engineers, turned out to be essential for getting things done at scale. Sam learned to build relationships with influential colleagues, pre-sell ideas before formal meetings, and approach engineers directly before escalating to managers. The strategy: frame requests around customer problems ("I noticed a customer has this problem, and to fix it, we probably need to touch the system you own. Can you explain how it works?") rather than demanding changes. This builds consensus from the bottom up while respecting others' expertise.

Perhaps most counterintuitively, Sam emphasizes energy management over time management. The best work comes from projects that generate energy rather than drain it. When Sam stopped getting energy from their last job for many months, despite discussing changes with management, they quit without another position lined up. "I can go for some time without getting energy from my work, but it drains me. I try to catch myself before it gets too bad." This awareness—recognizing when work is no longer sustainable and acting before burnout—separates sustainable high performers from those who crash and burn.

Key takeaways:

• Public visibility (GitHub, social media) doesn't correlate with engineering excellence—reputation and relationships do
• Communicate delays as tradeoffs with options, not as failures or problems
• Set boundaries clearly: know your top 3 priorities and protect the #1 priority ruthlessly
• Build relationships with influential colleagues and pre-sell ideas before formal meetings
• Approach other engineers directly about customer problems before involving managers
• Energy management matters more than time management—leave before work drains you completely
• Task breakdown and estimation skills improve with practice and are foundational to delivery

Why do I care: This interview challenges the performative aspects of tech culture that I've seen distract engineers from actual impact. The empty GitHub profile is particularly striking—in an era where developers feel pressure to maintain public portfolios, contribute to open source visibly, and build personal brands, Sam's success proves that deep, consistent delivery within your organization matters far more. For senior engineers and architects, the lessons are clear: invest in relationships, communicate proactively, set boundaries, and focus on energy-generating work. The "10x" multiplier isn't about coding speed—it's about leverage through communication, trust, and strategic focus. This is especially relevant for consultants who must deliver across different teams and codebases quickly.

"How to be a 10x engineer" – interview with a standout dev