Mock Interviews

The Interview Flow

1. Greeting & Small Talk (1-2 min): Be professional but personable
2. Problem Introduction (2-3 min): Listen carefully, ask clarifying questions
3. Thinking Out Loud (3-5 min): Discuss approach before coding
4. Coding (15-20 min): Narrate your code as you write it
5. Testing (3-5 min): Walk through examples verbally
6. Follow-up (2-5 min): Handle optimization or extension questions

Clarifying Questions to Always Ask

// Before coding, clarify:
1. "Can the input array be empty?"
2. "Are there any duplicate values?"
3. "Is the array sorted?"
4. "What should I return if no solution exists?"
5. "What are the constraints on input size?"
6. "Can the values be negative?"

Think-Aloud Framework

Phase 1: Understanding
"Let me make sure I understand the problem correctly. We need to [restate problem]. The input is [describe input], and we need to return [describe output]."

Phase 2: Approach
"I'm thinking about using [pattern name] because [reason]. My approach would be to [high-level steps]. The time complexity would be [X] and space complexity would be [Y]."

Phase 3: Coding
"I'm creating a [variable name] to store [purpose]. Now I'm iterating through [structure] to [purpose]."

Phase 4: Testing
"Let me trace through the first example. Starting with [initial state], after processing [element], we get [result]. The final answer is [answer]."

Common Interview Mistakes to Avoid

1. Jumping into code too quickly: Always discuss approach first
2. Not asking questions: Shows poor communication skills
3. Silent coding: Interviewers can't evaluate your thought process
4. Ignoring edge cases: Discuss them explicitly
5. Not optimizing: Always mention if a better solution exists
6. Giving up too quickly: Talk through your reasoning when stuck

The STAR Method

Component	Description	Time
Situation	Set the context	15-20%
Task	Describe your responsibility	10-15%
Action	Explain what you did	50-60%
Result	Share the outcome	15-20%

STAR Example Template

Situation: "In my previous role at [Company], we were [context]."

Task: "I was responsible for [specific responsibility]."

Action: "I [specific actions you took]. First, I [step 1]. Then, I [step 2]. Finally, I [step 3]."

Result: "As a result, [quantifiable outcome]. This led to [broader impact]."

Amazon Leadership Principles - Common Questions

Leadership Principle	Common Question
Customer Obsession	"Tell me about a time you went above and beyond for a customer."
Ownership	"Describe a situation where you took responsibility beyond your role."
Invent and Simplify	"Share an example of how you improved a process."
Are Right, A Lot	"Tell me about a time you made a difficult decision with limited data."
Learn and Be Curious	"How do you stay current with industry trends?"
Hire and Develop the Best	"Describe your approach to mentoring junior team members."
Insist on the Highest Standards	"Give an example of when you refused to compromise on quality."
Think Big	"Tell me about a time you proposed an ambitious solution."
Bias for Action	"Describe a situation where you had to act quickly."
Frugality	"Give an example of doing more with less."
Earn Trust	"Tell me about a time you had to rebuild trust with a stakeholder."
Dive Deep	"Describe a time you used data to solve a problem."
Have Backbone; Disagree and Commit	"Share an example of when you disagreed with a decision."
Deliver Results	"Tell me about a time you exceeded expectations."

Behavioral Question Preparation

Prepare 8-10 stories covering:

1. A technical challenge you overcame
2. A time you disagreed with a team member/manager
3. A project where you took ownership
4. A failure and what you learned
5. A time you mentored someone
6. A tight deadline situation
7. A customer-facing issue
8. A process improvement you implemented