Shopify · OA → Phone screen → Onsite
In process2017–2026 Shopify SDE Intern OA / Interviews: 79 Experiences (Part 2 :)
The assessment accounts name several distinct tasks, while pairing often required explaining the implementation.
Coverage: 20 reports from 2025–2026: SWE and engineering internship coding assessments, technical pairing and Life Story; Canadian and unspecified locations where reported.
What came up
These accounts cover coding assessments and object-oriented pairing. AI permissions and specific language requirements vary by report. Counts cover the 20 reports in this part.
| Topic | Reports |
|---|---|
| Coding assessments | 13 of 20 |
| Object-oriented tasks or pairing invitations | 10 of 20 |
| AI tools allowed, encouraged or used | 9 of 20 |
| Life Story / behavioral conversation | 7 of 20 |
| Logic, work-style or Criteria assessments | 7 of 20 |
| Pair programming / design discussion | 6 of 20 |
| Tests and code verification | 5 of 20 |
| Dynamic programming | 4 of 20 |
| Executable technical coding | 4 of 20 |
| Git and repository workflow | 2 of 20 |
| Small-system / function implementation | 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 | Reports: 2025-09; additional FastPrep history: 2026-05-08 |
| Filter words containing a given letter | 1 report | 2025-08-22 (report date) |
| Longest increasing subsequence in an array | 1 report | 2025-05-05 (report date) |
| Paint House-style dynamic programming | 1 report | 2025-08-22 (report date) |
Low-Level Design / Object-Oriented Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Design and implement a bank system / Bank class | 2 reports | Reports: 2025-09-09; 2025-08; additional FastPrep history: 2026-06-08 |
| Implement a car-rental system | 1 report | 2025-09 |
Practical Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Process background jobs with retries and exponential backoff | 1 report | 2026-01-30 (report date) |
Project Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Implement a bank-account utility with tests | 2 reports | Reports: 2025-05-05 (report date); 2025-04-28; additional FastPrep history: 2026-09-13 |
Behavioral (BQ)
| Question | Frequency | All last seen dates |
|---|---|---|
| Describe your past experience | 1 report | 2025-09 |
| How did you get into programming? | 1 report | 2025-09 |
| How do you keep up with industry trends? | 1 report | 2025-05-16 (report date) |
| Which projects are you proud of? | 1 report | 2025-09-13 |
| Why Shopify? | 1 report | 2025-09-13 |
| Why are you interested in ecommerce technology? | 1 report | 2025-05-16 (report date) |
Developer Tools / Code Discussion
| Question | Frequency | All last seen dates |
|---|---|---|
| Explain the code produced by Cursor | 1 report | 2025-08-30 |
20 candidate timelines, loops and screens
21: A later attempt passed technical but stopped at behavioral
Winter 2026 recruiting period · Context: SWE internship recruiting context
After returning to Waterloo in late January 2026, the applicant interviewed with Shopify again. This time they passed technical and were rejected after behavioral.
They wondered whether their presentation had sounded too narrowly technical. That was their own explanation; the post gives neither a scoring rubric nor a question transcript. It is a separate application cycle from their April 2025 rejection.
22: A forty-five-minute invitation explicitly encouraged AI
Invitation posted January 16, 2026 · Role: SWE intern
The Summer 2026 internship invitation described a real-world object-oriented challenge that the candidate would lead with an interviewer. It explicitly encouraged using AI and allocated 45 minutes.
This account ends at the invitation. It establishes the described format, not a completed interview or a particular question.
23: Retries and exponential backoff with little interviewer feedback
January 2026; report posted January 30 · Role: SWE intern in the account body
The coding task involved background jobs, retries and exponential backoff, with asynchronous behavior and failure cases at its center.
The candidate implemented the core logic and discussed scaling, persistence and monitoring. They ran out of time before finishing all the tests. They found the interviewer’s limited interruptions and feedback stressful because they could not tell whether the design was too complicated or too shallow. A rejection followed.
The post’s title says new grad, while its firsthand body calls this an SWE intern interview; the account is included under that explicit body description.
24: Full coding score, then an interview invitation
January 2026; update posted January 19 · Context: SWE internship discussion
The participant reported a 100% coding-assessment score and finishing all forty Criteria questions with about thirty seconds left.
They had received a pairing invitation by the time of the update. They did not disclose the coding tasks or a later interview result.
25: Ninety-percent test coverage under time pressure
January 2026 · Role: Software engineer intern · Location: Toronto, ON, Canada
OA — 60 minutes
Three coding tasks were reported: the first medium/hard and the next two easy. A forty-item logic test and work-style questionnaire followed. The actual programming prompts were not given.
Technical — 50 minutes
The candidate implemented several functions for a system and estimated that their tests reached 90% coverage. They found the main pressure came from the clock rather than the implementation’s difficulty. The record says no offer, without naming the system or establishing why the decision went that way.
26: A short OOP pairing round and an October offer
August–October 2025 · Role: Software engineering intern · Location: Toronto, ON, Canada
An August OA was listed as 45 minutes and described as one or two medium coding questions. The prompts were not supplied.
September pairing lasted 30 minutes and involved a basic OOP task. October’s 30-minute Life Story included behavioral questions and the preparation package sent to the candidate. They received an offer.
27: A Bank class with Cursor encouraged
August 20–September 17, 2025 · Role: Engineering intern · Location: Toronto, ON, Canada
Applied August 19 and took the OA the next day. The 45-minute assessment included an easy algorithm problem, a simple C++ task and a simple Ruby task; none was transcribed.
The September 9 phone round lasted 45 minutes. The task was to design and implement a Bank class, and Cursor or other AI tools were encouraged.
A 30-minute final on September 17 drew on documents sent beforehand. An offer arrived September 19.
28: A phone implementation, then a Hack the North conversation
August 19–September 13, 2025 · Role: Engineering intern · Location: Toronto, ON, Canada
OA — August 19, 60 minutes
One medium language-agnostic DSA problem was followed by very easy Ruby and C++ tasks. The account says AI was encouraged, with an expectation that the candidate would do more than paste an answer.
Phone — August 27, 45 minutes
About thirty minutes went to an OOD implementation and fifteen to conversation. The candidate gave only a generic CRUD example, not the actual system’s behavior. AI use was encouraged, and they stressed understanding what it produced.
Final — September 13, 30 minutes
The conversation happened in person at Hack the North and included why Shopify, past experience and projects they were proud of. They received an offer September 15.
29: An OA pass and a first AI-friendly pairing invitation
Report: September 4, 2025 · Role: SWE intern
The SWE intern applicant had passed the OA and scheduled pairing with a Shopify engineer. They described it as their first pair-programming interview and their first technical interview that encouraged AI use.
They did not give the OA questions or a completed pairing result.
30: References were checked, but an offer did not follow
August–September 2025 · Role: Software engineer intern · Location: Toronto, ON, Canada
An August OA was listed as 120 minutes and included three algorithm tasks, an IQ-style test and a behavioral assessment. The individual questions were not disclosed.
The September technical was a 45-minute OOP pairing round with AI strongly encouraged. A 30-minute final discussed previous work, Shopify values, preferred role and office location.
The candidate felt the interviewer reacted positively, and their references were checked. They were still rejected. That last detail matters: a reference request was not an offer in this account.
31: Knapsack, mandatory Ruby and a car-rental system
September 2025 · Role: Software engineer intern · Location: Toronto, ON, Canada
The 60-minute OA included a dynamic-programming knapsack problem and a question that had to be completed in Ruby. The source gives no full statement for either task.
The 45-minute final asked the candidate to implement a car-rental system from requirements supplied in the interview. They could use their own IDE, and AI was allowed. The requirements were not reproduced. The candidate did not receive an offer.
32: A bank implementation with account-kind follow-ups
August–September 2025 · Role: Engineering intern · Location: Toronto, ON, Canada
OA — August, listed as 60 minutes
The candidate described two easy CoderPad array questions, forty math/trivia items in twenty minutes, and repeated work-style statements rated from one to five.
Interview — August, 60 minutes
They designed and coded a bank system locally while sharing their screen, then pushed it to a specified repository. Unit tests were part of the task. Follow-ups added different account kinds.
Final — September, 45 minutes
Life Story covered how they started programming, hobbies, experience and projects. They were also asked about supplied Shopify-principles material and CEO emails. An offer followed.
33: Explain the plan in comments, then explain Cursor’s code
August 30, 2025 · Role: SWE intern, Winter 2026 cycle
The candidate described a simple, language-agnostic OOP problem with Cursor and other AI tools allowed.
They first talked through a high-level solution in comments, explaining the choices, and then used Cursor to build the functionality. The interviewer asked them to explain the generated code. They believed they completed the task but finished close to the time limit; no final outcome was given.
34: Forty minutes for DP, then ten minutes each for C++ and Ruby
Report: August 28, 2025; assessment day not given · Role: SDE intern applicant, 2026 cycle
The coding OA had three separately timed tasks: forty minutes for a dynamic-programming question in any language, ten minutes for a C++ array-traversal exercise, and ten minutes for a Ruby string-traversal exercise. The candidate found the last two simple checks of language familiarity. Their descriptions do not give the actual operations or expected results.
A separate cognitive assessment had forty questions in twenty-five minutes. The candidate felt short of time. No later interview or decision was reported.
35: Paint House, C++ strings and a Ruby word filter
Report: August 22, 2025; assessment day not given · Role: SWE intern applicant, 2026 cycle
The applicant received an automatic OA the day after applying. Criteria included an untimed self-assessment and forty logic questions in twenty minutes; they found the logic section tight on time.
CoderPad then contained three tasks. The first allowed forty-five minutes for a DP problem described as similar to Paint House. The report does not provide its precise cost model or variant rules. The second allowed ten minutes for simple string manipulation in C++, without disclosing the operation.
The third allowed ten minutes and required Ruby: given a list of words and a letter, return the words containing that letter. The candidate described this as a basic Ruby-familiarity check and asked about the next round; no advancement or final decision was confirmed.
36: Quadratic LIS passed, then the bank design started with one Account
April–May 2025; report posted May 5 · Role: Fall 2025 SDE intern applicant
OA
Although graduating in 2025, the candidate applied for the Fall internship after receiving an April 7 opening email. An OA email followed two days later. They recalled a roughly thirty-minute Criteria cognitive assessment, possibly called UCAT, and found its timing tight.
The forty-five-minute CoderPad task was a longest-increasing-subsequence variant. Their classic O(n²) solution passed; they did not use the faster binary-search approach. The exact variant was not reproduced.
Pair programming
An invitation arrived about a week later. It called the round System Design, but the task was to implement a banking system and tests. The candidate initially planned several classes. The interviewer redirected them to start with a basic Account, then they wrote tests covering corner cases.
AI tools were permitted, but this candidate did not use them. They chose Java and recommended IntelliJ's generated constructors and accessors for saving time. After the core work, they answered expansion questions verbally; the interviewer said these bonus questions varied. Their wording was not shared. A Life Story invitation arrived about two hours after the interview. The account ends before that conversation.
37: A six-day wait to behavioral
Report: May 16, 2025 · Context: Engineering internship discussion
Another participant in the Fall 2025 discussion reported about six days between their pairing interview and a behavioral invitation.
They supplied no question transcript or final outcome. Their timing is a separate account, not another stage in either neighboring candidate’s timeline.
38: About a week between pairing and the next invitation
Report: May 16, 2025 · Context: Engineering internship discussion
A separate participant said it took roughly a week after pair programming to receive the behavioral invitation.
The short reply did not disclose the technical task, the behavioral questions or an offer decision.
39: Ten business days to behavioral, then ecommerce questions
Report: May 16, 2025 · Role: Engineering intern
After technical pair programming for the Fall 2025 engineering internship, this participant reported waiting about ten business days for a behavioral invitation.
The behavioral conversation asked why they were interested in ecommerce technology and how they kept up with industry trends. They did not name the technical problem or report a final decision.
40: AI built the bank and CLI, but the decision was a rejection
Technical: April 28, 2025; report posted April 30 · Role: Fall SDE intern applicant
Applied April 7; received the assessment April 8 and the technical invitation April 23. Rejection arrived April 30, two days after technical.
The forty-five-minute pairing task was a banking utility with account creation, deposits, withdrawals and transfers. The language was open, AI tools were allowed, and the application had to run. The candidate used ChatGPT to generate the implementation and tests. When the interviewer asked for a CLI, they generated that too and checked edge cases.
The interviewer asked twice what could come next. The candidate proposed linting, style improvements, documentation and clearer code. The interviewer agreed and said those changes did not need to be implemented during the call. The candidate created a branch and opened a pull request.
They recalled a brief JavaScript setup delay and wondered what had gone wrong. They did not receive a reason for rejection. Their account explicitly says no algorithm, data-structure or system-design questions were asked.
In this series
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.