Farhan Thawar has led engineering at Shopify and earlier worked at Xtreme Labs, Pivotal Labs and Helpful. His interviews and writing discuss hiring through real work, pair programming, engineering intensity and reducing unnecessary meetings. — Lenny’s Podcast.

Concept map of Farhan Thawar's engineering-leadership practices: work-sample hiring, pair programming, meeting design, and coaching.

Part 1: The Hiring Philosophy & Radical Assessment

  1. Interview Performance Is Not Job Performance: Thawar says conventional interviews can be a poor predictor of on-the-job performance: a polished interview and strong work do not always coincide. He still uses interviews, then checks fit through actual work. — Lenny’s Podcast.
  2. Observe Real Work: At Helpful, Thawar favored learning from a hire’s actual work and detailed team feedback during a trial period over relying on a long technical interview alone. — Technical Interviews Are Garbage.
  3. Hiring Fast Required Coaching: In a 2017 account of Helpful’s hiring approach, Thawar argued for hiring quickly and parting ways promptly when the role did not fit. He explicitly said the approach depended on using saved interview time for coaching and team feedback. — Technical Interviews Are Garbage.
  4. Beware the Technical-Interview Illusion: Thawar argued that technical interviews can select for people who interview well rather than people who will do the job well. This was his critique of the hiring signal, not a claim that every technical assessment is useless. — Technical Interviews Are Garbage.
  5. Do Not Let Interviews Narrow the Talent Pool: In his 2017 Helpful essay, Thawar described diversity of experience as a strength of the team and argued that conventional technical interviews could work against the hiring approach he wanted. — Technical Interviews Are Garbage.
  6. Treat the First 90 Days as Evidence: Thawar says Shopify still interviews candidates, then uses 30-, 60- and 90-day check-ins to see whether their actual work fits the role and to give transparent feedback. — Lenny’s Podcast.
  7. Use the Trial to De-Risk a Hire: At Helpful, Thawar used a 90-day trial with 30-, 60- and 90-day check-ins so the team could judge a new hire’s impact from shared work rather than a handful of interview impressions. — Technical Interviews Are Garbage.
  8. Define What Good Looks Like: Before hiring an engineering leader, Thawar recommends defining the company’s needs at a granular level; that exercise may show that a team lead, manager or director—not a VP—is the right role. — First Round Review.
  9. Look Beyond Conventional Credentials: Thawar recalls hiring a machine-learning candidate he met at a coffee shop despite that person having no previous software job; he says the candidate’s curiosity and subsequent work mattered more than the résumé signal. — Lenny’s Podcast.
  10. Use a Life-Story Interview: For Shopify leadership candidates, Thawar describes a life-story interview that examines past experiences and decisions for situational clues, alongside a separate technical deep dive into a problem the candidate has worked on. — Simple Leadership.

Part 2: Interview Myths & Finding True Talent

  1. Build Instead of Only Applying: Thawar advises job seekers to read a company’s API documentation and build a real project rather than rely solely on sending résumés; the project develops skills and creates work to show even if no offer follows. — Lenny’s Podcast.
  2. Evaluate Engineering Leaders in Context: When hiring an engineering leader, Thawar assesses process, people and technology capabilities against the company’s current needs rather than treating any one pillar as universally dominant. — First Round Review.
  3. Use Internships as Extended Interviews: Thawar regards a four-month Shopify internship as richer evidence of technical fit than a few hours of interviewing, and says Shopify converts a meaningful number of interns into full-time hires. — Zero Experience, Infinite Leverage.
  4. Value AI-Native Intern Habits: Thawar says new interns often reach for AI tools without older work habits to unlearn. He still treats senior-engineer pairing and real feedback as essential to their learning. — Zero Experience, Infinite Leverage.
  5. Notice Curiosity on Hard Problems: In the intern cohorts he has worked with, Thawar says fast-growing interns ask questions early, choose harder problems when given a choice and keep practicing; this is his observation, not a proven screening formula. — Zero Experience, Infinite Leverage.
  6. Keep Technical Assessment Close to Work: Shopify is experimenting with technical evaluations in which AI is prohibited, optional or required. Thawar says the open question is how well these exercises predict later job performance, making real internship work an important additional signal. — Zero Experience, Infinite Leverage.
  7. Show Self-Directed Work: For early-career engineers, Thawar recommends building a real project, publishing it on GitHub, fixing an open-source issue or building against a prospective employer’s API; the work demonstrates effort and gives the candidate something to learn from. — Zero Experience, Infinite Leverage.

