Shopify · OA → Phone screen → Onsite
In process2017–2026 Shopify SDE Intern OA / Interviews: 79 Experiences (Part 1 :)
A supplied repository and a ninety-percent test target made one bank task especially concrete.
Coverage: 20 reports from 2026: SWE and engineering internship assessments, pairing and Life Story; Canada, the US and unspecified locations where reported.
What came up
Life Story and coding assessments feature throughout this group. The named technical tasks include a bank, a booking system and a rover. Counts cover the 20 reports in this part.
| Topic | Reports |
|---|---|
| Life Story / behavioral conversation | 15 of 20 |
| Coding assessments | 11 of 20 |
| Object-oriented tasks or pairing invitations | 9 of 20 |
| AI tools allowed, encouraged or used | 5 of 20 |
| Dynamic programming | 3 of 20 |
| Logic, work-style or Criteria assessments | 3 of 20 |
| Small-system / function implementation | 3 of 20 |
| Tests and code verification | 3 of 20 |
| Executable technical coding | 2 of 20 |
| Git and repository workflow | 2 of 20 |
| Scaling and data-structure follow-ups | 1 of 20 |
One report can appear in several topic rows.
Questions we found
Algorithms / Data Structures
| Question | Frequency | All last seen dates |
|---|---|---|
| Backpack / knapsack problem | 1 report | 2026-05-08 |
Low-Level Design / Object-Oriented Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Design and implement a bank system / Bank class | 1 report | Reports: 2026-06-08; additional FastPrep history: 2025-09-09 |
| Implement a movie-theatre booking system | 1 report | 2026-06-03 |
Practical Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Build a CLI Mars rover with cardinal directions and forward movement | 1 report | Reports: 2026-05 (report: 2026-05-16); additional FastPrep history: 2026-06-13; 2024-09-26 |
Project Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Implement a bank-account utility with tests | 1 report | Reports: 2026-09-13 (report date); additional FastPrep history: 2025-05-05; 2025-04-28 |
Behavioral (BQ)
| Question | Frequency | All last seen dates |
|---|---|---|
| Why Shopify? | 1 report | 2026-02 |
System Design Follow-ups
| Question | Frequency | All last seen dates |
|---|---|---|
| How would the current design scale beyond one billion objects? | 1 report | 2026-01 |
Developer Tools / Code Discussion
| Question | Frequency | All last seen dates |
|---|---|---|
| Explain a pull request and demonstrate Git commands | 1 report | 2026-05 |
20 candidate timelines, loops and screens
01: An offer after OA, AI-assisted class design and behavioral
Report: October 19, 2026; interview date not given · Role: Software engineer intern
Assessment and technical
The account describes an online assessment followed by a technical exercise involving class design with AI assistance. It does not name the class or reproduce the assessment questions.
Behavioral and result
The conversation covered the candidate’s background and interests. They reported accepting an offer.
02: A bank class, a supplied repository and ninety-percent coverage
Report: September 13, 2026; interview day not given · Role: Engineering intern
The candidate was told to prepare a GitHub account. During pairing, they received a repository to clone, worked in their own IDE and shared their screen throughout.
The task was a bank-account implementation. They also had to write their own tests and reach at least 90% coverage. If the main requirements were finished with time left, the interviewer selected a bonus requirement to add to the existing code. The report does not disclose that follow-up or a final hiring decision.
03: A late start to a basic behavioral conversation
September 9, 2026 · Context: SWE internship context
In the Winter SWE discussion, this participant said their recruiter arrived ten minutes late. They described the questions as basic behavioral questions, without giving the wording.
They were waiting for a decision at their last update. The account does not disclose a coding task or a final result.
04: A September 9 Life Story, then a September 16 offer
September 9, 2026 · Role: Winter SWE intern · Location: Toronto, Canada
The Toronto Winter SWE applicant described Life Story as a casual conversation. They found it difficult to judge what the interviewer was looking for from the tone alone.
Their later update confirmed a Canada SWE offer on September 16.
05: Life Story became a close resume discussion
September 2026; report posted September 24 · Role: SWE intern
The Winter 2027 SWE applicant found the interviewer friendly and curious, but the conversation stayed close to their resume rather than becoming an autobiography.
They were initially told to expect a decision by the end of the same week. A later email moved that to the following week. By the September 26 update, they were still waiting; no final outcome was reported.
06: Twenty minutes lost from a thirty-minute Life Story
September 2026; report posted September 18 · Context: SWE internship context
The participant said the interviewer joined twenty minutes late to a thirty-minute Life Story. They were rejected and felt the remaining ten minutes had not given them room to explain their background.
After they emailed about the experience, the recruiter arranged another call. A later update said they received feedback and were encouraged to try a later summer cycle. They also said the recruiter attributed the late start to call-related technical problems. The reported lateness is specific to this account.
07: Design, prompt an LLM, then review with an engineer
August–September 2026 · Role: Software engineer intern · Location: Toronto, ON, Canada
OA — August, listed as 60 minutes
The candidate named CoderPad, Criteria and a workplace-behavior component. They did not give the coding prompts.
Phone / pairing — September, 45 minutes
They worked with a senior engineer on an object-oriented system. The sequence was to explain a solution and design, send a prompt to an LLM, then review the result with the engineer. The system’s domain was not disclosed.
Final — 30 minutes
The final felt like a relaxed recruiter conversation about goals and personal background. The candidate received an offer for Winter 2027.
08: A small system finished with time to talk
August–September 2026 · Role: Software engineer intern · Location: Toronto, ON, Canada
OA — August, listed as 120 minutes
Three coding questions were reported. The first was harder than the other two; none of the prompts was given.
Technical — 50 minutes
The task was to implement a small system. The candidate finished with roughly ten minutes left and used that time to talk with the interviewer. The system itself was not named.
Final — September, 30 minutes
Questions covered Shopify, the candidate’s projects and the document sent beforehand. An offer followed for the January–April 2027 internship.
09: A timed open-language problem, Ruby, C++ and Criteria
August 8, 2026 · Role: Software engineering intern, Winter 2027 · Location: United States
Coding assessment
The US software-engineering applicant described three separately timed questions: 35 minutes for the hardest task in a language of their choice, then 25 minutes each for Ruby and C++. They reported no camera, audio or screen recording, and said their code passed the visible test cases. They did not disclose the actual prompts.
Criteria and work style
There were forty math/logic items in twenty minutes, with a calculator allowed, followed by untimed rating questions about the applicant. The candidate’s suggested study topics were advice, not a list of questions they said they received.
By August 18, they still had no follow-up. Passing their test cases was their own result, not confirmation of advancement.
10: A bank system in a two-part final loop
May 5–June 15, 2026 · Role: Software engineering intern · Location: Montreal, QC, Canada
Timeline
Applied April 27; OA May 5; technical Final 1 on June 8; behavioral Final 2 on June 15; offer June 22.
OA — listed as 45 minutes
CoderPad contained three tasks: a two-dimensional dynamic-programming problem in any language, a C++ array task and a Ruby array task. Their operations and full statements were not supplied.
Final 1 — 45 minutes
The candidate implemented an object-oriented bank system. Follow-ups asked about OOP and different ways to implement classes.
Final 2 — 30 minutes
Life Story included the candidate guide and a discussion in which the candidate felt personality and enthusiasm mattered. The reported result was an offer for a Montreal engineering internship.
11: Movie booking: design first, then generate and refine
June 3, 2026 · Context: Software engineering internship discussion
The candidate was asked to implement a movie-theatre booking system in the pairing interview.
They spent about twenty minutes designing the solution, then used AI to write code and refined the output. They felt the design portion had gone reasonably well, but were unsure how the overall interview would be judged. The source does not give booking rules, an interface or a later outcome.
12: Pairing on June 2, Life Story invitation by June 5
June 2, 2026 · Context: SWE internship discussion
This participant said they completed pairing on June 2 at 1 p.m. By June 5, their update said they had received Life Story.
They did not name the technical task or describe the later behavioral conversation. This is a progression timeline rather than a question report.
13: An AI-assisted invitation and an unreliable scheduling status
Invitation: May 23, 2026; later updates in June–August · Role: SWE intern
The SWE intern invitation described an OOP pairing interview with AI assistance rather than a LeetCode exercise. The applicant initially wanted to understand how much AI use was expected.
In a June update, they said a cancelled pairing status had still been followed by Life Story. An August comment said they had reached Life Story in the previous cycle and been rejected. Those updates describe the same applicant’s progression; the scheduling label alone did not settle the outcome.
14: An open-language task, Ruby and C, then pairing
May–June 2026 · Role: Engineering intern · Location: Toronto, ON, Canada
OA — May, 60 minutes
One task allowed the candidate’s chosen language; the others were described as Ruby and C. This report says C, while several other accounts say C++. It does not provide any of the task statements.
Technical — May, 45 minutes
The candidate was paired with an engineer and given a system to implement, using a language they were comfortable with. The system was not named.
Final — June, 30 minutes
A relaxed recruiter conversation came next. The candidate reported receiving an offer.
15: A difficult DP assessment, then a short AI implementation
May–June 2026 · Role: Software engineering intern · Location: Toronto, ON, Canada
OA — May, 60 minutes
The candidate described an unproctored, difficult two-dimensional dynamic-programming task without giving its objective or inputs.
Phone — June, 60 minutes
They implemented a few basic functions for an unnamed system. They said they gave Claude a plan and generated the implementation in one attempt; AI use was a visible part of their account.
Final — June, 30 minutes
They did not receive an offer and described behavioral as the difficult stage for them. No specific final-round question was supplied.
16: A backpack problem followed by OOP and company readings
May–June 2026 · Role: Software engineering intern · Location: Toronto, ON, Canada
Timeline and OA
Applied April 27 and took the OA on May 8. It was listed as 75 minutes: a medium-to-hard backpack problem in a language of their choice, plus easy C++ and Ruby exercises. The candidate described those two as syntax, library-function and basic-math checks rather than algorithm-heavy tasks.
Technical — May, 45 minutes
A senior engineer worked through an OOP problem with the candidate. The candidate emphasized talking through the reasoning, asking for clarification and exchanging ideas; the actual system was not named.
Final — June, 25 minutes
The candidate read a collection of Shopify articles before the interview and was asked about them. The rest covered past experience and goals. They received an offer.
17: OOP, tests and an explicit Git check
May–June 2026 · Role: Software engineer intern · Location: Ottawa, ON, Canada
OA
The process field lists 45 minutes. The narrative separately describes a hard open-language task with 35 minutes and two easy tasks taking about ten minutes each. Those timing descriptions do not add up to the same total, so they should stay separate. The prompts were not included.
Peer programming — 45 minutes
The exercise tested OOP, requirements, edge cases and possible tests. The candidate described explaining the problem back before coding, running code early and keeping classes and tests in separate files.
Git was part of the discussion: clone, commit, push, pull, log, status and branch, plus an explanation of a pull request. The follow-up covered what to improve, including user storage, scaling, authentication and security; an unfinished solution could still be discussed.
Final — June, 45 minutes
The candidate’s notes for this stage focused on their background, a school/work/team challenge, product ownership and impact, interest in Shopify, and familiarity with the resume. They did not give a word-for-word question transcript. An offer followed for an Ottawa internship.
18: A working rover and tests, followed by rejection
May 2026; report posted May 16 · Context: SWE internship discussion
The technical-screen task was to build a command-line Mars rover controller. The reported rover faced north, south, east or west and could move forward.
The candidate wrote tests and got the behavior working, but was rejected. In a follow-up, they said the interview appeared to require both implementation ability and the ability to guide AI. They requested feedback; no detailed feedback was included.
19: The follow-up asked about more than a billion objects
January–February 2026 · Role: Software engineer intern · Location: Toronto, ON, Canada
Assessment
The process field lists a 100-minute January OA. The narrative breaks it into a 60-minute coding assessment, an IQ-style test and a work-style assessment. No coding prompt was reproduced.
Phone — January, 45 minutes
The follow-up moved into data structures and algorithms: how would the current design scale beyond one billion objects? The underlying system and its operations were not given.
Final — February, 30 minutes
Questions covered a project, the supplied document and why Shopify. The candidate received an offer.
20: CoderPad, Criteria, a class implementation and a guide quiz
January–February 2026 · Role: Engineering intern · Location: Toronto, ON, Canada
Applied in December 2025. January brought a 90-minute OA described as CoderPad plus Criteria; the individual questions were not supplied.
The February technical was a 45-minute OOP class implementation. A 45-minute final combined Life Story with questions on the candidate guide. An offer followed for the May–August 2026 internship.
In this series
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.