OA Round
Questions: Two coding questions followed by typical Amazon behavioral questions. The coding questions were long implementation-based but could be simplified using scripting languages like Python or JavaScript.
Candidate's Approach
Used JavaScript instead of C++ (my primary language) to solve both coding questions, ensuring all test cases passed.
Interviewer's Feedback
No feedback provided.
Interview Round 1
Questions: Given a file consisting of many lines, each line consisting of many words, find the longest word that matches a given pattern. No constraints provided, no optimization needed; focus was on code structure, maintainability, and extensibility.
Candidate's Approach
No approach provided.
Interviewer's Feedback
No feedback provided.
Interview Round 2
Questions: Started with typical questions around Amazon's Leadership Principles, related to work experience and projects, followed by problem-solving and Linux scripting questions.
- How do you find a pattern in a file?
- How to find files in a directory?
- Standard shell script questions.
- DSA Question: Similar to "minimum-number-of-platforms-required-for-a-railway".
Note: The shadowing interviewer interfered at the end, stating the approach was wrong on a few cases, but it turned out to be a mistake on their part.
Candidate's Approach
No approach provided.
Interviewer's Feedback
No feedback provided.
HM Round
Questions: Discussed previous experience and several questions around Amazon's Leadership Principles. Followed by questions related to computer networks and Linux commands:
- How does DNS work?
- What happens when you visit Amazon.com in your browser?
- How can you troubleshoot a website that is not reachable?
- How to send SMTP via shell script?
Candidate's Approach
No approach provided.
Interviewer's Feedback
No feedback provided.
Bar Raiser Round
Questions: Started with a couple of Leadership Principles questions, followed by a low-level design problem of a Parking Lot (variation with multiple parking lots within one system). Discussed deployment, scaling, expected traffic, eliminating SPOFs in the system, database selection, and load balancer placement.
Note: The system design round was unexpected for L4/SDE1/SysDE1 roles but did not impact performance due to prior preparation.
Candidate's Approach
Felt confident in coding and believed the interviewer was satisfied with the approach and answers.
Interviewer's Feedback
No feedback provided.
Verdict
Got the offer after 2 weeks.
Compensation Details