Part 3: Pair Programming & The Underhanded Free Throw

  1. Pairing Can Look Awkward: Thawar compares pair programming to the underhanded free throw: a practice people may resist because it looks or feels strange even when they see value in using it. — Lenny’s Podcast.
  2. Measure More Than Lines of Code: Thawar jokes that two engineers pairing may write less code than either would alone; the point is to find a better design and deliver customer value, not maximize keystrokes. — Lenny’s Podcast.
  3. Treat Pairing Overhead as a Reported Estimate: In a TelcoDR interview, Thawar said research suggested roughly 15% overhead for pairing and described better knowledge sharing, code quality and fewer bugs as benefits. The interview did not identify the underlying studies, so this is his reported estimate rather than a verified general result. — TelcoDR Transcript.
  4. Full-Time Pairing Was Intense: Thawar recalls full-day pairing at Xtreme Labs and Pivotal as demanding but fast for learning. He distinguishes those earlier settings from Shopify, where engineers use pairing selectively. — Lenny’s Podcast.
  5. Xtreme Labs Made Pairing the Default: At Xtreme Labs, Thawar says his team hired about a thousand people over four years and gave one desktop to each two-person pair, making pairing the normal way to work there. — TelcoDR Transcript.
  6. Give the Pair Two Roles: In Thawar’s description, one engineer drives at the keyboard while a navigator questions choices, watches for problems and can take over; he compares the exchange to pilot and copilot work. — TelcoDR Transcript.
  7. Pairing Can Accelerate Onboarding: Thawar says pairing let less-experienced Xtreme Labs interns learn a stack quickly while giving senior engineers a partner who could contribute increasingly useful ideas. — TelcoDR Transcript.
  8. Pair to Investigate Uncertain Problems: At Shopify, Thawar says engineers may pair during an incident or when they are unsure how to proceed, using the shared session to investigate together. — Lenny’s Podcast.
  9. Share Knowledge Across Pairs: Thawar cites knowledge transfer and fewer silos as benefits of pairing, because engineers work through design decisions together rather than keeping all context with one person. — Lenny’s Podcast.

Part 4: Cultivating High-Intensity Engineering

  1. Seek Intensity, Not Longer Hours: For Thawar, engineering intensity means making better use of the hours already available, not simply extending the workday; he focuses on how much useful work a team can do within an hour. — Lenny’s Podcast.
  2. Protect Focused Work: Thawar values pairing in part because two engineers concentrating on one problem are less likely to drift into messages or unrelated tasks while they work through the design. — Lenny’s Podcast.
  3. Learn Beside Strong Peers: Thawar says choosing challenging work put him beside people he could learn from, and that working closely with skilled peers can expose how they reason through problems. — Lenny’s Podcast.
  4. Make Room for the Hard Work: At an Enrich event, Thawar urged teams to make repeated parts of a job easier through automation and useful defaults so they can spend more attention on the difficult work that remains. — Enrich Event Recap.
  5. Cut the Nice-to-Haves in Mobile Projects: At Xtreme Labs in 2013, Thawar said his team focused on customers’ must-have mobile-app features and set aside the nice-to-haves when scoping a build. — BizTech Magazine.
  6. Show What AI Helped You Build: Thawar says he wants engineers to share examples of useful work they completed quickly with AI tools, making tool-assisted approaches visible to colleagues. — Enrich Event Recap.
  7. Choose Hard Paths for Learning: Thawar’s career heuristic is to take worthwhile difficult paths because the skills and relationships gained can remain valuable even when the immediate attempt fails; difficulty alone is not the goal. — Lenny’s Podcast.
  8. Separate Pathfinding From Implementation: Thawar describes Shopify as a pathfinding company: teams may spend time discovering what to build, then pair more intensively when the problem and approach are clearer. — Lenny’s Podcast.

