J'ai postulé via un établissement d'enseignement supérieur ou universitaire. Le processus a pris 4 semaines. J'ai passé un entretien chez Amazon (Seattle, WA)
Entretien
An Amazon recruiter came to my University to give us a spiel about working at Amazon and accepted resumes at that time. She contacted me by phone to see if I would be interested in interviewing. This was an expenses-paid trip to Seattle for a few days.
The day started with a general QA session with some really nice Amazon SE Engineers. The bulk of the interview after that was a group programming project; we were given a task, split into teams of 3, and had around 6 hours to program. We were pulled out individually during that time to discuss our individual implementation and ideas. They wanted to, of course, discuss the time complexity of the implementation. I was a bit turned off by the fact that they asked 0 questions about projects we had worked on in the past or questions to learn more about us as people--but maybe they were getting some of that information just by observing how we interacted with our teammates?
I personally think I flubbed this one--I got flustered at the start and it took me too long to get started. Be prepared to think through a large, complex problem that could involve a lot of programming and data structures. The problem in our case was divided into three parts--I took the third one, but I think it was more reliant on the other parts than I had anticipated. I recommend trying to pick a part of the problem that doesn't necessarily build from the other parts if you plan to "divide and conquer" to solve the problem.
If I had to do it again, I might try a more team-oriented approach. Instead of trying to get everything implemented in such a short amount of time, work together to really iron out the implementation on paper, and THEN get started on the implementation with really well-defined (and modest) goals for each programmer. One of the reasons I didn't feel quite comfortable with this approach at the time is that one of my teammates was sort of bashing people he had programmed with in the past... and I felt uncomfortable about adding myself to his roster of bash-ees! If I do apply again in 6 months as Amazon suggested, I'll be sure to ignore such impulses and really apply myself to the idea of working as part of a team.
Questions d'entretien [1]
Question 1
Large group programming project--working on a small development team and brushing up on datastructures would be helpful for preparation
Interview by recuriter, Phone interview over Chime with one easy Leet code problem and 2 behavioral questions. Although the interviewer was very casual at the start of the conversation, it quickly changed into behavioral questions at the start.
Questions d'entretien [1]
Question 1
Encoding optimization algorithm and talk about a project you did recently.
First round is just leet code coding which screens through AI before going into live coding. Pretty simple and straighforward. Not too tough. Recruiter walks through it pretty nicely. Not sure how many rounds there are exactly
J'ai passé un entretien chez Amazon (New York, NY)
Entretien
After submitting my application for the Software Engineer position, I received an invitation to complete an automated Online Assessment (OA). The assessment consisted of standard coding challenges, primarily focusing on algorithmic and data structure problems. Unfortunately, a few days after submitting my solutions for the assessment, I received an email informing me that I would not be moving forward in the interview process and was rejected.