Internship applicants have rated the interview process at Amazon with 3.2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 40% positive. To compare, the company-average is 58.2% positive. This is according to Glassdoor user ratings.
Candidates applying for Internship roles take an average of 16 days to get hired, when considering 5 user submitted interviews for this role. To compare, the hiring process at Amazon overall takes an average of 31 days.
Common stages of the interview process at Amazon as a Internship according to 5 Glassdoor interviews include:
One on one interview: 50%
Skills test: 33%
Personality test: 17%
Here are the most commonly searched roles for interview reports -
During the interview, the interviewer fired off a series of tough behavioral questions that probed my past challenges and decision‑making—questions that, given their depth, easily consumed several minutes each—before pivoting to core machine‑learning concepts like contrastive learning, where they quizzed me on how I’d construct anchor‑positive‑negative pairs, choose an appropriate loss (e.g. InfoNCE versus triplet loss), and leverage large batch or memory‑bank strategies to learn robust embeddings; finally, they pressed me on post‑training techniques for LLMs, asking how I’d apply methods such as fine‑tuning, parameter‑efficient adapters like LoRA, low‑bit quantization, pruning, distillation, and even RLHF to both shrink model size and align outputs with human preferences—all delivered with a somewhat challenging tone that tested not only my technical knowledge but also my ability to stay calm, structured, and concise under pressure.
Interview questions [1]
Question 1
What's contrastive learning? Tell me about the procedure
I applied through other source. The process took 4 weeks. I interviewed at Amazon in Jan 2025
Interview
The interview process was heavily focused on algorithmic thinking, featuring multiple LeetCode-style problems. One was categorized as easy, testing basic data structures, while the other was medium difficulty, involving edge cases, optimization, and clean code structure. Communication of thought process, time management, and code correctness were all emphasized throughout the session. It felt like a typical competitive programming challenge.
A few questions and leetcode question and bq questions, first introduce yourself and then answer the questions they have, and then solve a few questions , and then answer a few bq questions