Lenny's PodcastTaking control of your career | Ethan Evans (Amazon)
CHAPTERS
- 0:00 – 0:36
Why inventiveness is about a few great ideas (not constant breakthroughs)
Ethan opens with a counterintuitive take: you don’t need lots of ideas to be seen as inventive—one strong idea can take years to fully express. He uses examples like Prime and Kindle to show how sustained iteration, not nonstop ideation, creates “inventor” reputations.
- •A small number of good ideas can power a long inventive track record
- •Execution/iteration is the long tail of any invention
- •Examples: Prime and Kindle improving over decades
- •Framing inventiveness as expression over time, not flashes of genius
- 0:36 – 4:37
Ethan’s Amazon background and what this episode will cover
Lenny introduces Ethan’s 15-year Amazon career, major products he helped build, and his current work coaching leaders. The episode roadmap is set: the Magic Loop framework, interviewing, failure lessons with Jeff Bezos, Amazon leadership principles, contrarian takes, and a lightning round.
- •Ethan’s leadership scope: VP at Amazon, teams up to 800+
- •Key products: Prime Video, Appstore, Prime Gaming, Twitch Commerce
- •Current focus: executive coaching and leadership courses
- •Episode agenda preview
- 4:37 – 8:31
The Magic Loop: a practical framework for career growth
Ethan explains the five-step Magic Loop designed to help people advance even with an imperfect or busy manager. It starts with solid performance, builds trust by helping your manager, and then aligns your goals with the team’s needs through repeated cycles.
- •Step 1: Do your current job well (get aligned with your manager’s expectations)
- •Step 2: Ask your boss how you can help
- •Step 3: Do what they ask (even if it’s not glamorous)
- •Step 4: Ask to align help with your personal goal (promotion/role/skills)
- •Step 5: Repeat to compound trust and opportunity
- 8:31 – 11:00
Why it’s called “magic,” and why managers often don’t manage careers well
Ethan shares why the framework earned its name: it works so reliably that some people feel overwhelmed by the new opportunities it unlocks. He also explains why you often can’t just ask for growth—many managers are well-intentioned but too busy or not skilled at career development.
- •“Magic” effect: rapid opportunity and promotions can snowball
- •Common exception: truly exploitative managers (rare)
- •Most managers are busy; career development gets deprioritized
- •The loop is designed for imperfect, overloaded managers
- 11:00 – 12:46
Clarifications: ownership of your career + leaders can run the loop too
Ethan addresses a common objection—“my manager should notice”—by emphasizing controllability: the loop puts progress in your hands. He also notes managers can initiate the same partnership with their reports to create a virtuous cycle of development and performance.
- •Stop waiting for “should”; focus on what you can control
- •Career progress is faster when manager-report becomes a partnership
- •Managers can proactively ask about goals and create aligned opportunities
- •Trust and rapport are the engine behind the framework
- 12:46 – 15:19
Real-world results: entry-level wins and executive-level acceleration
Ethan offers social proof from both ends of the seniority spectrum. One early-career professional used the loop to earn major raises and multiple promotions, while an Amazon engineer used a similar growth partnership to rise from mid-level IC to executive leadership over ~8 years.
- •Example 1: large raise and accelerated job progression after layoffs
- •Example 2: SDE2 → senior engineer → manager → director → exec leader
- •Growth is amplified by consistent stretching into bigger scopes
- •Hard work matters, but structured opportunity and sponsorship matter too
- 15:19 – 17:19
Advanced mode: from asking for help to proactively spotting opportunities
As you become more senior, the “explicit” loop becomes implicit: leaders expect you to anticipate needs and propose solutions. Ethan warns not to jump to advanced mode too early; it requires trust so you don’t accidentally work on the wrong problems or cross purposes.
- •The loop evolves: ask → suggest → act and inform
- •Executive expectations: proactivity and anticipation
- •Trust is the gating factor for autonomy
- •Don’t skip steps; misalignment risk is high early on
- 17:19 – 21:47
Why the Magic Loop works: lonely management + human reciprocity
Ethan breaks down the underlying mechanics: managers rarely receive genuine help and are often overwhelmed, so allies stand out. The loop leverages normal reciprocity—people help those who help them—turning an oppositional manager relationship into a cooperative one.
- •Management can be isolating; assistance is disproportionately valued
- •Reciprocity is the non-exploitative “social engineering” behind the loop
- •Shifts relationship from adversarial to team-oriented
- •Also surfaces promotion gaps earlier (vs. surprise at review time)
- 21:47 – 23:09
If you’re not chasing a promotion: redefining the goal
Lenny raises the scenario where someone is happy as an IC and doesn’t want a promotion. Ethan explains the loop still applies because most people still have a goal—different projects, different team, skill growth, or healthier boundaries—and the loop helps align that with business needs.
- •Your “goal” can be role change, skills, projects, or work-life boundaries
- •Ethan used the loop to shift into gaming work he found meaningful
- •Managers often assume you want either status quo forever or their path
- •Explicit goals remove ambiguity and enable better support
- 23:09 – 28:47
Breaking out of a senior-manager plateau: scarcity + next-level behavior
Ethan explains why many leaders get stuck: director roles are limited, and the economy can tighten the funnel further. The key is to practice director-level capabilities before the title appears—strategy, influence, cross-team coordination, and letting go of detail obsession—to become the obvious pick when opportunity emerges.
- •Director roles are a structural choke point (span of control limits)
- •Growth-era “riding the elevator” is less available in lean times
- •Shift from functional excellence to influence and strategic leadership
- •‘What got you here won’t get you there’ behavior change is required
- •Be the one chosen when org reshuffles, layoffs, or expansions happen
- 28:47 – 36:06
How to become systematically inventive (and why it takes less time than you think)
Ethan shares how he learned inventiveness at Amazon, eventually earning 70+ patents. He outlines a repeatable approach: build domain expertise, schedule dedicated thinking time, and combine existing concepts—illustrated by a drone-delivery “aircraft carrier” truck concept—then iterate for years to make ideas real.
- •Amazon culture pushes “Think Big” and “Invent and Simplify”
- •Inventiveness requires expertise + dedicated uninterrupted thinking
- •Most inventions are recombinations of existing ideas
- •Example patent: truck-based ‘carrier’ enabling neighborhood drone delivery
- •Two hours a month can be enough; execution/optimization is the long work
- 36:06 – 40:46
Interviewing advice from 2,500+ interviews: enthusiasm, presence, and impact
Ethan’s interview guidance centers on signals that dominate outcomes: enthusiasm and professional presence, especially on Zoom. Beyond first impressions, candidates stand out by articulating why their work mattered—business impact—rather than listing tasks or effort.
- •Top drivers: enthusiasm and professional presentation
- •Zoom tips: be fully present, camera on, stable setting, eye contact
- •Always aim to get the offer—even if you’re unsure you want the job
- •Talk impact and outcomes, not just activities and hard work
- •Leaders hire to solve problems; show you understand the business need
- 40:46 – 53:11
Failing Jeff Bezos: the Appstore launch outage and earning back trust
Ethan recounts a high-stakes failure launching the Amazon Appstore: a key feature broke at launch, triggering a furious Bezos email thread that escalated up leadership. Ethan stabilized the situation by owning the failure, communicating a clear hourly plan, pulling in AWS experts, and later rebuilding trust through direct human interaction with Bezos.
- •Launch-day failure escalated quickly to Bezos, Wilke, and leadership
- •Response playbook: ownership + proactive updates + clear plan cadence
- •Avoiding micromanagement by restoring confidence through communication
- •AWS team provided emergency capacity to keep a flawed design running
- •In-person conversation helped de-escalate; trust can be re-earned
- 53:11 – 1:00:35
Lessons from the failure: reputation risk, safer launches, and caring for the team
Ethan extracts concrete lessons: prioritize reputation over arbitrary dates, ‘fear the New York Times headline,’ and avoid surprise launches by doing real beta testing even if leaks happen. He also regrets not supporting a junior engineer whose bug contributed to the incident, underscoring leadership accountability for psychological safety and retention.
- •Wilke lesson: don’t gamble with public trust; date < reputation
- •Operational mindset shift: ‘fear the NYT headline’ at scale
- •Process change: betas over surprise launches; leaks beat outages
- •People lesson: junior contributors need support after failures
- •Ownership includes protecting and coaching the humans behind the work
- 1:00:35 – 1:08:52
Amazon leadership principles: ‘Ownership’ language and the power of influence
Ethan shares how ‘Ownership’ was accidentally dropped during a revision of Amazon’s leadership principles and how directors pushed to restore it. He contributed the line ‘An owner never says, “That’s not my job,”’ illustrating how good ideas can influence even the highest levels, plus he highlights ‘Bias for Action’ and nuanced edits like ‘Leaders are right a lot.’
- •Leadership principles evolved through multiple major revisions
- •Directors challenged missing ‘Ownership’ and drafted replacement wording
- •Ethan’s contributed line became durable company-wide language
- •Favorite principle: Bias for Action—speed matters, reversible decisions
- •Principles are carefully edited to encode behaviors (e.g., disconfirming beliefs, diverse perspectives)
- 1:08:52 – 1:12:14
Contrarian corner: remote work innovation + doing business on a handshake
Ethan argues remote work has more room to improve than offices, which have centuries of optimization behind them, so he expects remote to win long-term. He also prefers trust-based business relationships over heavy contract dependence, accepting occasional downside for lower friction and higher trust.
- •Offices are a mature technology; remote work is early and improvable
- •Innovation is the lens: remote tooling and norms can evolve rapidly
- •Handshake-first approach: trust and word-as-bond reduce transaction costs
- •Acknowledges risk of getting burned, but prefers net benefits
- •Trust culture as a competitive and relational advantage
- 1:12:14 – 1:21:07
Lightning round and closing: books, questions, life mottos, and where to find Ethan
Ethan recommends decision-making and leadership books, shares a favorite interview question about disagreeing with leadership, and offers a personal motto about responsibility. He closes by pointing listeners to his LinkedIn writing, coaching, and his course for breaking through from senior manager to executive.
- •Book recs: Decisive; Leadership and Self-Deception; Almanack of Naval Ravikant
- •Favorite interview question: disagreeing with management/backbone stories
- •Life motto: responsibility scales with what you’ve been given
- •Would go to space (but not at today’s ticket price)
- •Find Ethan on LinkedIn; focus areas: career growth and exec readiness
