YOE: <1
Degree: BE Computer Science, MS Data Science
Location: United States
Background Information
After trying to get into Amazon for 2 and a half years. Making it to the final round each time you can say I have been determined to get this job since my Sophmore Year of University. This has been a long time coming and I prepared a tried to get this job. Endless nights of studying, Leetcode, Hackerrank, Systems Design Practice, CodePath Courses. If I can say anything about rejection I've been rejected countless times by over 100 companies and about 30 times I've made it to the final round and could not close until now. If I have any advice is Start Interviewing early and get better practice enough practice where it becomes a conversation, and start Leetcoding/ Hackerranking/ until you have basic ideas and foundation of any approach to a problem.
If I could recommend anything at all it is CodePath Interview 12 Week FREE Program. It gives you structure and what I mostly struggled with at first is the initial idea of how a problem should be approached. And they help learning key-words to look for and approaches. Everyone should sign-up
Other than that do not get discourage by rejection do what programmers do best. Put your hood back up, put a smile on your face, and Code.
ROUND-1 : Call with Recruiter
ROUND-2 : OA
I believe I got this one and passed most test cases.
Question 1: Minimum Spanning Tree
Question 2: Find closest points to a certain spot in a graph
ROUND-3 : Technical Interview Phone Call
ROUND-4 : 5 Virtual Onsite Interviews
Tips- Try to approach the coding problems with a clear head and like you would approach real world problems. Understand what the questions means and ask clarifying questions and state your assumptions and get approval from the Interviewer. Match the problem into a problem that you may have looked at or a thought process you can think about (DFS, Binary Search, Tree Traversals, Graph Traversals, Adjancency List), talk about edge cases (Start off with a good approach that will work) and talk about the bad ones that forsure would not work and if you can assume they won't be inputs or you need to check for them. Talk to your interviewer of the ideas you have (Multiple approaches starting with what you think may be bad and then talk about pros cons and complexities) If you get stuck thinking of a better solution the interview sometimes helps.
Tips - Write down a lot of stories and the LP's they allign with. when I read comments like "You need 2 stories per LP" Sounds a bit crazy for me. I had like 7 concrete stories that demostrated behaviors I follow and the LP's that correlated with them (Ownership, Customer Obessesion, Learn and be Curious, etc etc)