Ostep

I want to share with you my interview experience both as an interviewer (100+ coding, sys design and behavior) and as an interviewee (also many interviews, 12+ yo).I created a step by step guide diagram for solving any coding question at FAANG interviews. This diagram isn’t a come-up of a couple days and interviews. I’ve spent a lot of effort in FAANG tech interviews for years. I’ve tried CP and so many coding websites I lost count, leetcode, hackerrank, codesignal, project euler, interviewbit, topcoder, acm-timus, codeforces, and even more that I forgot to mention here. I’ve interviewed a lot of companies and got destroyed and taken those personally. Eventually still retrospected and still managed to learn from failures. I saw how/where most people fail during interviews. The most common reason they fail during an interview, whether it’s a phone screen or onsite coding interview, is that they give up (early). The happy path of the diagram consists of 7 steps: 1. Listen to / read the problem 2. Ask clarifying questions 3. Find and suggest solutions; Evaluate Big O time & space; 4. Code the solution 5. Skim through your code 6. Dry Run your code; Choose common test cases 7. You’re Done Let me know if this diagram is helpful for you - it was for me and many candidates that I helped. I will keep this diagram updated practice-interview.com/blog/seven-steps-to-solving-coding-question as I learn more and more from new experiences.