← Amazon Interview Insights

Amazon·Frontend Engineer·Technical Phone Screen·Senior

Senior
May 2026

Summary

Amazon frontend interview that centered on a flexbox coding exercise, then pushed into design and accessibility territory fast. Two meaty follow-ups that I wasn't fully prepped for.

Questions Asked (2)

Q1

You have a flexbox layout rendering 10 boxes in a responsive grid. How would you scale it to 100 boxes? Walk through pagination vs. infinite scrolling, covering pros, cons, when each fits, performance implications, and UX impact.

Technical Trade-offsSystem Design
Author's notes

I started with infinite scrolling because it felt like the obvious modern answer, but they kept pushing on performance and I fumbled a bit.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying the requirements and constraints (e.g., data size, update frequency, device targets), then compare pagination and infinite scrolling across the specified dimensions (pros, cons, fit, performance, UX). Conclude with a recommendation and a brief implementation sketch that addresses scaling from 10 to 100 boxes.

Pro tip: Emphasize that the choice depends on user goals and content type—e.g., pagination for task-oriented or data-heavy lists, infinite scroll for exploratory feeds—and mention hybrid approaches like 'Load more' as a balanced alternative.

1. Clarify requirements and constraints

Ask about data size, update frequency, device targets, and user tasks to ground your analysis. This shows you avoid premature optimization and tailor solutions to real needs.

2. Compare pagination and infinite scrolling

Outline pros and cons of each, covering performance (DOM size, memory, network) and UX (navigation, orientation, accessibility). Be specific about how each scales from 10 to 100 boxes.

3. Match approach to use case

Explain when each fits: pagination for structured, goal-oriented content; infinite scroll for exploratory feeds. Mention hybrid patterns like 'Load more' as a compromise.

4. Address performance implications

Discuss DOM node count, rendering cost, memory, and network requests. Suggest techniques like virtualization, lazy loading, and efficient data fetching to mitigate issues.

5. Recommend and sketch implementation

Give a clear recommendation based on the context, and briefly outline how you'd implement it (e.g., flexbox with pagination controls or intersection observer for infinite scroll).

Key Points to Mention

  • DOM size and rendering performance: 100 boxes vs. 10, and how virtualization or windowing can help
  • Network efficiency: pagination reduces initial payload; infinite scroll may require careful caching and prefetching
  • UX impact: pagination offers clear position and control; infinite scroll can cause loss of context and footer access issues
  • Accessibility: pagination provides keyboard and screen-reader friendly navigation; infinite scroll needs focus management and live regions
  • Hybrid approaches: 'Load more' button combines control with incremental loading
  • Implementation details: flexbox with wrap, CSS Grid for layout, Intersection Observer API for infinite scroll, and state management for page/offset

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.

Q2

If you go with pagination, how do you make it fully accessible? Cover keyboard navigation, ARIA roles on the pagination control, focus management after a page change, and live region announcements for screen readers.

Technical Trade-offsSystem Design
Author's notes

This one tripped me up more than I expected.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by framing accessibility as a core requirement, not an afterthought, and structure your answer around the four areas the interviewer listed. For each area, explain the specific implementation (e.g., roving tabindex, aria-current, focus reset, aria-live) and tie it back to real-world trade-offs like screen reader verbosity and keyboard efficiency.

Pro tip: Mention that you would test with actual screen readers (NVDA/VoiceOver) and keyboard-only navigation, and note that pagination should be a <nav> landmark with an accessible name—this shows you go beyond checkbox accessibility.

1. Semantic structure and ARIA roles

Wrap the pagination in a <nav> element with aria-label='Pagination' and use a list (<ul>/<li>) for the page links. Use aria-current='page' on the active page link and ensure each link has a clear accessible name (e.g., 'Page 3' or 'Go to page 3').

2. Keyboard navigation

Ensure all pagination controls are focusable and operable via keyboard (Tab to move between controls, Enter/Space to activate). Consider a roving tabindex pattern so only the active page link is in the tab order, and support arrow keys to move between page links for efficiency.

3. Focus management after page change

After a page change, move focus to a logical place: either the first item of the new page content (with tabindex='-1' and focus()) or the pagination control itself if content updates asynchronously. Avoid losing focus to the top of the document; announce the change via a live region.

4. Live region announcements

Use an aria-live='polite' region (visually hidden) to announce the page change, e.g., 'Page 2 of 10, showing items 11-20'. Ensure the announcement is concise and not repeated excessively; update the live region text after the new content is rendered.

5. Testing and edge cases

Test with keyboard only and screen readers (NVDA, VoiceOver) to verify focus order, announcements, and that aria-current is conveyed. Handle edge cases like disabled previous/next buttons (use aria-disabled instead of disabled to keep focus) and dynamic content loading.

Key Points to Mention

  • Use <nav> with aria-label and a list structure for pagination.
  • Apply aria-current='page' to the active page link.
  • Implement roving tabindex and arrow key support for efficient keyboard navigation.
  • Manage focus after page change: move to new content or pagination control.
  • Use aria-live='polite' region to announce page changes and item ranges.
  • Test with screen readers and keyboard-only navigation; consider aria-disabled for unavailable controls.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.