Part 5: Meeting Armageddon & Reclaiming Time

  1. Reset Recurring Internal Meetings: Thawar says Shopify annually deletes recurring internal meetings with more than two people while leaving one-on-ones and external meetings outside the purge, forcing teams to reconsider which recurring meetings they need. — Lenny’s Podcast.
  2. Subtraction Is Harder Than Addition: Thawar observes that a meeting is easy to add but socially difficult to decline or remove, which is why Shopify used a calendar reset to make re-adding valuable meetings a deliberate choice. — Global News Interview.
  3. Free Time for Engineering Work: Thawar says the meeting reset gave engineers more uninterrupted time for their craft. He tracked individual-contributor meeting hours to see whether calendars left enough working time. — Lenny’s Podcast.
  4. Pause New Recurring Meetings for Two Weeks: After Shopify’s calendar reset, Thawar says teams wait two weeks before adding a recurring meeting back. One-off meetings remain possible during that cooling-off period. — Lenny’s Podcast.
  5. Move Broadcast Updates Out of Chat: Thawar says Shopify moved large announcements and status updates from interruptive Slack messages into a feed-style Workplace channel, allowing people to consume those updates more deliberately; he noted Workplace was being deprecated. — Lenny’s Podcast.
  6. Clear Wednesday Calendars in the 2023 Reset: A direct 2023 interview report says Shopify cleared Wednesday meetings as part of its meeting-reduction intervention, giving employees a more protected workday at that time. — Global News Interview.
  7. Batch the Largest Meetings: In the same 2023 calendar intervention, Shopify reserved gatherings of at least 50 people for Thursdays rather than scattering those large meetings across the week. — Global News Interview.
  8. Repeat the Calendar Reset: Thawar says Shopify runs the recurring-meeting purge once a year at an unpredictable time, using the reset to counter the tendency for standing calendar commitments to persist by default. — Lenny’s Podcast.

Part 6: Leadership, Mentorship, and Looking Dumb

  1. Treat Looking Foolish as a Learning Tool: In a signed essay, Thawar calls his willingness to look foolish repeatedly a superpower. In a later interview, he describes asking questions until he understands rather than pretending to know. — Why Looking Stupid Is My Superpower.
  2. Ask Basic Questions in Public: Thawar argues that repeatedly trying ideas and asking seemingly basic questions in public can help a team learn; he says others often have the same question but hesitate to ask it. — Why Looking Stupid Is My Superpower.
  3. Learn Through Senior Pairing: Thawar says interns grow through real work with experienced engineers, including pairing and access to technical discussions. He does not present physical proximity as a prerequisite or promise a fixed junior-to-senior timeline. — Zero Experience, Infinite Leverage.
  4. Use Leadership Reviews to Unblock Work: Thawar describes regular leadership reviews and occasional pairing with engineers as ways to see where teams are stuck and help clear obstacles. — Lenny’s Podcast.
  5. Do Not Confuse Activity Metrics with Progress: Thawar cautions that counts of code, pull requests or commits can miss the work that matters, including removing code or helping another engineer; he favors looking at the actual contribution. — Zero Experience, Infinite Leverage.
  6. Simplify Routine Work to Protect Hard Work: At an Enrich event, Thawar urged engineers to make routine parts of their jobs easier so they can spend more attention on the difficult work that remains. — Enrich Farhan Thawar Event.
  7. Make Work Visible for Feedback: Thawar describes weekly public progress threads that let colleagues see what leaders are working on and contribute context or feedback; he does not claim visibility guarantees agreement. — Lenny’s Podcast.
  8. Mentor by Working Together: Thawar argues that new engineers learn from working beside experienced engineers on real problems, including pairing and visible technical discussions. That complements, rather than replaces, other mentorship formats. — Zero Experience, Infinite Leverage.

