← Back to Directory

Shopify interview notes, page 11 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

Jul 2026
Shopify ML engineer interview with a meaty open-ended system design question around building a package delivery ETA model. Single question but it sprawled into six or seven distinct sub-problems, which made it feel more like a 45-minute design session than a traditional interview.
  • Design an end-to-end ML system to predict package delivery ETA, covering target definition, model choice, feature engineering, handling missing scan events, offline and online evaluation, prediction intervals, and production monitoring.

“This one is deceptively wide.”

View Post

Shopify·Machine Learning Engineer·Technical Phone Screen

Jul 2026
Shopify ML engineer interview that turned out to be a pure coding exercise, which I wasn't really expecting. The main problem was a robot simulator on a 2D grid, and they pushed pretty hard on follow-ups about obstacles and multi-robot coordination.
  • Design and implement a 2D robot simulator. The robot lives on a finite grid and accepts commands: PLACE (with coordinates and a facing direction), MOVE, LEFT, RIGHT, and REPORT. Build a clean Robot class with a CLI loop, and write unit tests. Any command that would push the robot off the grid should be silently ignored.
  • Extend the simulator to support obstacles placed on the grid. The robot must not be able to move into a cell that contains an obstacle.
  • Further extend the simulator to support two or more robots operating on the same grid, taking turns issuing commands, with the constraint that robots cannot collide with each other.

“I started with the state representation and got a bit too deep into enum choices for direction before writing any actual logic.”

View Post

Shopify·Machine Learning Engineer·Technical Phone Screen

Jul 2026
Shopify ML engineer interview where the main event was a deep end-to-end walkthrough of a project from your resume. They don't just want the highlight reel, they want to poke at every decision you made along the way.
  • Walk me through an ML project on your resume from start to finish, covering the business problem, data, modeling decisions, evaluation, deployment, and how you monitored it afterward.

“This sounds like one question but it's really like eight questions stacked in a trench coat.”

View Post

Shopify·Software Engineer·Take-home Assignment

Jul 2026
Shopify software engineer round where they handed me a local URL shortener to build from scratch, library-style, with persistence and tests. More depth than I expected for what sounds like a toy problem.
  • Build a local URL shortener library with shorten and resolve operations, URL validation, hash-based code generation, collision handling, in-memory storage, JSON file persistence, and deduplication for repeated inputs.
  • How does memory usage scale as the number of stored URLs grows, and what architectural changes would you make if the data no longer fits on a single machine?

“The collision handling part is where I spent way too long.”

View Post

Shopify·Data Scientist·Technical Phone Screen

Jul 2026
Shopify data scientist interview, got a coding question that looked simple at first glance but had enough edge cases to trip you up if you weren't paying attention. Pretty standard technical screen vibe.
  • Write a Python function that computes the Jaccard similarity between two lists of strings, handling duplicates, empty inputs, and doing it in linear time without any external libraries.

“The empty list edge cases are what got me thinking for a second.”

View Post

Shopify·Machine Learning Engineer·Onsite - Behavioral / Leadership

Jul 2026
Shopify ML engineer interview that was basically a long career retrospective plus a deep project dive. The whole thing felt like they wanted to see if you'd actually shipped production ML or just run notebooks.
  • Walk through your career from university to now, covering why you made each major transition, what challenge you ran into, and what impact you had.
  • Pick one project that best represents your work and go deep: what problem were you solving, why did it matter to the business, what did you own specifically, what technical decisions and trade-offs did you make, how did you measure success, and what was hardest and what would you do differently?

“This took longer than I expected.”

View Post

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

Jul 2026
Shopify ML engineer system design round, one big open-ended question about building a personalized product feed from scratch. The scope was massive and I kept second-guessing how deep to go on each piece.
  • Design an end-to-end ML system for personalized product feeds in an e-commerce app. The feed should be ranked by relevance, availability, diversity, and freshness. Cover data collection, candidate generation, feature pipelines, model training, online serving, re-ranking, experimentation, monitoring, reliability, and cold-start handling.

“This question ate the whole session.”

View Post

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

Jul 2026
Shopify ML engineer interview, one meaty system design question about building a product ranking model end to end. Pretty open-ended, which I liked but also found stressful because there's no obvious stopping point.
  • You're building a product ranking model for an e-commerce marketplace. Given a user, some context, and a set of candidate products, how would you rank them so the most relevant items show up first? Walk through data collection, label definition, features, model choices, training, and offline/online evaluation.

“This is a lot of ground to cover and I think I spread myself too thin.”

View Post

Shopify·Machine Learning Engineer·Take-home Assignment

Jul 2026
Shopify ML Engineer take-home that was really more of a software engineering test than anything ML-related. You get 60 minutes to build a CLI key-value store with OOP, file persistence, unit tests, a README, and a GitHub Actions workflow, then explain your design decisions afterward.
  • Design and implement a single-class CLI application supporting add, get, delete, list, help, and exit commands, with file-based state persistence, input validation, and error logging.
  • Write comprehensive unit tests covering happy paths, edge cases like duplicate or missing keys, and malformed command handling.
  • Set up a GitHub Actions workflow that automatically runs the test suite on every push.
  • Explain your class design: how you structured state, methods, and dependency boundaries within the single-class constraint.
  • How would you refactor this design to support subcommands or a modular command structure as the application grows?
  • What trade-offs did you make given the 60-minute time constraint, and what would you do differently with more time?

“The 60-minute clock made me cut corners I later regretted.”

View Post

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

Jul 2026
Shopify ML Engineer interview with a meaty system design question around building a loan recommendation system from scratch. A lot of ground to cover and the breadth of it was a bit overwhelming in the moment.
  • Design a baseline loan recommendation system for users. Walk through your objectives and constraints, feature design, modeling approach, evaluation strategy, and rollout plan.

“This one sprawls in every direction if you let it.”

View Post