Lenny's PodcastFarhan Thawar: Why Shopify always picks the harder path
By favoring pair programming, code deletion, and the harder option; Shopify compresses more craft per minute, not more hours from each engineer.
CHAPTERS
- 0:00 – 1:08
Cold open: choosing the hard path as a career unfair advantage
Farhan kicks off with a concrete example of why picking the “hard path” pays off even when it fails: it forces learning, craftsmanship, and better artifacts to show. He contrasts passive job searching (mass résumé sending) with building something real as proof of ability and a learning engine.
- •Hard choices create learning even when outcomes don’t work out
- •Building a real project (e.g., from API docs) beats sending many résumés
- •Hard paths increase exposure to smarter peers and stronger networks
- •Artifacts (GitHub, demos) compound career opportunities
- 1:08 – 5:39
Farhan’s background and the three recurring themes of his career
Lenny introduces Farhan and frames the conversation around three themes: choosing hard paths, creating organizational intensity, and hiring. Farhan agrees these themes connect in retrospect, setting up the rest of the episode’s structure.
- •Farhan’s role: VP and Head of Engineering at Shopify
- •Shopify context: large (10k+), remote, still highly urgent and first-principles
- •Conversation pillars: hard path, intensity, hiring
- •Retrospective pattern recognition: careers “connect backward”
- 5:39 – 9:37
Decision-making principle: why the hard option can be the safest long-term bet
Farhan explains the logic behind choosing the harder route when faced with multiple options: hard paths make you better even if you lose. He adds the nuance that “hard” should mean high-learning and high-signal, not arbitrarily painful or dumb complexity.
- •Easy path failing produces little learning; hard path failing still builds skill
- •Hard paths tend to place you among stronger peers and mentors
- •Key filter: optimize for learning journey and people, not difficulty for its own sake
- •Use cases: course selection, career choices, and job-search strategy
- 9:37 – 13:20
Getting comfortable looking dumb: building resilience through rejection and questions
Farhan shares his “superpower” of looking stupid in public and repeatedly asking questions until he understands. He ties this to early experiences in commission-based retail—high rejection volume taught him to recover quickly and iterate instead of ruminating.
- •Asking “dumb questions” often unlocks group understanding others were afraid to ask
- •Retail/commission work builds rejection tolerance and rapid recovery
- •Use guardrails for risky experimentation, but don’t fear embarrassment
- •Save the evidence: screenshot the harsh feedback as a reminder to keep learning
- 13:20 – 19:20
Lessons from working with visionaries: ‘unreasonable’ long-term thinkers + 1% weekly execution
Lenny and Farhan explore the pattern behind Farhan working with multiple billionaire leaders. Farhan describes them as long-term, “irrational” visionaries and positions his own strength as steady execution—moving toward the vision by small weekly increments.
- •Common trait: strong long-term worldview (“what the world should look like”)
- •Farhan’s advantage: operationalizing vision with consistent progress (1% per week)
- •Deliberate partner search: list the “unreasonable” people and test compatibility
- •Personal job framework: write down values to avoid being distracted by title/money
- 19:20 – 22:07
Creating organizational intensity: output per minute, cadence, and leadership ‘pairing’
Farhan defines intensity as doing more per minute, not working longer hours. He explains Shopify’s rhythm—weekly updates and six-week reviews—and reframes check-ins as leaders “pairing” with teams to unblock and improve decisions, not micromanage.
- •Intensity goal: compress work into normal hours to preserve life outside work
- •Mechanisms: weekly GSD updates and six-week reviews with leadership/Tobi
- •Parkinson’s Law: cadence creates visible progress and urgency
- •Reframe check-ins as collaborative problem-solving (not ‘gotcha’ oversight)
- •Culture: fast change, low change-management overhead, resilience through volatility
- 22:07 – 37:18
The power of pair programming: elegance over keystrokes (and pairing with AI)
Farhan makes the case that pair programming is a highly underused management tool: it reduces thrash, improves design quality, and accelerates learning. He shares extreme examples (timed sessions with code deletion) and connects the model to AI copilots as “always-on pairing.”
- •Throughput bottleneck is design clarity, not hands-on-keyboard speed
- •Extreme discipline: delete and restart if the solution isn’t elegant quickly
- •Benefits: higher learning, less siloing, fewer distractions, better outcomes
- •Shopify usage: targeted pairing (4–8 hours/week) for key problems/incidents
- •AI copilots increasingly act as default pair programmers; best results combine AI + humans
- 37:18 – 42:44
Meeting Armageddon and distraction control: deleting recurring meetings to reclaim flow time
Farhan details Shopify’s annual “Meeting Armageddon” reset: delete most recurring internal meetings, then block new recurring meetings for two weeks. He explains why recurring meeting inertia is costly and shares how Shopify tracks meeting load to protect maker time.
- •Annual reset: delete recurring internal meetings (>2 people) and pause new ones
- •Forces deliberate re-creation of only the meetings that truly matter
- •Measured outcome: large reduction in meeting hours (notably for ICs)
- •Flow time is treated as a scarce resource; meeting load is actively monitored
- •Counterintuitive lesson: fewer default meetings, but high-leverage check-ins remain
- 42:44 – 46:52
Building platforms, not point solutions: ‘put gas in the tank’ with infrastructure thinking
Using NFT-gating demand during the crypto/NFT boom, Farhan shares Toby’s push to build enabling infrastructure rather than a single feature. The goal: make it possible for anyone to build the desired feature in an hour, multiplying future velocity and use cases.
- •Question shift: “build the feature” vs. “build the platform so features take 1 hour”
- •Infrastructure investment looks slower short-term, faster long-term
- •API-first development: write client code against the API you wish existed
- •Intensity applied to unblock future work by investing in foundational layers
- •Platform mindset aligns with Shopify’s ecosystem and extensibility goals
- 46:52 – 49:41
Deleting 1M+ lines of code: simplification as a speed and reliability strategy
Farhan explains Shopify’s strong bias toward deleting and simplifying code, including a “delete code club” and hack-day efforts dedicated to removal. He argues that maintainability, performance, and reliability improve when the codebase becomes easier to hold in your head.
- •Code is a liability; smaller systems are more resilient and understandable
- •Dedicated rituals: delete code club and recurring deletion-focused hack efforts
- •Common outcome: regularly finding a million+ lines to delete
- •Critique of AI metrics: writing code is less impressive than deleting the right code
- •Simplification is directly linked to higher speed and easier platform evolution
- 49:41 – 57:44
Three buckets of building: experiments vs. features vs. infrastructure (and generating more options)
Farhan outlines Shopify’s taxonomy for work and how it guides engineering tradeoffs: experiments help learn, features leverage existing infra, and infra enables many futures. He also shares Toby’s insistence on generating more options beyond A/B to find better “right answers.”
- •Classification: experiment (learn), feature (ship on infra), infrastructure (enable scale)
- •Hard part: correctly recognizing when to invest in infra vs. ship a feature
- •Toby’s heuristic: there are many right options—don’t stop at the first acceptable one
- •Leadership pattern: send teams back to generate more options for better solutions
- •Connects back to “choose the hard path”: make the feature easy to build (via infra)
- 57:44 – 1:03:11
Remote work and the ‘trust battery’: intentional IRL to recharge collaboration
Farhan describes Shopify as 90–95% remote, supplemented by intentional in-person moments (Summit, bursts, optional offices). The “trust battery” metaphor explains why relationships and collaboration can degrade over time remotely—and how to recharge them deliberately.
- •Remote-first, with designed IRL moments: company Summit and team ‘bursts’
- •Trust battery: trust depletes remotely and must be recharged intentionally
- •Optional offices: come in if you want, not mandated hybrid schedules
- •Hiring advantage: remote enables hiring the best people anywhere
- •Use cases for IRL: Black Friday/Cyber Monday war rooms, hack days, prototyping bursts
- 1:03:11 – 1:09:49
Hiring philosophy: interviews are weak predictors—optimize for real work signals and fast fit checks
Farhan argues interviews don’t reliably predict performance and prefers job-trial-like signals whenever possible. He explains Shopify’s efforts to approximate real work in interviews, the “life story” step to reveal curiosity and range, and early feedback loops to ensure fit quickly.
- •Interviews often mispredict performance; real work product is stronger evidence
- •Race-car analogy: the best test is putting someone in the ‘car’
- •‘Life story’ interview: get the why behind decisions, not just résumé facts
- •30/60/90-day reality checks: transparent feedback and fast course correction
- •Intern programs as scaled job trials: four months of real evidence beats post-intern interviews
- 1:09:49 – 1:15:35
Internships and co-op systems at scale: 1,000 interns as a talent engine (and intensity flywheel)
Farhan details Shopify’s plan to hire 1,000 interns and treats it as strategic talent development—not charity. He ties it to Waterloo-style co-op programs and explains why early-career cohorts benefit from in-office structure while still feeding the broader remote-first culture.
- •Scale plan: 1,000 interns in 2025 as a pipeline of job trials
- •Interns bring modern AI-native workflows and new commerce behaviors
- •Cohort design: interns in-office several days/week for mentorship and peer learning
- •Manager/mentor expectations include intentional IRL contact
- •Co-op model benefits: strong interview reps + real experience before graduation
- 1:15:35 – 1:20:39
Managing 120 direct reports: flattening orgs with systems, unscheduled 1:1s, and pairing culture
Farhan recounts running an extreme org design at Extreme Labs: up to 120 direct reports and no scheduled one-on-ones. He replaced manager-heavy processes with systems (pair programming, demos, backlogs, shared work hours) and used unscheduled conversations for real unblocking.
- •Experiment: 120 direct reports made scheduled 1:1s impossible by design
- •Replace managers with systems: pairing, demos, backlogs, clear working rhythms
- •Unscheduled 1:1s used for real-time unblocking (the highest-signal interactions)
- •Flat structures reduce hierarchy depth; alignment degrades as distance from leadership grows
- •Scaling reality check: what works at 120 likely breaks at 400—add structure without losing speed
- 1:20:39 – 1:30:11
Failure Corner: the costly hedge (POS rebuild) and Shopify’s risk-taking learning culture
Farhan shares a major early Shopify mistake: a hedged tech decision in rebuilding POS that cost roughly 18 months for a large team. The deeper lesson from Toby: don’t get punished for taking the right risks—get punished for failing to take them—and share the learning broadly.
- •Mistake: split approach (Swift iOS + React Native Android) created rework later
- •Outcome: realized React Native was the future and had to re-base/rewrite
- •Toby’s feedback: “tell everyone this story” to spread learning
- •Core lesson: hedging can be worse than a bold, well-supported bet
- •Reflection: if you’re going to “do all the things” to make a path succeed, commit fully
- 1:30:11 – 1:40:02
Lightning round and closing: books, favorite media, motto, and hiring for raw capability
The episode closes with rapid-fire recommendations (books, shows, products) and Farhan’s motto: “Everything you know is wrong.” He ends with a memorable hiring story—recruiting a standout waitress into tech—reinforcing his belief that talent is everywhere and performance reveals itself in real contexts.
- •Book recs: ‘Manna’ (AI-directed work), ‘Business Adventures’ (deep focus and case stories)
- •Favorite show: ‘Halt and Catch Fire’ as a realistic startup portrayal
- •Favorite product: Meta Ray-Bans as ‘right amount of tech’ and hands-free capture
- •Life motto: first-principles experimentation—assume your knowledge may be wrong
- •Hiring story: spotting intensity and organization in service work, then enabling a career shift
