Amazon Interview Experience | SDE Intern (Off Campus)

Round 1: It was an online test at Mettl. It consisted of 28 MCQs based on Data structures and algorithms and some output based questions and 2 Coding Questions. Difficulty level for this was Medium.

Coding questions asked were:

  1. Euler’s Totient Function
    https://www.geeksforgeeks.org/eulers-totient-function/
  2. Count Inversions in an Array
    https://www.geeksforgeeks.org/counting-inversions/

I was able to clear this round and received interview call 2 weeks later but couldn’t attend it because of some reason then I was again called for an interview a week later.

Round 2: This was a F2F Technical Interview or I’d say more of a problem solving round. Interviewer seemed friendly. She started off by asking about myself, then after giving her introduction and straight away jumped to DS and Algo.

I was asked 2 questions –



  1. Stock Buy Sell to Maximize Profit
    https://www.geeksforgeeks.org/stock-buy-sell/
  2. Given a string and a pattern. Find the count of occurrences of pattern as sub sequence in the string(Non – overlapping).

I was able to solve both the questions. In the end she asked me if I have any questions for her and then told me to wait outside. HR told me that I’ll have a Round 2 and was called for round 2 in about half an hour.

Round 3: This was again a F2F Technical Interview / problem solving round. He straight away jumped to DS and Algo.

I was asked 2 questions –

  1. Connect n ropes with minimum cost
    https://www.geeksforgeeks.org/connect-n-ropes-minimum-cost/
    I wasn’t directly told to implement this problem but had to figure out from the problem statement that this is the underlying problem.
  2. Return the number of steps to reach from a node to another in a directed unweighted graph.
    I did it using Level Order Traversal.

I was able to solve both the questions. In the end he asked me if I have any questions for her and then told me to wait outside.

 

The thing with these technical interviews is to know the candidates’ thought process behind approaching a problem. They give you a lot of hints if you get stuck somewhere, they ask you to optimize the approach if they know this can be optimized further. After discussing the approach you are asked to write production-ready code on paper.

After 10 minute or so HR told me that I’m hired 🙂

Write your Interview Experience or mail it to contribute@geeksforgeeks.org

My Personal Notes arrow_drop_up

If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to contribute@geeksforgeeks.org. See your article appearing on the GeeksforGeeks main page and help other Geeks.

Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.