Shopify interview preparation: what they hire for and how to get ready

Did you find a loop structure on a forum and start rehearsing tidy stories about metrics you moved? That prep might be fine, but it can also miss the thing Shopify's own leaders spend the most time talking about, which is a bar and a working style that a lot of candidates would not enjoy.

This article covers what Shopify leaders say they hire for, how to prepare for a pairing-style process, and why writing matters there more than at most companies. It also covers where Shopify's stated approach contradicts standard career advice, and the questions to ask so you can decide whether you'd thrive. Read the honesty section first, because it tells you what this playbook does not cover.

Everything here traces to a named Shopify leader speaking on the record: Farhan Thawar, VP and head of engineering, who runs the internship program and redesigned Shopify's compensation system; Tobi Lütke, Shopify's founder and CEO; Archie Abrams, VP of product and head of growth; and Brandon Chu, who was VP of product there for seven years. Every quote below plays the exact moment it was said, or carries the timestamp if only audio exists.

What this playbook can and can't tell you

We don't have reliable current information about Shopify's interview loop mechanics, so we're not going to invent any. Round counts, question formats, take-home policies, and whether a given team pairs with you live all change from year to year and from org to org. If you read a blog post claiming to know Shopify's exact 2026 loop, treat it as one person's experience on one team.

What we do have is a lot of on-the-record material from Shopify leaders about the bar they're aiming at and the culture you'd be joining. That's what this playbook is about. Ask your recruiter for the loop structure, because they'll tell you, and use the rest of this to prepare for what the loop is measuring. For the round shapes that are common across companies, the engineering interview guide covers the formats you're most likely to get.

What Shopify leaders say they hire for

Farhan Thawar runs the hiring process at Shopify and doesn't think interviews work very well.

That belief changes what the interview is for. If you assume interviews are weak predictors, you stop trying to make them a perfect filter and you start trying to make them look like the job. Thawar uses a race car analogy for this, and he's explicit that the real evaluation continues after you start.

He's blunt about what that means for you. He says a fast, chaotic environment isn't for everyone, and that if it isn't a fit, both sides benefit from finding out quickly. He also says Shopify wants to be the best 10,000-person company rather than a much bigger one. Take that at face value when you're deciding how hard to push.

One named interview step does come up. Thawar describes a stage called the life story, and what it's built to find.

So if you get a stage that walks through your whole history, don't recite your resume in order. Have a reason ready for every move you made. Why you left, why you picked the next thing, what you were curious about, what you went and learned on your own. Thawar is explicitly reading for curiosity and range, and he mentions that David Epstein's book Range changed his mind about specialists. A career that looks scattered is not automatically a problem here, as long as you can explain the logic behind each jump.

Tobi Lütke frames the bar in a different way, and it's worth holding next to Thawar's version because it tells you what a "good hire" is supposed to produce.

That's a useful lens for every answer you give. When you tell a story about past work, spend most of it on the small judgment calls you made and why, rather than on the outcome. The outcome only proves you were there, and the reasoning is what they say they're actually buying.

Thawar also says he's a big fan of job trials, and that Shopify runs them at scale through the internship program, which he said would take on a thousand interns in 2025. If you're early in your career, that's a real door, and it's a door where four months of work product replaces eight hours of interviews.

What they mean when they say intensity

Shopify leaders use the word intensity constantly, and it doesn't mean what people usually assume. Thawar's version is about density of work inside normal hours.

He goes further in the same conversation. He says that if you don't have two or three big projects on fire, you're probably not pushing hard enough, and that you want a little chaos at the edge. He also says comfort feels like stability but discomfort actually gives you stability, because you're constantly learning.

Two things follow for your prep. First, if an interviewer asks how you work, an answer built around long hours won't get the reaction you expect. Talk about how you compress a task and what you cut to protect the hours that matter. Second, if you're asked about a project that went badly, don't sand off the chaos. Someone who says they've only ever worked on things that went smoothly is telling this particular company that they've never taken a real risk.

How to prepare for a pairing-style interview

Thawar calls pair programming the most underutilized management tool in engineering, and he's put money behind that belief, paying for two people to sit at one computer. Shopify isn't a full-time pairing shop, and he says so plainly: it's more like a four to eight hour a week pairing culture, plus pairing during incidents and on unfamiliar parts of the codebase. But the mental model behind pairing tells you exactly what a live problem-solving round is measuring.

He also tells the story of Tobi Lütke and CTO Cody Fauser pairing with a one-hour timer, deleting all the code and keeping the tests if they didn't finish, on the theory that a solution that takes longer than an hour means the design is wrong. That's a strong signal about how they think, and about how comfortable they are throwing work away.

If your round involves working through a problem live with someone, here's how to prepare for it:

If rambling under pressure is your failure mode, the playbook on rambling and the one on organizing your thoughts before you speak both drill the same muscle a pairing round tests.

Why writing matters more here than at most companies

Brandon Chu spent seven years at Shopify, ending as a VP of product, and his blog posts on product management are widely read. He says writing did more for his career than anything else, and his reason is about thinking rather than publishing.

He puts the obligation on anyone doing the job, whether or not anything gets published: "You owe your team, your peers, your stakeholders that level of clarity. So even if you're writing and throw it away, you've created the clarity in your mind and you can articulate it as such" (31:29, audio). He also describes the practical effect at Shopify, where the company was hiring so fast that people who joined his team already knew how he thought because they'd read his posts.

