A recruiter reached out on LinkedIn. I responded a month later, and they seemed eager to recruit me.
Instead of a phone interview, I was given a coding challenge. I had studied using AlgoExpert and completed about 25% - 30% of those questions, covering each category.
I was given a coding challenge – I believe it was two hours to complete two questions. They were a little tricky, but I was able to figure them out just in the nick of time. I thought they were of appropriate difficulty.
A few days later, I was invited to a final interview. It was virtual, and I had four back-to-back hour-long interviews.
Most of the interviewers were nice, but the first one seemed very rude. I think I just caught him on an off day. Overall, it was a positive interview experience.
The speed of the process was also great. After passing the coding challenge, I was able to schedule the interview as soon as a few days later, or as late as a month and a half out in the future. I opted for sooner since I was trying to coordinate with other interviews.
I received an acceptance offer exactly three business days after the interview.
One interview was a standard coding challenge: a LeetCode medium problem about the amount of water between an array of walls of varying heights.
Another interview involved writing out the APIs for a simple program, focusing on object-oriented design.
A third interview was also a coding challenge, but it was more about writing APIs for a publish/subscribe model.
And the last one had no code; it was just a high-level discussion about how I would organize a solution to a coding challenge.
The following metrics were computed from 12 interview experiences for the Amazon Software Engineer role in Arlington, Virginia.
Amazon's interview process for their Software Engineer roles in Arlington, Virginia is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Amazon's Software Engineer interview process in Arlington, Virginia.