RepostedAmazon logo

Amazon · OA → Phone screen → Onsite

In process

Amazon Frontend Engineer OA and Interviews: 11 Experiences

Frontend engineer · UnknownBachelor's degreeSep 2026
Shared by

Amazon frontend engineer OA and interviews in 2026: 11 reports where vanilla JS UI builds, JS fundamentals and LeetCode-style DSA sat beside LP.

At a glance

  • Process: OA (120 minutes on HackerRank in OA 01: vanilla JS UI tasks, sometimes DSA and React debugging, plus LP) → phone screen with a UI build → a loop of three or four rounds, each pairing behavioral questions with UI coding, DSA or frontend design (01, 05, 08).
  • Asked recently: live UI builds in 7 of 11 reports (autocomplete, floating panels, product search, Like button); DSA in 8; JavaScript and browser fundamentals in 3 (01, 03, 06).
  • Difficulty: these were not only React interviews: one phone screen allowed no autocomplete or docs (01), and several loops still had medium LeetCode rounds (07, 08).
  • Practise first: Render a Comment Hierarchy, the one reported task with a FastPrep problem (01).

Coverage: 11 Amazon frontend reports from 2026 (January to August): three OAs and eight interview loops or screens. Roles: Front-End Engineer I, a new grad FEE, a full-time FEE, an L5 on Prime Video, a mid-level engineer, and some with level not given. Locations named: Bengaluru, Seattle and Vancouver. OA 01 and entry 03 share a role and post date, and OA 03 and entry 02 share a role, city and month, so they may be the same two candidates.

Interview reference image

What came up

UI building and DSA showed up about equally; frontend design and JavaScript internals were less common but went deep. Counts are out of 11.

Topic Reports Last seen
Behavioral and Leadership Principles 8 of 11 Aug 2026
DSA (arrays, graphs, trees, greedy, LeetCode medium) 8 of 11 Aug 2026
UI implementation (vanilla JS or React) 7 of 11 Aug 2026
JavaScript, DOM and browser fundamentals 3 of 11 Aug 2026
Frontend system design and performance 3 of 11 Jul 2026
React debugging (OA) 1 of 11 May 2026
Async JavaScript 1 of 11 Jan 2026
Interview reference image

Questions we found

Frontend UI

Question Reports Last seen
Vanilla JavaScript form with validation 2 May 2026
Product search: top ten results, API and debounce 1 Aug 2026
Three buttons opening closable data panels 1 Jul 2026
Like button from an image 1 Jul 2026
Autocomplete search bar with alternating rows 1 Jul 2026
Responsive product card in React 1 May 2026
Accordion 1 May 2026
Wishlist with pagination and search 1 May 2026
React debugging task 1 May 2026
Render a supplied list 1 Mar 2026

JavaScript and browser

Question Reports Last seen
Output of let vs var code 1 Aug 2026
Center content in a layout 1 Aug 2026
List virtualization 1 May 2026
getElementsByStyle 1 May 2026
Macrotasks vs microtasks, Promise vs setTimeout 1 Mar 2026

Algorithms / Data Structures

Question Reports Last seen
Render a Comment Hierarchy 1 Aug 2026
Minimum cost of repeatedly joining two elements 1 May 2026

Frontend system design

Question Reports Last seen
Real-time, lazy-loaded news feed 1 Jan 2026
Rate-limited async request queue 1 Jan 2026
Diagnose a poor LCP 1 Jan 2026

One report set also mentions explaining a frontend design process (requirements to components, state, APIs, performance and testing), with no entry recorded.

Behavioral (BQ)

Question Reports Last seen
Why Amazon? 1 Aug 2026
A mistake with real consequences 1 Aug 2026
A team heading the wrong way 1 Aug 2026
A tight deadline 1 Jul 2026
Moving forward with little information 1 Jul 2026
Conflict with a coworker 1 Jul 2026
Ownership, Customer Obsession and measured impact 1 Jan 2026

Also reported, without an entry attached: persuading a team that disagreed with you. Follow-ups asked what the candidate owned, the rejected alternatives, the data and what changed.

Online assessments (OA)

OA 01: A 120-minute HackerRank

Post date: May 10, 2026 · Role: Front-End Engineer I

  1. Build a form in vanilla JavaScript with DOM manipulation, covering validation, submission and edge cases.
  2. Build a wishlist with pagination, add and remove, search, and mark or unmark.
  3. A Leadership Principles section.
  4. Fields, rules, page size and tests were not shared.

OA 02: A form and a list

Date: March 2026 · Role: Frontend Engineer

  1. Validate a form in vanilla JavaScript and HTML, then add valid entries to a table.
  2. Render a supplied list of items. Fields, schema and tests were not shared.

OA 03: DSA plus React debugging

Interview: May 2026 · Role: Front-End Engineer I · Location: Bengaluru

  1. Two DSA problems (not shared).
  2. Debug and fix a React task; the code and tests were not shared.

8 interview loops and screens

01: A new grad FEE loop on AWS EC2 Pricing

