Fast-paced, technically challenging, very rewarding
Fast-paced, technically challenging, very rewarding
- Many opportunities.
- Productivity is embraced.
- Agile processes carefully guide each project to measurable success.
- Be prepared for your manager to use your peers to keep you in check.
- Everyone is brilliant, so the least productive discussions are usually a Mexican standoff of everybody being right.
Was this helpful?
Amazon Interview Questions
Amazon Interview Experiences
Software Engineer
Many rounds of interviews with very technical questions. The people were nice, but the process could be easier and more streamlined. Overall, I would recommend. Nice job, Amazon. I recommend knowing a lot of Python and C++ for the interview.
Software Engineer
The LeetCode problem was not bad; it was easy. The interviewer was nice. I solved the problem and received some follow-up questions. However, I did not get an offer. I'm unsure where the issue might be.
Software Engineer
It was a standard LeetCode-style interview with a lot of emphasis on getting the logic right. They also emphasized running tests and checking the logic against them. I was also asked to write tests for all the edge cases and identify them in the fir
Software Engineer
Seattle, Washington, United StatesNovember 30, 2023Many rounds of interviews with very technical questions. The people were nice, but the process could be easier and more streamlined. Overall, I would recommend. Nice job, Amazon. I recommend knowing a lot of Python and C++ for the interview.
Software Engineer
Seattle, Washington, United StatesApril 30, 2024The LeetCode problem was not bad; it was easy. The interviewer was nice. I solved the problem and received some follow-up questions. However, I did not get an offer. I'm unsure where the issue might be.
Software Engineer
Seattle, Washington, United StatesApril 1, 2025It was a standard LeetCode-style interview with a lot of emphasis on getting the logic right. They also emphasized running tests and checking the logic against them. I was also asked to write tests for all the edge cases and identify them in the fir
