Amazon interview

[Sampoornesh_babu]

Amazon vadu direct ga call chesasdu..scheduled interview for Aws architect(telephonic round?

any idea how it will be going to be and how many rounds?

 

[dakumangalsingh]

Oka 5-10 rounds vuntayi 

if they want to hire you you should be more skilled than 50% of the employees working already in Amazon in your domain. 

[Amrita]

5 rounds min. 1st round phone interview taruvata coding interview on sharing screen untundi. Ayina amazon vadu pampaleda email with resources for prep and interview procedure ? 

[Sampoornesh_babu]

Inka pampaledu..one person said we will connect annadu before the interview..might be vadu cheptadu emo

[Amrita]

Please read the attachments carefully and the information below, so you can prepare for the interview.

Our style of interviewing at Amazon is a combination of technical and behavioral. They will ask questions, to ascertain your Machine learning depth. And ask one or two coding questions, as well as one or two behavioral questions.

If you are unfamiliar with behavioral interviewing, please take some time to review http://muse.cm/1K2lQJ0  

 

Attached, you will find our Amazon Leadership Principles. Our interviewers are looking to evaluate your technical qualifications for this position but they are also looking to see if you have the characteristics that exemplify our leadership principles. Please go thru each LP and think of the best example that you can to demonstrate your leadership. 

 

 Example: 

LP = Bias for Action. 

Possible question: 

 Give an example of when you had to make an important decision and had to decide between moving forward or gathering more information.  

 What did you do?  

What information is necessary for you to have before acting?

 

Here is a quora thread on some of the interview questions Amazon interviewers have asked https://www.quora.com/topic/Amazon-Interview-Questions

 

 

White Boarding:

You will be coding on the white board. If you need to make assumptions, voice those assumptions with the interviewer and through the course of your exercise, let your interviewer know what you are thinking as he/she is as interested in your thought process and how you approach the problem. There may be missing information in the problem. So, ask clarifying questions before jumping into a solution. There are no trick questions. Share your thought process when solving a problem. The thought process is as important as the solution itself. 

Also, the interviewer may provide hints along the way if you have voiced your approach.  

 

Coding:

Use sites like Interview Cake or Critique My Code to prep.

Practice on a whiteboard.

Come up with solutions in a timely manner.  Take yourself thru a practice problem prior to interview. 

Make sure your code is clean, bug-free and properly handles edge cases. If you need to write pseudo-code to gather your thoughts first (pseudo-code does not count and you must code in a specific l language of your choice), verbally tell the interviewer this is what you are doing.

 

(Hints) If you get stuck and need a hint, feel free to ask –your interviewer is here to help.
(Shadow) You might notice an additional interviewer in the room that was not included on your interview confirmation link up, he/she is there to observe and to provide feedback on our interviewer.

(repeating examples) We prefer fresh examples for each interviewer, however, if you are going to use an example more than once, please voice that to the interviewer. 

Please let me know if you have any questions?

 

[godfather03]

Good luck man...Pay chala baguntundi ani vinnanu.

[Amrita]

I am sending you the interview preparation; so you can take your time to prepare.

It may not be as tough as my interview prep, but I prefer you to be over prepared!

Please review and let me know if you have questions.

 

The next step is a one hour technical (white boarding) interview, on a shared code link.

For this interview you will want to be in front of your computer, by yourself in a quiet room, as this is a very technical, white boarding, interview.

 

For best preparation you will want to brush up on OO design, OO data structures, algorithms, Computer Science fundamentals. And have a story about the most interesting or complex system design you have done (from an overview perspective you may want to think of this in the STAR method, situation/task/action/results). Thanks!

 

Below and attached is some information to help you prepare for the interview. Please review carefully.

After reviewing my prep material attached and below; please plan to be in a quiet room, by yourself, in front of a computer to take the  Technical Phone Screen. This screen focuses on : OO development, Computer Science fundamentals and Best Practices, OO Data Structures and System Design.

 

Here is a video which might help answer some of your questions.

 

The phone interview and onsite interviews are comprised of the following components:

 

1. Technical/coding and design questions:

 

These questions will test your ability to solve a technical problem. If you are rusty, you should study up on:

o    Trees (binary/red black trees/N-ary trees, tree symetric (inverse image), tree traversal, sorting trees)

o    hash maps, stacks/queues/heap/priority que, describe hashtable

o    link lists/reverse link lists (space vs time)

o    recursion/recursive strings

o    binary search

o    Arrays - 2d/3d

o    graphs/graph traversal

o    Big O notation

-          This is the Website that recent candidates hired at Amazon, have said helped them immensely to prepare: https://www.interviewbit.com/

 

-          Specific type of tree<https://en.wikipedia.org/wiki/Trie> to review. 

Some tools you might find useful to study up for the coding portion include:

o    Leet Code or Codefights

o    Elements of Programming Interviews

o    Cracking the coding interview

o    AWS Application Architecture Center – these are the tools that we use to develop amazon services/products.

 

Some interviewers may expect you to beable to discuss examples of big-O notation,

http://pages.cs.wisc.edu/~vernon/cs367/notes/3.COMPLEXITY.html

 

And there will be basic questions on OO data structures and algorithms.

Think about all the edge case scenarios during system design (especially authentication mechanisms)

Must beable to substantiate depth of knowledge when questioned on basics of CS like Algorithms, Data structures and ability to think through the downsides with the system design.

Queues and Arrays

And they may ask you to design a system you have designed recently (distributed system design).

 

Examples of big-O notation, which is a common topic:

http://pages.cs.wisc.edu/~vernon/cs367/notes/3.COMPLEXITY.html

 

basic questions on data structures and algorithms.

Think about all the edge case scenarios during system design (especially authentication mechanisms)

Must beable to substantiate depth of knowledge when questioned on basics of CS like Algorithms, Data structures and ability to think through the downsides with the system design.

Queues and Arrays

Describe the most interesting or complex E2E system you have designed recently

 

Coding questions..see samples that you can find on Interviewbit.com and Leetcode:

-Describe Hashtable

[panipoori]

1 minute ago, godfather03 said:

Good luck man...Pay chala baguntundi ani vinnanu.

lite

[Sampoornesh_babu]

Thanks bro @ amrita

[Amrita]

6 minutes ago, Sampoornesh_babu said:

Thanks bro @ amrita

Good luck dude.

[KrishnaDevaRaya]