Amazon Non Software Development Engineer interview questions
based on 3.4K ratings - Updated Jun 28, 2026
Averageinterview difficulty
Very positiveinterview experience
How others got an interview
48%
Applied online
Applied online
20%
Campus Recruiting
Campus Recruiting
18%
Recruiter
Recruiter
11%
Employee Referral
Employee Referral
1%
Other
Other
1%
In Person
In Person
1%
Staffing Agency
Staffing Agency
Interview search
3,377 interviews
Viewing 161 - 165 of 3,377 Interviews
Amazon interviews FAQs
Non Software Development Engineer applicants have rated the interview process at Amazon with 4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 58.7% positive. This is according to Glassdoor user ratings.
Candidates applying for Non Software Development Engineer roles take an average of 90 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Amazon overall takes an average of 29 days.
Common stages of the interview process at Amazon as a Non Software Development Engineer according to 1 Glassdoor interviews include:
Group panel interview: 33%
Skills test: 33%
Phone interview: 33%
Here are the most commonly searched roles for interview reports -
I applied online. I interviewed at Amazon (Berlino)
Interview
For the first stage, I did an online assessment, which had 2 DSA-type questions with some workstyle questions.
The second stage, was an hour phone screening where I was asked some behavioral type questions with 2 DSA questions (One of the questions was easy and the other was hard).
I applied through a recruiter. The process took 5 days. I interviewed at Amazon (Minneapolis, MN) in Mar 2024
Interview
I've interviewed at Amazon a few times. Ever since they've implemented their coding challenge, it's made the entire process pointless. Before, technical interviews were done with an Amazon developer and they could ask questions while you're writing out code. They could see how you approach problems, how you break down complexity. Basically, it was an evaluation of your skill as an engineer.
Now, the coding challenge is really more a test of your typing skills, the performance of the site's compiler, etc. It's a task that could easily be done by copy-pasting from some other site, but that's against the rules. It just gives you an entirely alien coding experience that doesn't actually measure anything that would indicate your quality as an engineer.
Interview questions [1]
Question 1
Create an algorithm that does some string manipulation
Multiple recruiters reached out concurrently, and they seem pretty disorganized with tracking candidates.
I ended up connecting with a great recruiter and did an Online assessment (OA). It then took forever to get lined up for a Full Interview loop. Over 2 months back and forth, applying to different teams after I did the OA with the help of the recruiter.
The quality of the interviewers during the full loop was pretty mixed. They didn't seem at all engaged, and one might have been multitasking. I wish it was in person. The questions themselves were mostly fair.
Interview questions [1]
Question 1
Every round included 15 minutes around leadership principles and then ~30 minutes to solve a technical problem.
One system design round and three coding ones.