Coding assessment (an API call and data validation): It’s an easy problem that can be solved with a couple of hashmaps; don’t overthink it. If you’re stuck on: “you’re almost there, you have a couple of minor bugs in your code,” re-read the task and the text in bold carefully. Live coding: It was a LeetCode easy-style problem - not word-for-word copied from LeetCode, but you can find similar ones. I recommend practicing explaining your thinking out loud. They’re not looking for a perfect solution, and they’ll give you a ton of hints. System Design: Read the reviews. I got the most common problem mentioned. Do mock interviews, draw diagrams, and practice beforehand. I had very little experience in doing System Design, but roleplaying questions from Glassdoor and learning to draw the diagram quickly helped me ace it. Also, the interviewer was very well-spoken and supportive. Behavioural: This was a pretty difficult interview for me, and unfortunately, it’s the most important one. “Tell me about a time you had to do X at company Y.” I prepared 10 stories for different scenarios, but wasn’t prepared for that turn of events. “I don’t have an example from company Y, but I had a similar experience at company Z” was not good enough. All of the questions about your strengths (leadership, solving technical challenges, delivering on a tight deadline) will revolve around your last job or the last 2–2.5 years of your career. If you had less than 3–4 years at your last place of work and just didn’t have the time to acquire enough stories, you might be in for a bad time.