Interviews: July 16, August 13 and August 19, 2026 · Post date: August 22, 2026 · Role: Front End Engineer, new grad (NG26) · Team: AWS EC2 Pricing

Applied June 2; phone screen July 16; moved on July 28; final rounds August 13 and 19.

  1. Phone screen: improving something, work outside normal duties, and what they would do differently. Then rebuild a design with three numbered buttons, each opening a closable panel that fetches and shows data. No autocomplete and no docs, but clarifying questions were welcome.
  2. Hiring manager: Why Amazon?, then render the nested comment hierarchy from id, parentId and text at any depth. They built an N-ary tree and later discussed a hash-map approach; clarifying took much of the 30 minutes. BQ: a mistake with real consequences.
  3. Senior engineer: resume deep dive and tech trade-offs, let vs var output, CSS centering, then a search showing the ten products most relevant to a keyword, first hardcoded, then from an API with debouncing.
  4. Bar Raiser: a deep investigation, a team heading the wrong way, and learning a frontend technology, including support for different screens, and anything important not yet covered.

02: Graphs, a product card and an offer in Bengaluru

Interview: May 2026 · Role: Front-End Engineer I · Location: Bengaluru · Result: Accepted offer

  1. A graph problem with follow-ups, a resume chat and LP.
  2. A reusable, responsive Amazon-style product card in React, plus Next.js, JavaScript, HTML, CSS, projects and AI-assisted coding.
  3. Hiring manager: resume and LP. The design and fields were not shared.

03: A greedy problem and JS/DOM

Post date: May 10, 2026 · Role: Front-End Engineer I · Result: Not selected

  1. Problem solving: minimize the total cost of repeatedly joining two elements; greedy, but the cost formula was not shared.
  2. Frontend: explain list virtualization, implement getElementsByStyle (only the name was shared) and build an accordion, explaining its state and structure.
  3. The candidate said the focus was JavaScript fundamentals, DOM traversal, component structure and UI state.

04: An autocomplete phone screen

Date: July 21, 2026 · Stage: Phone screen · Role: Full-time FEE

  1. Recreate an autocomplete search bar from an image, with result rows in alternating background colors.
  2. Behavioral: a tight deadline and a project with very little information.

05: Prime Video L5, with an offer

Interview: January 2026 · Role: L5, Prime Video · Result: Offer

  1. Coding 1: an array DSA problem, no DOM or CSS.
  2. Coding 2: a rate-limited queue for async requests in JavaScript, with Promise chains, errors and cancellation.
  3. System design: a real-time, lazy-loaded news feed; WebSocket vs SSE, virtualization and CDN edge caching.
  4. LP: Ownership and Customer Obsession, and how customer impact was measured.
  5. Bar Raiser: diagnose a poor Largest Contentful Paint and propose fixes.

06: The event loop in a Seattle screen

Report date: March 25, 2026 · Location: Seattle · Result: No offer

  1. Explain macrotasks vs microtasks, why Promise callbacks run before setTimeout, and how that affects rendering.
  2. The process also had a live DSA challenge, a React and system design round, and a behavioral round with an engineering manager.

07: A Like button, then three LeetCode mediums

Report date: July 24, 2026 · Location: Vancouver · Result: No offer

  1. Screen: build a Like button matching an image.
  2. Later: three medium LeetCode questions, more UI questions, and one behavioral-only interview expecting STAR answers.

08: Four rounds over two days

Report date: July 16, 2026 · Level: Mid-level · Result: No offer

  1. Behavioral plus LeetCode; behavioral plus frontend coding; behavioral plus LeetCode; behavioral plus frontend system design.
  2. The only prompt shared: describe a conflict with a coworker.

Patterns across the reports

  1. UI from a picture. Entries 01, 04 and 07 all rebuilt a UI from a supplied design or image.
  2. Behavioral in every round. Entries 01 and 08 had behavioral questions in each round, not just the Bar Raiser; 02 and 05 mixed LP into technical rounds.
  3. LeetCode still matters. Entry 07 had three medium LeetCode questions and 08 two LeetCode rounds; 02, 03, 05 and 06 had a DSA round.
  4. Vanilla JS in the OA. OA 01 and OA 02 both had a vanilla JavaScript form with validation.

Common questions

What is in the Amazon frontend engineer OA?

Vanilla JavaScript UI tasks such as a form and a wishlist (OA 01, OA 02), or two DSA problems plus React debugging (OA 03), sometimes with an LP section; OA 01 was 120 minutes on HackerRank.

Does the Amazon frontend interview include LeetCode?

Yes: entries 07 and 08 had LeetCode rounds, and 02, 03, 05 and 06 had a DSA round.

Is there frontend system design at Amazon?

In entries 05, 06 and 08: a real-time news feed with lazy loading in 05, a React and design round in 06.

Can you use autocomplete in the Amazon frontend screen?

Entry 01's environment had no autocomplete and no docs.

Keep practicing

Interview reference image

Sources: Anywhere useful interview info can be found.

4 total reactions. Your reactions: none.
0 comments

Comments

0

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