Status: BS, MS, 3+ YOE
Position: Software Developer at a Local Government
Date: February, 2021

Technical Phone Screen (1 hour) Jan 19th:
Introduction Interviewer 5 mins
Introduction Interviewee 5 mins
Leadership Principles - 20 mins
Coding question and Clarification - 6 mins
Coding - 14 to 18 mins
Final questions to interviewer - 5 mins

Virtual Onsite 1st - Manager Interview (1 hour) on the day:
Introduction Interviewer 5 mins
Introduction Interviewee 5 mins
Leadership Principles - 25 mins
System Design question and clarification - 10 mins
Design and Explanation - 13 mins

Virtual Onsite 2nd - Technical Team(2 folks) Interview (1 hour) on the day:
Introduction Interviewer 5 mins
Introduction Interviewee 5 mins
Leadership Principles - 22 mins
Object Oriented Design question and clarification - 10 mins
Coding 10 mins
Questions - 5 mins

Virtual Onsite 3rd - Technical Interview from different team (2 folks) (1 hour) on the day:
Introduction Interviewer 10 mins
Introduction Interviewee 2 mins
Leadership Principles - 25 mins
Technical Coding interview involving stack and clarification- 15 mins
Coding - 7 mins
Questions - 3 mins

Virtual Onsite 4th Technical Interview from Team(1 person) (1 hour) on the day:
Introduction Interviewer 5 mins
Introduction Interviewee 3 mins ( learnt to keep it short by this time)
Leadership Principles - 16 mins (learnt to keep it effective at this point)
Technical Coding interview of real world scenario and clarification - 7- 10 mins
Coding - 15 - 20 mins
Questions and chatting - remaining time.

Note: The last interview should be the typical style of your interview. You have to get to the coding question by the 25th minute. If not, you are losing control of the interview. The least you can do is the 30 th minute. But you have to be really good at coding in 15 or less minutes. I wasn’t. I am a critical thinker and take a long time to think out a solution. I learnt my lesson to obtain a better understanding of the solution before I code and to practice coding faster.

Result: Recruiter called 3 working days later to confirm rejection. Feedback was coding as expected.

Behavioral note: My behavioral was good from what I know because of my communication skills. Things to follow: STAR method; Story should have a good outcome, if not, its not worth taking up; Have some metrics in hand for the story(saved millions of dollars, improved speed, reduced latency by ms/seconds, application processees billions of dollars worth, number of user /requests, etc); throw in technical details that are universal; it should always be something you did or happened to you in real life(you should have lived the story, no matter how small). Always provide a 2 sentence gist of the story after you explained the S-ituation or at the end.

Some helpful resources: https://theinterviewguys.com/star-method/
https://managementconsulted.com/amazon-leadership-principles/

The question oriented approach. Write up a story based on the questions in the links above.
OR
LP oriented approach. A mix of both works great.

Preparation for LP questions:

Created a doc with the LP from Amazon's site
For each of their LP created 4 examples. This is necessary as the LP could be asked more than once(I guess).
Out of the 4 examples, prioritize 2 unique examples for each and write about them in points so that its easy to take a print out a few days before your interview to revise it.
Prioritize the most asked one from the list. It really depends on your experience level. The recruiter briefing a week before the interview will give you a lot of information.
There may be questions you did not prepare for. Just take a nice 1 minute pause, think it out and go with it from your experience.