Just finished the Shopify loop for a senior backend role. Focusing on the system design round because that's where I see the most confusion online.
They don't call it L5 internally, but the senior IC band maps roughly to what you'd call L5 at other companies. The system design interview is 60 minutes, one interviewer. No panel.
What they actually asked me: Design a flash sale system that can handle 100k concurrent checkout attempts for a single product drop. Classic e-commerce pressure test. Makes total sense given what they build.
They care a LOT about: How you handle inventory contention at scale (optimistic locking vs. queuing vs. reservation windows) What happens when downstream services fail (Stripe, fulfillment, email) Data consistency tradeoffs, especially around overselling Observability. I mentioned structured logs and trace IDs early and the interviewer visibly relaxed.
They do NOT care about: Drawing a perfect architecture diagram Memorized CAP theorem definitions Whether you've used Kafka specifically (just reason about why you'd use a queue)
I came from FAANG where system design is basically a whiteboard performance. Shopify felt more like a conversation. The interviewer was genuinely curious whether I'd thought about the problem, not just pattern-matching my vocabulary.
One thing that surprised me: they pushed on the merchant side pretty explicitly. Like, how does a small merchant with 200 products experience this differently than a Gymshark-scale merchant? Made me think about multi-tenancy in a way I hadn't fully prepped.
Time management: I spent too long on the happy path and almost ran out of time for failure modes. Prioritize failure modes earlier than you think you need to.
If you're prepping for the Shopify senior system design interview in 2026, their engineering blog actually has good posts about their flash sale architecture. Read those. It's not cheating, it's showing you're interested in what they actually build.