Part 7: Code Craftsmanship & Radical Simplification

  1. Treat Code as a Long-Lived Liability: Thawar argues that code remains with a team after it ships, so exploring a problem before committing to an implementation can lead to a shorter, better design. — Lenny’s Podcast.
  2. Create Space to Delete Code: Thawar says Shopify runs a Delete Code Club and deletion-focused hack days, giving engineers explicit time to remove code that is no longer needed. — Lenny’s Podcast.
  3. Use Pairing to Preserve Shared Context: Recalling an earlier practice at Pivotal Labs, Thawar says a pair might discard solo code written during a partner's absence and rebuild it together so both engineers understand the solution. He presents this as an extreme example, not a Shopify rule. — Lenny’s Podcast.
  4. Use AI as One Pairing Aid: Thawar describes AI coding assistants as another aid engineers can use while pairing and experimenting. His crafter's-paradise goal remains centered on enabling engineers to do skilled work. — Lenny’s Podcast.
  5. Optimize Design, Not Typing Speed: Thawar says an engineer's hands-on-keyboard speed is not usually the limiting factor in good software work; pairing can help a team frame a problem and choose a better design before typing more code. — Lenny’s Podcast.
  6. Let Pathfinding Improve the Final Design: Thawar describes trying an approach and then rewriting or removing parts of it as a way to discover a simpler final solution. The exploratory code need not become the permanent implementation. — Lenny’s Podcast.
  7. Reward Useful Deletion, Not Line Counts: Thawar argues that removing unneeded code can be more valuable than adding lines, so simple code-volume measures miss important engineering contributions. — Lenny’s Podcast.
  8. Spread Code Context Through Pairing: Thawar says pairing lets engineers share knowledge of a problem and codebase as they work, reducing reliance on a single person to hold all the context. — Lenny’s Podcast.

Part 8: The Trust Battery & Organizational Culture

  1. Use the Trust Battery as a Team Metaphor: Thawar applies Shopify's trust-battery language, associated with Tobi Lütke, to relationships in distributed teams: extended remote work can leave less interpersonal context, while intentional time together can replenish it. — Lenny’s Podcast.
  2. Calibrate Collaboration to Trust: Thawar describes the trust-battery metaphor as a useful shorthand for judging how much shared context colleagues have before difficult work together; he does not say it mechanically determines decision speed. — Lenny’s Podcast.
  3. Choose Higher-Fidelity Remote Conversations: For distributed work, Thawar recommends richer communication when a text exchange cannot carry enough context, including video or a real conversation and occasional non-work connection. — Simple Leadership.
  4. Rebuild Trust with Intentional Time Together: Thawar says team summits, short in-person bursts and optional office time can recharge trust in a remote-first organization. He does not dismiss such gatherings as ineffective team-building. — Lenny’s Podcast.
  5. Reward the Work Behind the Visible Feature: Thawar says Shopify adjusted performance management to recognize engineers who do essential behind-the-scenes glue work, not only work that appears as a merchant-facing feature. — Stripe Sessions: Building a Culture of System Reliability.
  6. Ship Often Enough to Test an Idea: At Helpful, Thawar describes a maximum one-week mobile-app ship cycle intended to put experiments before users quickly and reveal whether an idea deserved more investment. — Why Looking Stupid Is My Superpower.
  7. Aim for a Crafter's Paradise: Thawar calls Shopify's desired engineering environment a crafter's paradise: a place where builders can concentrate on skilled, meaningful product work. — Lenny’s Podcast.
  8. Let New Engineers See Work in the Open: Thawar says Shopify's public technical discussions allow interns and other engineers to observe how experienced colleagues reason through problems and use AI tools, creating learning opportunities beyond assigned tasks. — Zero Experience, Infinite Leverage.
  9. Protect Intensity by Removing Wasted Time: Thawar argues for making normal work hours more effective, including targeted pairing and fewer low-value meetings, so engineers have more time for the craft itself. He does not claim those practices guarantee freedom from burnout. — Lenny’s Podcast.