El proceso tomó 2 días. Acudí a una entrevista en Amazon (Seattle, WA) en sept 2011
Entrevista
The big thing wasn't exact coding skills; it was ALL problem solving and worthing with a client. IE, you are the engineer, the interviewer is the client, how do you design and lay out what they need their software to do etc. The big thing was how do you build a system; I focused on making cheap, easily maintainable systems, and that was impressive to them.
I also point out some flaws with the assumptions of the questions (this isn't how all users act, etc) and that helped out a lot as well.
Even when I didn't fully understand the problem, I kept asking and figuring, trying to learn what it is that they wanted, and how I could build it. You should always talk out your thought processes, to show them they are happening, and to get them to talk as well! TALK TO GET THEM TO TALK!!
Acudí a una entrevista en Amazon (Londres, Inglaterra)
Entrevista
OA contained 2 coding questions and then followed by a multiple choice question on behavioral where they emphasized a lot on their leadership rules which you can find on their website
Preguntas de entrevista [1]
Pregunta 1
What is customer obsession and how do you apply it
Could not use AI during the first interview. The recruiter was helpful in the screener but the coding exam was tough including the take home test. Did a few Leetcode examples but apparently that wasn't enough.
Applied online via the company careers page. Received a reply from HR within a few weeks inviting me to an initial
screening call over Teams. Process also included an online coding assessment sent as a pre-interview step.
Communication from HR was professional, prompt, and friendly throughout the scheduling stage.
Preguntas de entrevista [1]
Pregunta 1
Standard background and motivation questions — what attracted me to the company, and a walk-through of recent
