RepostedAmazon logo

Amazon · Phone screen → Onsite

In process

Amazon Frontend Spring 2025 Loops: 11 Experiences (Part 2 of 2)

Frontend engineer · Full-time1 year experienceBachelor's degreeSep 2026
Shared by

Amazon frontend loops from January to June 2025: 11 reports with React and Vanilla JS builds, DSA like Trapping Rain Water, frontend design and two offers.

At a glance

  • Process: OA → phone screen → four or five one-hour rounds, sometimes over two days, mixing UI coding, DSA, frontend design, a hiring manager and LP questions (entries 13, 14, 17, 18, 20).
  • Asked in this part: React tabs (14, 15), image carousel (17, 18), news-site design (13, 17), Two Sum or a variant (11, 16), plus Trapping Rain Water, Edit Distance and Rotting Oranges.
  • Difficulty: strong UI rounds did not save loops with weak DSA or Bar Raiser signals (entry 14); two new grad and FE I candidates got offers (entries 10, 18).
  • Practise first: Trapping Rain Water, LRU cache and Rotting Oranges.

Coverage: 11 reports from January to June 2025: Front-End Engineer I and new grad (entries 10, 18, 19) and experienced or level-not-stated frontend engineers (FEE II, SDE II frontend, AWS, Amazon Studios), in Hyderabad, Bangalore, India, Bucharest, New York and the US. The question tables for the whole series are in Part 1.

In this series

  • Part 1: question tables for all 21 reports, then the July–November 2025 reports (entries OA 05, 01–09).
  • Part 2 (current): spring 2025 loops, January to June (entries 10–20), including two offers.

What came up

Ten of these eleven loops had a UI build, and nine had DSA. Design rounds ranged from a news site to a banking system, and LP questions came up in almost every round.

Topic Reports Last seen
UI component built live 10 of 11 Jun 2025
DSA coding 9 of 11 Jun 2025
Frontend or system design 7 of 11 Jun 2025
LP questions inside technical rounds 6 of 11 Jun 2025

11 detailed candidate timelines

10: Hyderabad FE I loop and offer

Interview date: April 18 to June 23, 2025 (decision June 24) · Role: Front-End Engineer I · Location: Hyderabad · Result: Selected

The candidate started in an SDE I process and moved to FE I because of their frontend background.

Round 1

  1. Maximum Points You Can Obtain from Cards, and Edit Distance, with brute-force and optimized approaches.

Round 2

  1. An LRU cache with production-quality behavior.
  2. Taking responsibility outside your role; a tight deadline.

Round 3

  1. An LP deep dive, plus theory questions on React and JavaScript.

Round 4

  1. An analog clock in HTML, CSS and JavaScript.
  2. Design a banking system with savings and current accounts, interest or charges, deposits, withdrawals, balances and month-end processing.
  3. A project estimated at fifteen days that took two to three months; doing something without first telling your manager.

11: AWS mid-level frontend phone screen and onsite

Report date: June 7, 2025 · Role: AWS Frontend Engineer · Experience: four years · Result: Not stated

  1. Phone screen: Two Sum.
  2. Onsite: a configurable digital clock in React with time zones and tests, keeping rerenders low.

12: Bangalore FEE II partial loop

Report date: May 7, 2025 · Role: Front-End Engineer II · Location: Bangalore · Result: Two of four rounds done when posted

  1. Round 1: an Amazon order-history interface with infinite scrolling (initial loading, pagination, caching, restoring scroll position, edge cases); React Hooks and React Window; an easy array problem (not shared).
  2. Round 2: a low-level autocomplete component or service, with a component or class model, scalability, pagination and API failure.

13: Bucharest frontend loop

Report date: April 27, 2025 · Role: Frontend Engineer · Location: Bucharest · Result: No offer

  1. A live-coding screen where the code was not compiled.
  2. Four one-hour technical interviews on DSA, frontend system design and clean code, including a news website design with API endpoints and caching; LP questions in every round.
  3. A separate HR conversation.

14: US FEE II loop and rejection

