Continued on Par1

10: Hyderabad FE I loop and offer

Interviews: April 18 to June 23, 2025 · Decision: June 24, 2025 · Role: Front-End Engineer I · Location: Hyderabad · Result: Selected

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

Round 1

1. Maximum Points You Can Obtain from Cards.
2. Edit Distance.
3. Explain brute-force and optimized approaches.

Round 2

1. Implement an LRU Cache with production-quality behavior.
2. Discuss taking responsibility outside the assigned role.
3. Discuss a tight deadline.

Round 3

1. Complete a Leadership Principles deep dive.
2. Answer theoretical React and JavaScript questions.

Round 4

1. Build an analog clock with 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. Discuss a project estimated at fifteen days that actually took two to three months.
4. Discuss doing something without first telling a manager.

11: AWS mid-level frontend phone and onsite

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

Phone screen

1. Solve Two Sum.

Onsite technical

1. Build a configurable digital clock in React.
2. Support different time zones.
3. Add tests.
4. Reduce unnecessary renders.

12: Bangalore FEE II partial loop

Report date: May 7, 2025 · Role: Front-End Engineer II · Location: Bangalore · Status: Two rounds completed when posted

Technical round 1

1. Build an Amazon orders or order-history interface with infinite scrolling.
2. Discuss initial data loading, pagination, caching, restoring scroll position, and edge cases.
3. Discuss React Hooks and React Window.
4. Solve an easy array DSA problem whose exact prompt was not disclosed.

Technical round 2

1. Design an autocomplete component or service at low level.
2. Draw the component or class model.
3. Discuss scalability, pagination, and API failure.

Two remaining rounds had not yet occurred when the candidate published the report.

13: Bucharest frontend loop

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

1. Complete one live-coding screen without compiling the code.
2. Complete four one-hour technical interviews covering DSA, frontend system design, and clean code.
3. Design a news website and discuss API endpoints and caching.
4. Answer Leadership Principles questions during every technical round.
5. Complete a separate HR discussion.

Most exact coding prompts were not published, so the process shape is stronger evidence than any missing question detail.

14: US FEE II loop and rejection

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

OA

1. Build a dropdown component.
2. Build a contact form.

Phone screen

1. Discuss a project the candidate was proud of.
2. Build a tab bar in React.

Final loop

1. Solve Trapping Rain Water. The interviewer requested brute force before optimization, and the candidate did not complete the final code.
2. Build a React star-rating component.
3. Answer a Leadership Principles question about solving a problem with insufficient data.
4. Complete a Bar Raiser with four behavioral questions, including a time the group disagreed but the candidate stayed with an approach.
5. Design a mobile multiple-choice math game.
6. Build a relative-time component and schedule its next update with setTimeout.

The recruiter reportedly said the frontend rounds were strong, while the DSA and Bar Raiser signals were weaker.

15: SDE II frontend virtual onsite

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

1. Implement behavior similar to JSON.stringify, followed by a Leadership Principles question about a tight deadline.
2. Build tabs in React and answer additional behavioral follow-ups.
3. Complete a hiring-manager project deep dive and design a bike-sharing application with emphasis on user experience.
4. Convert a serialized HTML-tree object into an HTML string.
5. Complete a final Leadership Principles-only round.

16: Amazon Studios frontend process

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

1. Build a React component in Amazon's plain internal code editor.
2. Complete an algorithm and data-structures round with a variant of Two Sum or Three Sum.
3. Complete a system-design round that expanded into full-stack topics such as server load balancing.
4. Meet with product and design interviewers.

The candidate identified algorithms and system design as the weaker signals. This report is a useful reminder that some frontend loops broaden well beyond browser-only architecture.

17: Screen and four-round frontend loop

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

Screen

1. Implement getElementsByStyle.
2. Build a reusable n × n chess grid in which one cell can be selected.

Round 1

1. Build an image carousel in Vanilla JavaScript.

Round 2

1. Solve a caption-equivalence problem using a dictionary of similar words.

Round 3

1. Design a news site similar to a major media portal.
2. Discuss schemas, APIs, backend behavior, video, and ads.

Round 4

1. Complete a hiring-manager and Leadership Principles discussion.

