Shopify · OA → Phone screen → Onsite
In process2017–2026 Shopify SDE Intern OA / Interviews: 79 Experiences (Part 4 :)
Older accounts describe project demonstrations, open-book pairing and offer timelines.
Coverage: 19 reports from 2017–2022: backend, frontend, mobile, infrastructure and production-engineering internship applicants, plus a backend/data-engineering applicant; Canada and remote or sponsorship tracks where reported.
What came up
Life Story and personal projects account for much of the detail here. The frontend reports also include challenge submissions and a small-component pairing round. Counts cover the 19 reports in this part.
| Topic | Reports |
|---|---|
| Life Story / behavioral conversation | 13 of 19 |
| Project work or code review | 8 of 19 |
| Pair programming / design discussion | 4 of 19 |
| Developer practices | 1 of 19 |
| Executable technical coding | 1 of 19 |
| Frontend component implementation | 1 of 19 |
| Graph validation | 1 of 19 |
| OS / networking / CS fundamentals | 1 of 19 |
| Spacetagram frontend challenge | 1 of 19 |
| Tests and code verification | 1 of 19 |
One report can appear in several topic rows.
Questions we found
Algorithms / Data Structures
| Question | Frequency | All last seen dates |
|---|---|---|
| Write a graph-data-structure validator | 1 report | 2018-03-15 (report date) |
Project Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Warehouse inventory application | 1 report | 2022-01-27 (report date) |
Frontend / UI Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Build a small frontend component; tables and filters were examples | 1 report | Reports: November–December 2021; additional FastPrep history: 2022-03-15 |
| Spacetagram frontend coding challenge | 1 report | 2022-02-02 (report date) |
Behavioral (BQ)
| Question | Frequency | All last seen dates |
|---|---|---|
| How did you get into programming? | 1 report | Early 2018 |
| How do you feel about remote work? | 1 report | October–November 2021 |
| How was your application experience? | 1 report | 2018-03-15 (report date) |
| Suggest an idea for Hack Days | 1 report | 2018-03-15 (report date) |
| What was your most interesting individual project? | 1 report | October–November 2021 |
| What work would you like to do during the internship? | 1 report | 2018-03-15 (report date) |
| Why do you want this role? | 1 report | October–November 2021 |
Developer Practices
| Question | Frequency | All last seen dates |
|---|---|---|
| What do you know about test-driven design? | 1 report | October–November 2021 |
Project / Code Review
| Question | Frequency | All last seen dates |
|---|---|---|
| Present your own project and explain its code and design choices | 7 reports | November–December 2021; 2021-10-07; March–May 2020; Early 2020; Early 2018; Before January 2018; 2017 |
Application / Product Task
| Question | Frequency | All last seen dates |
|---|---|---|
| Create a fictional Shopify store | 1 report | 2018-03-15 (report date) |
19 candidate timelines, loops and screens
61: Another frontend applicant’s Spacetagram
Report: February 2, 2022 · Context: Frontend internship discussion
A separate participant shared their own deployed Spacetagram while comparing frontend application progress. They described it as covering the essentials, while acknowledging it was not their ideal final version.
They had seen the application reviewed and were still waiting at their last update. The record does not confirm a final decision or give the original task specification.
62: A thirty-minute Life Story before infrastructure technical
February 2022 · Role: Infrastructure intern
The infrastructure applicant’s Life Story lasted about thirty minutes. At the beginning, the interviewer explicitly said the interview’s length did not indicate success or failure.
The candidate subsequently had technical scheduled. They described the conversation as covering fit with Shopify’s values and how past experience matched the role, without reporting a technical prompt or final outcome.
63: Reviewers created stock in a deployed inventory app
Report: January 27, 2022 · Context: 2022 software internship discussion
The applicant noticed reviewers using their deployed warehouse inventory application: they created a new warehouse and added stock items. One item had a negative quantity, exposing a weakness in the submitted implementation.
The candidate had applied January 10. After several waiting updates, they reported receiving an interview invitation January 31. The original brief, stack and remaining acceptance criteria were not supplied.
64: A frontend demo, open-book pairing and an approved offer deferral
September–December 2021; report posted March 15, 2022 · Role: Frontend intern · Location: Canada
Application and Life Story
The candidate applied through a referral in September for Winter 2022 and submitted a coding challenge with the application. They described a small frontend or backend project shared through GitHub, but did not give its objective. They recalled the application window lasting less than a month.
HR contacted them in October. The hour-long Life Story asked why they wanted the role, about their most interesting individual project, what they knew about test-driven design, and how they felt about remote work. Follow-ups grew out of their answers. They found it conversational and passed in November.
Technical — 90 minutes
For the first twenty-five minutes, they used a local demo and slides to explain a module from a previous internship. Five minutes of follow-up questions came next.
The remaining hour was pair programming on a small frontend component. The candidate gave tables and filters as examples, without identifying the exact component or its rules; FastPrep's filterable-table practice version develops that reported idea. Documentation and Google were allowed. The interviewer emphasized clarifying requirements and communicating while solving a problem together, as in day-to-day work.
Offer and deferral
They passed technical in December. HR asked whether Summer 2022 would work instead, and an offer followed after they agreed. In March 2022 they asked to defer again to Fall; HR followed up promptly and approved the change within a week.
65: A frontend offer moved from winter to summer
November 8, 2021 · Role: Frontend intern
The frontend candidate completed technical November 8 and initially heard no decision.
They later received an email to arrange a call and confirmed that the call carried an offer. The Winter 2022 cohort was already full, so their placement moved to Summer 2022, which suited them better. The technical task was not described.
66: References Monday, offer Tuesday
October 22, 2021 · Role: Backend developer intern
The backend applicant completed technical October 22, received a reference request October 25 and an offer October 26.
They had earlier received the same mid-November decision estimate discussed in the thread, but their actual decision came sooner. They did not disclose the technical question.
67: Expected system design, received a LeetCode-like task
October 13–21, 2021 · Role: Backend intern
Applied September 21; Life Story invitation October 6; Life Story October 13; technical invitation October 19; technical October 21.
The recruiter had described a system-design question and was unsure about LeetCode. After the interview, the candidate said the task was much closer to LeetCode than expected and required executable code. They never supplied its actual statement.
References were requested November 12, a call was scheduled November 15 and an offer was extended November 23.
68: An October technical and a November offer
October 13–20, 2021 · Role: Backend developer intern
Applied September 21; application viewed September 22; Life Story invitation October 7; Life Story October 13; technical invitation October 15; technical October 20.
The original post asked what a systems-style interview would involve. Those expectations did not reveal the task actually received.
A reference request and call scheduling followed October 29, then an offer November 1. The final update confirmed the offer without adding a problem statement.
69: A verbal offer followed by paperwork the next day
October 8–18, 2021 · Role: Backend intern
Applied September 21 and saw the application viewed September 22. Life Story was invited September 30 and completed October 8; technical was invited October 15 and completed October 18.
On October 26, the candidate was asked for references and a call. The verbal offer came October 27; formal paperwork followed October 28. Their references responded quickly, and they did not know how much that timing affected the decision. The team and lead were identified with the offer. No technical task was disclosed.
70: Project review, design, then refactoring discussion
October 1–7, 2021 · Role: Backend / data-engineering intern applicant
The applicant applied to backend and data engineering September 21, completed Life Story October 1 and had the final October 7. An offer arrived October 8.
The final used about twenty-five minutes for a personal project, fifty for a system-design-like problem, five for improvements and refactoring, and another five to ten for questions. The candidate felt their deep knowledge of the project helped the discussion; the interviewers seemed engaged.
The design problem’s identity was not given. Its improvement discussion stayed attached to that same solution rather than becoming a separate task.
71: A fixed technical date after Life Story
May 28–June 2, 2021 · Role: Backend developer intern
Life Story was May 28, its follow-up invitation May 31 and technical June 2. The candidate corrected an earlier date in their own update and said the technical slot was fixed rather than freely movable.
They later had a recruiter call scheduled for June 8 to discuss exciting news. They thought technical had gone well. Their update stops at the planned call, without confirming an offer.
72: A previous Life Story rejection, reported the next year
Summer 2020; report posted June 9, 2021 · Role: Software internship applicant · Location: Canada
The third-year Canadian student said they had reached Life Story the previous summer and were rejected. Their recruiter’s explanation was that other applicants had more experience.
At the time of writing, they had mainly backend experience and were considering a frontend internship. Their questions about a future frontend technical interview were preparation questions, not another interview they had already completed.
73: An overlong project presentation, then time recovered in CoderPad
March–May 2020; Fall 2020 internship · Role: Backend developer intern · Location: Remote
Screen and Life Story
The backend applicant described a roughly two-month process: a fifteen-minute phone screen, a fifty-to-sixty-minute Life Story and a ninety-minute project/pairing interview. The first call covered interests and team preferences; Life Story followed the personal choices and programming journey behind the application.
Project review and coding
They brought a complex project they had spent nearly four hundred hours building and used an architecture diagram to explain it. The presentation ran long, leaving one question incompletely answered.
The following CoderPad exercise was about an hour and allowed their chosen language. They finished early enough to return to the earlier question and explain it more clearly. The coding prompt was not disclosed. They received the internship offer.
74: PHPSandbox source review and a project in Google Docs
Early 2020, after a December 2019 application · Role: Backend developer intern
The applicant applied through the Africa-focused sponsorship track after seeing it in December 2019. A roughly forty-five-minute Life Story covered family and pre-tech experiences as well as their developer journey.
For technical, two senior developers inspected PHPSandbox, the candidate’s own project. They asked about implementation choices and scaling. The second task was a real-project design discussion supplied in Google Docs, not a disclosed algorithm problem. The candidate explained approaches in a language-agnostic way, with PHP examples where useful.
The technical conversation took place over an audio call. They felt more nervous in the second half, but the engineers’ questions and feedback helped the discussion. Their references were contacted the day they submitted them, and a later recruiter call brought an eight-month internship offer. The source never names the Google Docs project.
75: Waiting after a Waterloo final
November 20, 2019 · Role: Backend engineering intern · Location: Waterloo, Canada
The backend applicant had completed the final interview the preceding Wednesday and was waiting for a decision. Their expected start was early January, making housing arrangements part of the time pressure.
They did not give the technical questions or report an offer or rejection.
76: A mobile Life Story followed by a missed response date
June 2019; report posted June 12 · Role: Mobile developer intern
The mobile-development applicant had completed Life Story the previous week. They expected a reply June 7 but had heard nothing by their post.
They sent a follow-up email and were still waiting at their last update.
77: A store, a graph validator and an Alexa Fridge project review
Early 2018, for Summer 2018 · Role: Backend developer intern · Location: Montreal, Canada
Application tasks
The backend applicant created a fictional Shopify store, choosing Japanese sweets and pastries. They also wrote a graph-data-structure validator in Python and used docstrings to keep the solution understandable. The original validation property and API were not disclosed.
Written application questions covered the work they wanted to do, their application experience and an idea for Hack Days.
Life Story and onsite
Life Story lasted about forty-five minutes and discussed interests, travel, earlier experiences and the path into programming. The onsite included a review of Alexa Fridge, their own project, with code and design choices, followed by a design-decision problem whose system was not named.
They received an offer about a week later for the Montreal backend internship.
78: The technical interview stayed on a personal project
Before the January 2018 internship; report posted January 17, 2019 · Role: Software engineering intern, Data Infrastructure · Location: Ottawa, Canada
The Data Infrastructure intern said their entire technical interview was spent discussing their own project: a demonstration, implementation details and reasons behind design choices.
79: Ceroku, Git servers and a difficult hypothetical
2017 hiring, for Winter 2018 · Role: Production engineering intern · Location: Ottawa, Canada
After Life Story, the production-engineering candidate presented Ceroku, their Heroku clone. Their custom Git server wrapped git-upload-pack and git-receive-pack for authentication. A pre-receive hook triggered a slug builder, which packaged application files and runtime binaries into a compressed archive. A slug runner started that archive in Docker containers, and Traefik routed each subdomain to its container.
The second part was a hypothetical problem with the engineers, involving operating-systems and networking concepts. They found it especially hard because they had not formally studied those subjects. The problem’s actual objective was not supplied.
A recruiter called a few weeks later with an offer for the Pods team in Ottawa.
Patterns across the reports
-
AI still came with an explanation step. Reports 11 and 33 describe planning an OOP solution, generating code, then refining or explaining it. Report 28 also emphasized understanding the output.
-
The interview order changed across periods. The 2025 bank account in report 36 reached Life Story after technical. The 2021–2022 accounts in reports 64 and 59 put Life Story before project review and pairing.
-
References did not guarantee an offer. Report 30 ended in rejection after references were checked. In reports 66, 68 and 69, references preceded offers.
-
The next invitation could take hours or days. Report 36 received Life Story about two hours after pairing; report 53 also moved ahead within hours. Reports 37, 38 and 39 instead describe roughly six days, a week and ten business days.
In this series
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.