Report date: April 21, 2025 · Role: Front-End Engineer II · Experience: seven years · Result: Rejected

  1. OA: a dropdown component and a contact form.
  2. Phone screen: a project you are proud of; a React tab bar.
  3. Final loop: Trapping Rain Water, brute force first, with the final code unfinished; a React star rating; an LP question on solving a problem with insufficient data; a Bar Raiser with four behavioral questions, including a time the group disagreed and you stayed with your approach; a mobile multiple-choice math game design; a relative-time component that schedules its next update with setTimeout.
  4. The recruiter said the frontend rounds were strong, the DSA and Bar Raiser signals weaker.

15: SDE II frontend virtual onsite

Report date: April 10, 2025 · Role: SDE II, frontend · Result: Rejected

  1. Implement JSON.stringify behavior, then an LP question about a tight deadline.
  2. Tabs in React, with more behavioral follow-ups.
  3. A hiring manager project deep dive and a bike-sharing app design focused on user experience.
  4. Convert a serialized HTML-tree object into an HTML string.
  5. A final LP-only round.

16: Amazon Studios frontend process

Report date: March 18, 2025 · Team: Amazon Studios · Role: Frontend Engineer · Result: Rejected

  1. A React component in a plain internal code editor.
  2. A Two Sum or Three Sum variant.
  3. A system design round that broadened into full-stack topics such as server load balancing.
  4. Product and design interviewers. The candidate saw algorithms and system design as their weaker rounds.

17: screen and four-round frontend loop

Report date: March 17, 2025 · Role: Frontend Engineer · Result: No decision received

  1. Screen: getElementsByStyle, and a reusable n × n chess grid where one cell can be selected.
  2. Round 1: an image carousel in Vanilla JavaScript.
  3. Round 2: caption equivalence using a dictionary of similar words.
  4. Round 3: a news site design with schemas, APIs, backend behavior, video and ads.
  5. Round 4: hiring manager and LP. No reply afterward.

18: New York new grad FEE I offer

Interview date: January 31 to February 28, 2025 · Role: New Grad Front-End Engineer I · Location: New York · Result: Offer

  1. OA (completed February 7): an accordion and a second DOM component in Vanilla JavaScript, and the work-style assessment.
  2. Phone screen: about 30 minutes of behavioral questions, then an image carousel in an editor that did not run code.
  3. Virtual loop: Rotting Oranges with behavioral follow-ups; three behavioral questions and a to-do app with two easy follow-ups; four behavioral questions and a wordy array problem, brute force then optimized.
  4. Story areas the candidate used: conflict, improving efficiency, a big challenge, a missed deadline, and solving a problem outside assigned work.

19: India FEE I interview

Report date: January 26, 2025 · Role: Front-End Engineer I (former intern) · Location: India · Result: Rejected

  1. Mettl OA: one coding task (not shared), multiple choice on DSA, OOP, networks, databases, SQL and testing, and a separate frontend assignment (not shared).
  2. Interview: a BST triplet that sums to zero; the row with the most ones in a sorted binary matrix, with dimensions up to 100,000; recreate a supplied interface in pure HTML and CSS.

20: US frontend offer after a five-interview onsite

Report date: January 1, 2025 · Role: Frontend Engineer · Location: United States · Result: Offer, accepted

  1. An OA with coding and behavioral sections, then a recruiter call.
  2. Five virtual-onsite interviews over two days: three technical, a hiring manager system design, and a behavioral-only round, with two to three LP questions in each. The technical prompts were not shared.

Patterns across the reports

  1. UI strength alone was not enough. Entry 14 was told its frontend rounds were strong but was rejected on DSA and the Bar Raiser; entry 16 saw algorithms and system design as its weak spots.
  2. Design rounds reached beyond the browser. A banking system (10), load balancing (16) and news-site backends with video and ads (17).

Common questions

How many rounds is the Amazon frontend onsite?

Four or five one-hour rounds: four in entries 13 and 17, five over two days in entry 20.

What UI questions does Amazon ask frontend engineers?

In this part: React tabs (14, 15), an image carousel (17, 18), a digital clock with time zones (11), an analog clock (10), a star rating and relative-time component (14), and a to-do app (18).

Did Amazon frontend candidates get offers in 2025?

Three in this part: an FE I offer in Hyderabad (10), a new grad offer in New York (18) and an accepted US offer (20).

Keep practicing

In this series

Interview reference image

Sources: Anywhere useful interview info can be found.

1 total reactions. Your reactions: none.
0 comments

Comments

0

No comments yet — be the first to share what you know.