The candidate reported being ghosted after the fourth round.

18: New York New Grad FEE I offer

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

OA

1. Build an accordion and another DOM component in Vanilla JavaScript.
2. Complete the work-style assessment.

Phone screen

1. Spend roughly thirty minutes on behavioral questions.
2. Build an image carousel with basic code in an environment where the solution was not run.

Virtual loop

1. Solve Rotting Oranges and answer behavioral follow-ups.
2. Answer three behavioral questions, then build a to-do application with two easy follow-ups.
3. Answer four behavioral questions, then solve a verbose array problem with brute-force and optimized approaches.

The candidate later shared recurring story areas: conflict, improving efficiency, a significant 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 · Location: India · Result: Rejected

The candidate was a former intern and chose the frontend role.

1. Complete a Mettl OA with one undisclosed coding task, core-CS multiple-choice questions, and a separate undisclosed frontend assignment.
2. Find a triplet in a BST whose sum is zero.
3. Find the row with the maximum number of ones in a sorted binary matrix, with dimensions reported as large as 100,000.
4. Recreate a supplied interface live using pure HTML and CSS.

20: US frontend offer with a five-interview onsite

Report date: January 1, 2025 · Role: Frontend Engineer · Location: United States · Result: Accepted offer

1. Complete an OA containing coding and behavioral sections.
2. Speak with a recruiter.
3. Complete five virtual-onsite interviews across two days.
4. Complete three technical rounds, one hiring-manager system-design round, and one behavioral-only round.
5. Answer two to three Leadership Principles questions in each interview.

The candidate did not disclose the technical prompts. This report is retained because it shows the loop shape and the density of behavioral evaluation without inventing missing questions.

What repeated often enough to prioritize

Tier 1: Practice until automatic

1. Accordion, tabs, carousel, form validation, and address book.
2. DOM traversal and event handling in Vanilla JavaScript.
3. One complete React component under a timer.
4. Array, string, graph, tree, dynamic-programming, and cache problems.
5. Six to eight reusable Leadership Principles stories with metrics.

Tier 2: Be ready to explain deeply

1. Debounce, throttle, stale requests, cancellation, and pagination.
2. Infinite scrolling, caching, scroll restoration, and virtualization.
3. Component APIs, controlled state, rerender behavior, and testing.
4. Accessibility, semantic HTML, focus management, and keyboard interaction.
5. Frontend system design with APIs, analytics, performance, and failure states.

Tier 3: Higher-level differentiators

1. SSR, static rendering, hydration failures, and image performance.
2. Full-stack boundaries such as caching, load balancing, and backend contracts.
3. Product judgment when a design prompt is intentionally incomplete.
4. Production debugging tied to customer impact and measurable outcomes.

Final checklist

OA (๑ᵔ⤙ᵔ๑)

☐ I can build an accordion and validated form in Vanilla JavaScript without framework autocomplete.

☐ I can read supplied HTML and CSS before rewriting the structure.

☐ I implement the simplest complete version before optional architecture.

☐ I test validation, duplicate submissions, empty input, keyboard behavior, and state changes.

☐ I read my own invitation carefully instead of assuming every Amazon OA uses the same format.

(˶ᵔ ᵕ ᵔ˶) Live interviews

☐ I clarify requirements before coding.

☐ I can switch between UI implementation and ordinary DSA.

☐ I narrate a baseline solution, optimization, complexity, and trade-offs.

☐ I handle loading, empty, error, race, keyboard, and responsive states.

☐ I can explain component boundaries, state ownership, API contracts, and tests.

☐ I can discuss pagination, caching, virtualization, SSR, hydration, and rendering performance.

☐ I have six to eight Leadership Principles stories with measurable results.

☐ I know the exact decisions and impact behind every important project on my resume.

☐ I can explain why Amazon and why this frontend role.

Read Part 1: 2025 Amazon Frontend OA / Interviews, 25 Experiences

Read the 2026 roundup: Amazon Frontend OA / Interviews in 2026, 10 Recent Experiences

These experiences were gathered from LeetCode Discuss, Reddit, and just about anywhere else useful interview information could be found. Come hang out on FastPrep Experience and share whatever’s on your mind. 💚