The recruiter would send an email where you get to pick an interview session through a calendar invite, then do a one hour coding session on the scheduled date with one of their engineers.

I directly applied to Shopify and was excited with their initial acknowledgement of the application, and that they were willing to invite me to the interview process. The first round was the technical pair coding round. They asked me to come on a codepair link which was set up with a video call provision. The interviewer was a calm, decent guy who explained the problem statement clearly, and also sort of helped me where he thought I was stuck. Coming the problem statement, I was able to get a good grasp of the problem statement and made sure the requirements were clear before jumping into coding. I suggested a couple of solutions, and with proper justification went ahead with one solution. I commented my code wherever needed and solved the problem completely. There was absolutely no doubt that I did not complete it improper way, or that I was timedout, etc. After 3-4 days of not hearing back from them, I sent a follow up mail to which they promptly replied saying I could not make it, with the usual template email for absolutely no specific reason. I was pretty shocked knowing that and later felt a waste of time introspecting on why they could have rejected me. In short, I must say it might be a big-time waste to apply to Shopify; they could reject even if you build a cloned Shopify in the test.

Applied online and sent a 1 hour coding online screen interview with dev Interviewer asked me to read question on coderpad and ask them if I had any questions. Question doesn't define highly specific input and output formats, so have to ask for those from interviewer. Unlike most interviews which really strive for correctness, this interview is more testing your object oriented design skills and TDD. For example, I initally proposed to output answer as tuples as opposed to object but the interviewer pushed me towards creating objects but not much direction other than that. I didn't know any of that until I received the rejection email (that is, what they are looking for) which I was pretty shocked by because I finished the whole interview 15 minutes early, didn't receive any negative feedback from interviewer and was able to solve problem without struggling. Appointment email actualy said "no need to prepare" for first interview but seems like there were more dimensions to it than advertised. Your code will be required to compile and run in coderpad and you will be running your code against pre-determined test that you have to copy and paste into the terminal, so make sure you actually know all the APIs you are going to use. Hopefully other devs will be able to read this to not repeat same mistakes, good luck everyone.