Shopify · OA → Phone screen → Onsite
In process2017–2026 Shopify SDE Intern OA / Interviews: 79 Experiences (Part 3 :)
Directional search, robot commands and specific Life Story questions appear alongside progression timelines.
Coverage: 20 reports from 2022–2025: software and engineering internship applicants, including Engineering & Data and frontend roles; Canada, a Seattle posting and unspecified locations.
What came up
The reports include executable coding, behavioral interviews and assessments. Named tasks include directional grid search, a word game and two different robot exercises. Counts cover the 20 reports in this part.
| Topic | Reports |
|---|---|
| Life Story / behavioral conversation | 12 of 20 |
| Coding assessments | 11 of 20 |
| Executable technical coding | 4 of 20 |
| Object-oriented tasks or pairing invitations | 4 of 20 |
| Pair programming / design discussion | 4 of 20 |
| Logic, work-style or Criteria assessments | 3 of 20 |
| Project work or code review | 3 of 20 |
| AI tools allowed, encouraged or used | 2 of 20 |
| Tests and code verification | 2 of 20 |
| Directional grid search | 1 of 20 |
| OS / networking / CS fundamentals | 1 of 20 |
| Robot command simulation | 1 of 20 |
| Spacetagram frontend challenge | 1 of 20 |
One report can appear in several topic rows.
Questions we found
Algorithms / Data Structures
| Question | Frequency | All last seen dates |
|---|---|---|
| Find a compromised server from eight-direction clues | 1 report | 2025-04-09 (report date) |
| Fix only the first robot instruction | 1 report | 2024-12-25 (report date) |
| Longest increasing subsequence in an array | 1 report | Reports: —; 1 undated report; additional FastPrep history: 2025-05-05 |
| Min-stack with O(1) minimum retrieval | 1 report | —; 1 undated report |
Low-Level Design / Object-Oriented Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Build a word-guessing game through OOP steps | 1 report | 2025-01 |
Practical Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Build a CLI Mars rover with cardinal directions and forward movement | 1 report | Reports: 2024-09-26; additional FastPrep history: 2026-06-13; 2026-05-16 |
Frontend / UI Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Spacetagram frontend coding challenge | 1 report | 2022-02-03 (report date) |
Behavioral (BQ)
| Question | Frequency | All last seen dates |
|---|---|---|
| What did you think or feel after reading Tobi’s letter? | 2 reports | 2025-01; 1 undated report |
| Why Shopify? | 2 reports | 2025-01; 2024-10-02 |
| Why software engineering? | 2 reports | 2025-01; 1 undated report |
| Describe your past experience | 1 report | 2025-02-01 (report date) |
| Tell the story that brought you to this conversation | 1 report | 2022-06-03 |
| What are you most proud of? | 1 report | 2024-10-02 |
| What comments or concerns do you have about the Shopify stories? | 1 report | 2024-10-02 |
| What was your biggest challenge? | 1 report | 2024-10-02 |
| What were your childhood hobbies? | 1 report | 2022-02-02 |
| What would you do if you disliked a merchant’s product? | 1 report | 2024-10-02 |
| Which Shopify values match your interests? | 1 report | 2024-10-02 |
| Why are you passionate about what you do? | 1 report | 2025-02-01 (report date) |
| Why did you choose your previous internship companies? | 1 report | 2024-10-02 |
Project / Code Review
| Question | Frequency | All last seen dates |
|---|---|---|
| Present your own project and explain its code and design choices | 2 reports | 2022-02; 1 undated report |
20 candidate timelines, loops and screens
41: A fixed CoderPad interface made boundary tracking difficult
Report: April 11, 2025; assessment day not given · Role: Fall engineering intern applicant · Posting: Seattle
An OA followed the application. The candidate described a twenty-five-minute cognitive test with simple math and spot-the-difference questions, then forty minutes of coding on CoderPad.
They thought the coding exercise might have a bug. In the discussion, they explained that its function parameters and return type were fixed and global variables were disallowed, leaving them unsure how to retain and update boundaries. The full objective was not supplied, so this account does not identify a specific reusable problem. The source marks the assessment unsuccessful without explaining its scoring.
42: Directional clues to a hidden compromised server
Report: April 9, 2025; assessment day not given · Role: Engineering & Data internship applicant
The assessment instructions listed about thirty minutes for Criteria, combining cognitive and work-style questions, and forty-five minutes for CoderPad. The candidate described one coding task with a forty-minute timer and an immediate score afterward.
Their screenshots show finding a compromised server on a grid. A fixed server is hidden in a grid whose top-left coordinate is (0, 0). Each clue points toward it in one of eight directions: up, up-right, right, down-right, down, down-left, left or up-left. The program must return the next probe as [x, y] and locate the server within the allowed number of tries.
The supplied interface was solve(direction, x, y, width, height), with each grid dimension between 1 and 10,000. The starting coordinates could be anywhere, and the first clue did not have to point down-right. The candidate also shared code with passing-test indicators, but did not report a later interview or hiring decision.
43: A technically correct solution, but difficult audio
Late April 2025 · Context: SWE internship recruiting context
The applicant believed they solved their first Shopify coding interview correctly but was rejected.
They recalled trouble hearing the interviewer because of the microphone. They also wondered whether they had used too little AI. The post does not establish either as the reason for rejection and does not name the task.
44: References after a nontechnical Life Story
January–February 2025; update posted February 1 · Context: SWE internship discussion
This candidate had finished technical and Life Story and received a reference request.
They said Life Story contained no technical questions. The examples they gave asked why they were passionate about what they did and asked them to describe past experiences. They had not confirmed an offer.
45: A supportive pairing interview, followed by an uncomfortable Life Story
January 2025; report posted February 1 · Role: Engineering & Data intern applicant
The candidate completed the OA in early January, then passed a pair-programming round with a senior frontend engineer. They described that engineer as supportive and said the conversation went well. They did not identify the coding task.
The next round was a thirty-minute Life Story. They found the recruiter conversation uncomfortable and believed they had answered the culture questions well, but did not reproduce those questions. The interview was on Thursday and rejection arrived Saturday. The report does not establish why they were rejected.
46: From January application to a February offer
January 22–29, 2025 · Role: SWE intern
Timeline
Applied January 9; technical invitation January 16; technical January 22; Life Story invitation January 24; Life Story January 29. References were requested January 29 and submitted January 31. The offer arrived February 3.
The candidate described technical as OOP/coding in a pairing format, rather than a large system-design exercise. They emphasized discussing the approach with the interviewer. The actual problem was not given.
47: Rejection just after applications closed
Report: January 13, 2025 · Role: SWE intern applicant, first year
The first-year applicant thought they had done very well on the coding challenge, but received a rejection immediately after the application deadline.
They wondered whether being a first-year student had hurt their chances. That explanation was their own guess. The challenge and score breakdown were not provided.
48: A word-guessing game broken into OOP steps
December 2024–January 2025 · Role: Software engineer intern · Location: Toronto, ON, Canada
OA — December, 30 minutes
One medium coding problem was reported, without its statement.
Technical pairing — January, 45 minutes
The exercise built a word-guessing game through several OOP steps. AI tools were allowed, and the account emphasized discussing the reasoning and understanding any generated code. It gives no word-length rule, feedback format or attempt limit.
Life Story — January, 30 minutes
Questions covered past internships, projects, school, extracurriculars, why Shopify and why software engineering. The candidate also gave an opinion on a letter from Tobi about work culture. An offer followed in February.
49: An eighty-minute HackerRank with LIS and a min-stack
Interview date unavailable; Summer 2025 internship record · Role: Software developer intern · Location: Toronto, Canada
The fourth-year software-development applicant described an 80-minute HackerRank with two programming tasks and multiple-choice questions.
The named programming tasks were finding the longest increasing subsequence in an array and implementing a min-stack with constant-time minimum retrieval. No input bounds or longer statements were supplied.
The MCQs covered data structures, algorithms, operating systems and networking. The OS items included process scheduling and memory management. The record says the candidate declined an offer.
50: Pairing felt collaborative, with AI allowed
Interview dates unavailable; May–August 2025 internship · Role: Engineering intern · Location: Toronto, ON, Canada
The sequence was OA, technical pairing, then Life Story. The candidate described their own OA problem as fairly easy but did not disclose it.
They enjoyed working with the interviewer in technical and said AI was allowed. Their round did not directly test DSA; understanding the chosen programming language was more prominent in their account.
Life Story felt conversational. The candidate highlighted the material sent beforehand and described growth and motivation as themes in their own advice afterward. They reported receiving an offer. The internship term does not provide an exact interview date.
51: A Christmas OA that changes only the robot's first instruction
Reports: December 22 and 25, 2024; Summer 2025 application · Role: SDE intern applicant
Criteria
In the first update, the applicant described forty IQ-style questions in twenty minutes, followed by roughly a hundred repeated work-style questions without a time limit. Their later post covers the coding portion of the same application.
CoderPad — 28 minutes
The task was to fix only the first robot instruction. The robot starts at (0, 0), facing right; right increases x and up increases y. FORWARD moves one step in the facing direction. BACK moves one step backward without turning. TURN LEFT and TURN RIGHT rotate a quarter-turn without moving.
Changing the first command must make the final position equal the target; passing through it earlier does not count. A valid correction is guaranteed. The required result is the exact text Replace instruction 1 with [command], rather than the resulting coordinates.
The example uses FORWARD, TURN RIGHT, FORWARD, TURN RIGHT and four more FORWARD commands. Its original endpoint is (-3, -1), while the target is (-1, 4). Replacing the first command with TURN RIGHT reaches that target. The candidate stressed matching the output format. They did not report a final outcome.
52: A working robot controller, then questions about Shopify values
September 5–October 2, 2024; report posted October 3 · Role: Engineering intern applicant
Application and pairing
Applied September 5 and completed an OA and take-home project that day, with their tests passing. The take-home's objective was not shared. A technical invitation arrived September 17; pairing took place September 26.
Although the invitation said System Design, the task was to write a robot-coordinate controller. Its disclosed operations moved the robot forward and changed its direction through Left and Right commands; other operations were left unspecified. The candidate used their own IDE and a main function to read commands and test the behavior. They said they finished and tested it in about thirty minutes, with no system-design questions.
Life Story — October 2
The invitation arrived September 27. The conversation asked whether they had read the Shopify stories in the candidate portal, what comments or concerns they had, and which company values matched their interests. Other questions were what they would do if they disliked a merchant's product, why Shopify, why they had chosen previous internship companies, what they were most proud of, and their biggest challenge.
They had glanced at the portal material but struggled to recall it during the interview. They felt most of the remaining conversation went well. The posting had said Remote US, yet the recruiter required the internship to be onsite in Toronto or Montreal and declined their request for remote work or only an initial month onsite. Rejection arrived October 3. The candidate suspected that discussion mattered; the report does not establish the reason.
53: A quick technical-to-Life-Story transition
September 2024 · Context: SWE internship discussion
The candidate completed technical on Monday, September 16. A Life Story invitation arrived a few hours later, and they took that interview two or three days afterward.
Their September 20 update reported an offer. They did not identify the coding task or behavioral questions.
54: Positive coding feedback did not lead to Life Story
Report: September 18, 2024 · Role: Engineering intern
The engineering-intern applicant reported full scores on the take-home assessment, then thirty minutes with an engineer to code a small program.
They said the program worked and the engineer gave positive verbal feedback. A rejection still arrived before Life Story. The program’s task was not described, and the account does not establish why the candidate was rejected.
55: Life Story included the application portal and Tobi’s letter
Interview dates unavailable; Fall 2024 internship · Role: Software engineer intern · Location: Toronto, ON, Canada
The stated sequence was OA, Life Story, then a final. The OA and final tasks were not described.
Life Story returned to a question from the application portal: how did the candidate feel after reading Tobi’s letter? Other prompts asked why software engineering and how their background and experiences led them there. The record says no offer.
56: Forty minutes of project review inside a ninety-minute technical
Interview dates unavailable; Fall 2024 internship · Role: Software engineering intern · Location: Toronto, ON, Canada
The recruiter screen lasted about sixty minutes and discussed the candidate’s projects, portal information and culture fit.
The ninety-minute technical split into roughly forty minutes on a personal project and fifty minutes on an OOP problem. The candidate described demonstrating the project, coding and testing in a familiar language, and keeping coding practices in mind under time pressure.
They received an offer. Their account explicitly identifies this as the Fall 2024 process, before later changes to interview order; the specific OOP prompt was not given.
57: A frontend Life Story before a late-June technical
June 3–30, 2022 · Role: Frontend intern
Applied May 9; Life Story invitation May 24; Life Story June 3; confirmation of passing it June 6; technical June 30.
The recruiter asked for the story that had brought the candidate to that conversation, allowing either professional or personal material. The candidate remembered discussing values and direction and found the exchange enjoyable. The technical task and final result were not supplied.
58: Small hints during frontend programming
February 28–March 9, 2022 · Role: Frontend intern
Applied January 18 and saw the application move into review the next day. The later updates record Life Story on February 28, a technical invitation afterward and technical on March 9.
The candidate thought the technical had gone well and said the interviewers offered small hints during programming. No task identity or final decision was given.
59: A childhood-hobbies opening, then open-book pairing
February 2–11, 2022 · Role: Backend developer intern
Application and Life Story
Applied January 6 and received the Life Story invitation January 28. In the February 2 conversation, the recruiter opened by asking about childhood hobbies. It became a two-way discussion, with time left for the candidate’s own questions.
The recruiter invited them to technical during Life Story. The recruiter suggested a medium-sized project the candidate had written themselves. The plan was thirty minutes reviewing that project with two engineers, then sixty minutes pairing with one engineer on a system-design problem. It was described as open book: browsing and questions were permitted.
Technical and decision
The scheduling email came February 8, and the candidate had completed technical by February 11. References were requested February 16; they accepted the formal offer February 17. The actual pairing problem was never named.
60: A deployed Spacetagram submission, then rejection
Report: February 3, 2022 · Role: Frontend intern
The frontend applicant shared their own deployed Spacetagram coding-challenge submission while waiting for an update.
A later edit reported rejection. They did not reproduce the assignment’s full requirements, and the outcome does not establish which part of the submission was judged weak.
In this series
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.