
One candidate who interviewed for a Shopify Engineering Manager role describes a recruiter screen on management style, an unexplained pre-interview test, and a required pair-coding round. They did not get an offer.
$194K
Avg. Base Comp
$264K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Shopify's engineering manager postings describe the role as balancing people management with hands-on contribution to technical design and product development. One candidate described a process that started with a conversational recruiter screen covering the role, their management style, and how they think about growing a team. Have concrete examples ready of how you coach engineers and build a team.
The most distinctive detail is the required pair-coding round. The candidate was told it applies at all levels, including management. The task was a relatively simple piece of code, and they got through it without real problems, but the interview moved on to questions before they could finish. Practice talking through your approach while you code.
The candidate also mentions a strange test before the rest of the process and was never sure what it was meant to measure. Ask your recruiter early what each stage covers. They received no offer and no clear explanation of how the pair-coding round ended. This is a single report, so other candidates may see something different.
Synthesized from 1 candidate report by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Shopify process.
I started with a recruiter screen that felt pretty standard: they got to know me, walked me through the role, and spent time on my management style and how I think about growing a team. That part was conversational, and when I asked questions back, the responses were very positive and encouraging, which made the process feel warm at first. After that, I had a pair coding interview, which I was told was required for all levels. There was also a strange test before the rest of the process, and I still wasn’t really sure what it was meant to measure. The coding itself was not especially hard — I was asked to write a relatively simple piece of code and got through it without any real problems — but the interview ended before I could finish because they moved on to questions instead. That was a little frustrating, especially since I never got a clear explanation for the decision. Overall, the experience turned negative for me pretty quickly after the initial recruiter conversation. It felt like there was a lot of process, including the odd pre-test and the pair coding round, but not much clarity on what they were actually evaluating. I ended up not getting an offer, so my main takeaway is to be ready for a required pair-programming round even for EM roles, and don’t be surprised if the process includes something unusual before the main interviews.
Prep tip from this candidate
Be ready for a required pair-coding round even at the Engineering Manager level, and expect it to be more about working through a simple coding task live than solving a hard algorithm. Also prepare for a recruiter screen that leans into management style and team growth, plus a strange pre-interview test that may not be clearly explained.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Shopify
Given two sorted lists, write a function to merge them into one sorted list.
| Question | |
|---|---|
| Alphabet Sum | |
| Prime to N | |
| One Element Removed | |
| Priority Queue Using Linked List | |
| Unified Inbox | |
| LRU Cache 1 | |
| SageMaker Deployment Architecture | |
| Hurdles In Data Projects | |
| Minimum Directional Path | |
| Walking Robot | |
| Pop Tail | |
| Filling Supermarket Bag | |
| Move Zeros Back | |
| Merchant Dashboard Design | |
| Messenger Service Design | |
| Text Editor With OOP | |
| External Sorting | |
| Fixed-Length Arrays: Deletion | |
| Client Solution Pushback | |
| String Palindromes | |
| Why Do You Want to Work With Us | |
| Get Top N Frequent Words | |
| Find the First Non-Repeating Character in a String | |
| Find Bigrams | |
| N-gram Dictionary | |
| Find the Missing Number | |
| String Shift | |
| Google Maps Improvement | |
| Scrambled Tickets |
Synthesized from candidate reports. Individual experiences may vary.
The candidate describes a fairly standard recruiter conversation. It covered the role, their management style, and how they think about growing a team. When they asked questions back, the responses felt positive and encouraging. Prepare specific stories about coaching and team growth.
The candidate reports a strange test before the rest of the process and says they were never sure what it was meant to measure. They did not say exactly where it fell relative to the pair-coding round, and no format details were given, so ask the recruiter what to expect rather than assuming a particular type of assessment.
The candidate was told pair coding is required at all levels. The task was a relatively simple piece of code that they got through without real problems, but the interview moved on to questions before they could finish. Practice narrating your thinking in a live session, and be ready for the session to move on to questions.