← Back to Directory

Shopify interview notes, page 4 of 12

Large Enterprises

Most of these Shopify write-ups come from Machine Learning Engineers (36), then Data Scientists (32) and Software Engineers (27). The most reported rounds are the technical phone screen (49), the system design round (17), the product sense round (14) and the recruiter screen (9).

115 interview notes · updated Oct 2026

Shopify·Machine Learning Engineer·Onsite - System Design / Architecture

May 2026
Shopify ML engineer interview focused on a full system design question around search autocomplete, covering everything from candidate generation to ranking models to serving infrastructure. Pretty deep dive, felt like they wanted to see if you could connect the ML pieces to the engineering reality.
  • Design a search autocomplete system from an ML perspective, covering candidate generation, ranking, and serving at scale.

“This question is deceptively wide.”

View Post

Shopify·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Shopify for a software engineering role. The question was a beast, basically a full library management platform with more moving parts than I expected. Came out feeling okay but not great.
  • Design a system to manage borrowing and returning rare books across multiple library branches, covering catalog search, reservations, waitlists, appointment-based access, identity verification, condition inspection with photos, audit trails, fines, RFID/barcode check-in/out, and inventory reconciliation.
  • Define the core APIs for this library system, including creating users, placing and canceling holds, checking items in and out, reporting damage or loss, and scheduling appointments.
  • How would you handle consistency and concurrency to prevent two users from simultaneously booking the last available copy of a rare book?
  • What architecture would you propose for this system in terms of services, databases, caches, queues, and search indexes? How do you handle authorization, encryption, and tamper-evident audit logs?
  • How would you extend this design to support inter-library loans and offline operations at branches with unreliable connectivity?

“This one sprawled fast.”

View Post

Shopify·Data Scientist·Onsite - Multi Round

May 2026
Shopify DS interview with two meaty sections: a product case around launching an App Store (metrics framework, instrumentation, experiment design) and a data investigation case where you have to explain a traffic spike with a degraded funnel. Pretty demanding for a single session, and the breadth of it caught me off guard.
  • You're supporting the launch of Shopify's App Store. How would you define and measure success across merchants, developers, and Shopify itself, including a north-star metric, leading indicators, and guardrails?
  • What event streams and data model would you design to support App Store metrics? Walk through key tables and how you'd handle identity resolution across merchants, developers, and sessions.
  • Design an experiment to improve an App Store outcome, such as a ranking algorithm change or a recommendation module. Cover randomization unit, duration, validity threats, and how you'd make a ship decision.
  • Given three years of daily App Store data, you notice a large unexplained traffic spike where ATC rate drops sharply and conversion rate drops slightly. What hypotheses would you form, and how would you investigate?
  • What charts would you build to validate or refute your hypotheses about the traffic spike, and what follow-up data would you request if the existing dataset isn't enough?

“This is the kind of question where you can talk forever and still feel like you missed something.”

View Post

Shopify·Machine Learning Engineer·Technical Phone Screen

May 2026
75-minute technical screen for an MLE role at Shopify, centered entirely on a mobile robot grid problem with three follow-up extensions. Rejection email came the next day, which stings a little when you thought you were keeping up.
  • Given a 2D grid, navigate a mobile robot from a start position to a target position. Then extend the solution to handle obstacles on the grid.
  • Now extend the robot navigation problem to handle multiple robots moving simultaneously on the same grid.
  • Extend the same robot navigation problem from a 2D grid to a 3D grid with x, y, and z axes.

“The base problem was familiar enough that I felt okay going in.”

View Post

Shopify·Data Scientist·Technical Phone Screen

May 2026
Shopify Data Scientist interview that was basically a pattern recognition gauntlet. Four sequence/grid puzzles back to back, which felt more like a math olympiad warm-up than a data science screen. Not what I was expecting.
  • Find the next number in the sequence 2, 3, 5, 9, 17, 33, and explain your reasoning.
  • Identify the next two values in the sequence 1, 4, 2, 8, 4, 16, 8, 32, ?, ?
  • What comes next in the sequence 1, 3, 7, 15, 31, and why?
  • In a 3x3 grid where the rows are [7, 4, 11], [5, 9, 14], and [?, 13, 18], find the missing value and describe the rule governing each row.

“Each term doubles the previous one and subtracts 1, so 33 times 2 minus 1 gives 65.”

View Post

Shopify·Machine Learning Engineer·Onsite - System Design / Architecture

May 2026
Shopify ML engineer onsite, this particular round was all about system design with an ML flavor. The question centered on personalized product feeds, so less about model training and more about how you'd actually build the thing end to end.
  • Design a personalized product feed system for an e-commerce platform.

“This is where I probably underinvested in the infrastructure side.”

View Post

Shopify·Data Scientist·Technical Phone Screen

May 2026
Shopify data scientist interview with a single very deep experimentation question. The whole thing was basically one giant case study on A/B testing at scale, and it covered more ground than I expected in one sitting.
  • You're evaluating a core product change that likely has network effects in a large platform with millions of daily active users. Walk through your full experiment design: success metrics, randomization unit, test plan with ramp strategy and stopping rules, variance reduction techniques, sample size calculation for a specific scenario, how you'd detect heterogeneous treatment effects, what you'd do if randomization isn't feasible, and how you'd define ship vs rollback criteria and communicate results to stakeholders.

“This was one question but it kept expanding.”

View Post

Shopify·Product Manager·Onsite - Product Sense / Strategy

May 2026
Shopify product interview, one question about improving the merchant onboarding flow. Pretty open-ended, not a lot of scaffolding given.
  • How would you improve the sign-up experience for new merchants?

“I went straight to activation metrics and time-to-first-sale as the north star, which felt right but I probably skipped over the problem framing too fast.”

View Post

Shopify·Product Manager·Onsite - Product Sense / Strategy

May 2026
Shopify PM interview, one question about measuring product success. Short session, not much else to report.
  • How would you determine whether a product is successful?

“Went straight to metrics and kind of rambled.”

View Post

Shopify·Machine Learning Engineer·Technical Phone Screen

May 2026
Shopify ML engineer screen, pretty standard coding problem but the follow-ups about obstacles and path tracking added some pressure toward the end. Nothing too wild but I left feeling like I could've been cleaner on the edge cases.
  • Given an m x n grid and a robot starting at position (r, c), process a string of movement commands ('U', 'D', 'L', 'R') and return the robot's final position. Any move that would take the robot out of bounds should be ignored.

“Seemed easy at first and I think I got a bit overconfident.”

View Post