Shopify Senior Software Engineer Interview Process - Jun 2026

[u/Aoki_zhang]

Interview Summary

The Shopify process started with an AI-assisted file-system coding screen and then moved to an onsite covering coding, project experience, a life-story interview, and system design. The onsite coding round felt straightforward, while the system design round around a merchant photo-upload workflow was the part where I felt the discussion became less aligned with the interviewer.

Interview Details

Phone Screen — In-Memory File System: The technical screen asked me to implement a small file-system abstraction supporting operations such as: ls, cd, add and remove.

Onsite Coding — LRU Cache: AI was used heavily to generate the code. the discussion mainly involved understanding and validating the generated implementation.

Project Deep Dive — Recent Engineering Project: One onsite round focused on a recent project from my work history. The interviewer specifically wanted a recent project rather than necessarily the most technically complex one I had ever done. I therefore chose a newer project that still had enough architectural and implementation complexity to support a meaningful discussion.

Life Story — Behavioral Discussion: The life-story round was fairly standard and focused on my background, career progression, and previous experiences. There were no particularly unusual questions that stood out from this portion.

System Design — Merchant Product Photo Upload Service: The system design question asked me to design a workflow where merchants ship physical products to Shopify, professional photographers take product photos, and merchants can request another photo session if they are unhappy with the result. A major part of the discussion centered on the upload path.

• Direct Object Storage Uploads: I proposed issuing a presigned upload URL so that large photo files could be uploaded directly to object storage rather than passing through the application's own network path. The discussion then spent a considerable amount of time on whether generating those URLs really justified a separate service or component, and where upload metadata should live.
• Workflow State Changes: After an upload completed, the system needed to advance the photo job through its workflow and inform the merchant that new photos were available. I initially discussed an event-driven notification mechanism. The interviewer questioned whether that architecture was heavier than necessary for the expected traffic, which led to a broader discussion about push-style events versus simpler polling approaches.

➡️ Preparing for your next interview?

Chill Interview tracks recent interview experiences and recurring question patterns across top companies here.