For your prep, that means two things. Anything you send them in writing is part of the evaluation, so treat the application questions and the follow-up email as work samples rather than formalities. And if you've written anything public about your craft, put it where they'll find it, because Chu describes writing as the thing that built his trust with Tobi Lütke and pulled other people into the company.

Where Shopify contradicts the standard advice

This is the part worth sitting with, because Shopify's leaders say things that cut against advice we and most other people give. Naming the tension is more useful than pretending it isn't there.

Metrics and goals

Most interview prep tells you to quantify everything and to lead with the metric you moved. Archie Abrams, who runs growth, says the core of the company doesn't work that way.

He's honest about the cost too, saying conversations get extremely subjective about what the right thing to do is, and that a small group including Tobi Lütke holds the taste bar. So keep your numbers, because a Shopify growth interviewer will still want them. But have a second version of every story that runs on conviction: what you believed and why, and what you'd have done if the dashboard had told you nothing useful. If your entire professional identity is "I hit the number," this is a place where that answer does less work than usual.

One-on-ones

Our one-on-one playbook tells you to protect the recurring meeting with your manager and to run it deliberately, and we stand by that at most companies. Thawar ran the opposite experiment, at a company before Shopify.

Two honest caveats. This was his previous company, in roughly 2009 to 2013, and he says his biggest investor pushed back by asking whether it would work at 400 people, at which point he added structure and made a few directors with 40 reports each. He also says Shopify has guardrails and he doesn't carry 120 reports there. So this isn't a description of Shopify's current management model.

The part that transfers is the underlying claim: he looked back at 151 weekly one-on-ones over three years at Microsoft and concluded the useful conversations were the unscheduled ones, when he knocked on his manager's door with an actual problem. If you're interviewing at Shopify, or anywhere that talks like this, prepare for a manager relationship where the burden of raising things sits with you. Ask in the interview how your prospective manager runs it. And if the honest answer is that you do your best work with a protected weekly slot, that's real information about fit, and you shouldn't hide it.

Meetings and process

Shopify deletes every recurring internal meeting with more than two people once a year at a random time, then bans new recurring meetings for two weeks. Thawar describes it in the same conversation and says the point is to break the inertia behind meetings that exist only because they've always existed. If you're used to influence flowing through a standing meeting series, expect to build it differently there.

Questions that tell you whether you'd actually thrive there

Thawar's own advice for job seekers is to write down a framework of what you care about, before a recruiter's pitch has a chance to confuse you. He says title, company, and money all distract, that he sent his framework to a recruiter once to explain why a role didn't fit, and that when he notices his framework is being violated he resigns, sometimes without another job lined up (15:53 and 17:07 in the same episode). You don't have to be that extreme to use the idea. Write your version down before your first call, then ask questions that test it.

Listen for whether the answers sound proud or resigned. A team that talks about the chaos with energy is a very different place to work from one that talks about putting up with it. And notice your own reaction, because Thawar's whole point is that the environment is genuinely not for everyone, and that finding out fast is good for both sides.

What to do before you apply

The most actionable thing Thawar says has nothing to do with interviewing. It's about what job seekers do with their time.

This is the head of engineering telling you what would impress him. Ship something on Shopify's platform, even something small, and now you have a real answer when someone asks why this company. You'll also have opinions about the developer experience, which is a much better conversation than reciting the company's mission statement back at them.

For the rest of your application materials, the positioning playbook covers how to frame your background for a specific company, and the behavioral interview playbook covers the story-based rounds you'll get regardless of what else the loop contains.

Frequently asked questions

Does Shopify still do pair programming interviews?

We don't know, and we're not going to guess. Thawar describes Shopify as roughly a four to eight hour a week pairing culture rather than a full-time pairing shop, and he describes pairing on incidents and unfamiliar code. Whether that shows up in your loop depends on the team and the year. Ask your recruiter what each round involves, and prepare for live collaborative problem-solving either way, because it's the format most likely to catch you off guard.

What is the life story interview?

Thawar names it as a step where they walk through your experiences looking for evidence that you're a curious person with range. His framing is that a resume tells you what someone did but not why, and the why is the interesting part. Prepare a reason for every transition in your history.

Is Shopify a hard place to work?

Their leaders say yes, in public, on purpose. Thawar says you should have two or three big projects on fire, and calls the environment chaotic and fast-moving. Abrams describes a place where teams throw away months of work when the world changes. Nobody is hiding this. Decide whether it appeals to you before you spend weeks preparing.

Should I quantify my achievements if KPIs are banned there?

Yes, keep the numbers. Abrams says growth teams do use metrics, they just take a different form, and no interviewer penalizes a clear result. Add a layer on top: what you believed and why, and what call you'd have made without the data. That's the reasoning Lütke describes hiring for.

How do I get a Shopify internship?

Thawar treats the internship program as Shopify's real job trial at scale, and said the 2025 program would take roughly a thousand interns. He explicitly contrasts four months of work product against eight hours of interviews. If you're early in your career, that path is worth more of your attention than a perfectly tuned resume.

What if I've never worked somewhere this intense?

Say so, and be specific about what you have done. Thawar's own advice is to take the harder path, and he points out that even when the hard thing doesn't work out you've learned something and worked with sharp people. An honest answer about a stretch you took, including what went badly, fits their stated values better than a polished record with no risk in it.

Your Shopify prep checklist