Hopefully someone can shed some light into this. In the following weeks I have a couple of interviews with Shopify, and the process seems like a 5 step to me: 1) pair programming 2) Recruiter call 3) pair programming (probably FE focused) 4) Technical Deep Dive 5) Problem Solving Everything up to #3 seems straight-forward really. #4, TDD, seems to be a project that I have worked on (focusing on the architecture). #5 is the one that is troubling me, I think this is a design challenge, but I'm not sure if this is a frontend-oriented design discussion or an e2e one where I have to dive a good amount on the server-side. Any inputwould be greatly appreciated. #shopify #frontend #interview
Curious if you ever found out what #5 was
Tech Industry
7h
151
How privacy conscious are you?
India
2h
263
'Hindutva': The Radical Hindu Ideology That Seeks to 'Push Christianity Out of India’
Tech Industry
Yesterday
1725
Women, help me understand why this is inspirational
AMA
Yesterday
743
PM Manager, early 40s, married and ENM (Ethical Non Monogamous) AMA
Health & Wellness
Yesterday
642
Lasik cost
I just completed the loop. I have to give shopify credit. Every interview was very conversational and not intimidating. Interviewers are generally great there. Tdd is explaining a project that you worked on. Preferably one that you had a big part in or lead. You'll discuss the project briefly and keep going more in depth. They'll ask you technical considerations. Why did you choose x technology over y, why didn't you use some technology, how did you handle state management, what performance considerations did you make, What challenges did you face, What was unexpected, What went well, etc. I did not get a problem solving round. I applied for a senior fe dev. The pair programming rounds are straight forward. They don't change the questions much. I suggest searching on glassdoor and codesandbox and you can find examples of what to study easily.
Thank you for putting the time to reply, this is really helpful (also the first time I post anything on Blind - was a bit anxious). So regarding the project (TDD) it's related to the frontend only? Or do you kind of dive in both sides (front/back) ? Apologies for the back-to-back questions, feel free to ignore me since it's the weekend, no worries.
No worries. I think it's really up to you on what you want to focus on. It's an open ended conversation that youll be leading and they'll interject with questions along the way. I chose to give a full stack architecture overview. I started at the front end and talked about technology, considerations we made regarding tech, performance, accessibility, etc. Then I gave a high level overview of the microservice architecture of the app. Most of his tech questions focused on the front end.