Amazon Non Software Development Engineer interview questions
based on 3.4K ratings - Updated Jun 24, 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 2996 - 3000 of 3,377 Interviews
Amazon interviews FAQs
Candidates applying for Non Software Development Engineer roles take an average of 16 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 27 days.
Common stages of the interview process at Amazon as a Non Software Development Engineer according to 1 Glassdoor interviews include:
Phone interview: 50%
Skills test: 50%
Here are the most commonly searched roles for interview reports -
I ha three technical phone screens and then onsite.
Onsite interview was like a coding problem and the students are divided in to a group of 3.
We need to solve it and the engineers would come over and will ask your design and way of approach to the problem. Later some time they will call you and review the code.
Interview questions [1]
Question 1
Its says team project. But remember each member is evaluated independently.
I applied through a recruiter. I interviewed at Amazon in Jan 2013
Interview
Best way to get your foot in the door is to send your resume to a recruiter. Was a little frustrated that for the first phone interview, they ended up not calling and had to reschedule a month later. The interview itself was straight-forward, no-frills, coding questions. Used a website that allows the interviewer to see code that you type up. Still in the process of interviewing.
Interview questions [1]
Question 1
As one author put it, Amazon loves Object-Oriented Questions. It seems like the interviewers are more concerned with the process and quality of code over the number of questions you're able to answer, although I'm sure a good balance of both is useful.
I applied online. The process took 4 weeks. I interviewed at Amazon (Seattle, WA) in Dec 2012
Interview
I applied online and got contacted roughly 2 weeks later.
The first interview was a technical interview in which I was asked one question to implement a function that required recursion. I was a bit rusty on recursion so I struggled with it, but the interviewer gave me tips and was helpful and I eventually got the solution. I thought due to my struggles that I would simply be brushed off from that point. However, I was surprised to see that I passed and moved on to the next stage.
The second interview was two weeks later, in which the interviewer didn't call and it had to be rescheduled. At the rescheduled interviewed, the interviewer had a thick accent and explained the function that she wanted me to code. Throughout the interview her tone of voice generally sounded depressed or bored and she didn't really offer any positive acknowledgements like the first interviewer. I finished the function but got it wrong since I mistaken what she wanted probably due to her accent, but quickly fixed it to be what it was supposed to be within 30 seconds.
I found out a week later that they're going to pursue other candidates.
Overall, the first interviewer was clean, concise, and helpful in what he wanted me to do, even though I struggled I passed the first phase. The second interviewer seemed as though she wasn't as organized (missed first scheduled interview, really did not explain the question clearly - the first interviewer copy pasted an exact description of the function + examples, whereas she manually typed in some examples while trying to explain it), and clearly was not excited or enthused about her job (or maybe the interviewing portion of it).