Design an image carousel component
PremiumFrontend systemEasy
- Touch gestures
- Lazy loading
- Image preloading
Quick answer
This frontend system interview question asks you to design an image carousel component. Aim for a design that loads fast, stays responsive and is easy to maintain, then explain components, state, data fetching and trade-offs. Interviewers want to see how you structure the interface, manage state and keep the experience fast.
The problem
Design an image carousel component for an e-commerce product page, like the product gallery on Amazon. It shows one of 5 to 20 images at a time, and the hard part is making swipe, arrows and keys behave alike while loading only nearby images and staying accessible.
It has previous and next arrows, dot indicators, thumbnails, swipe on touch devices, optional autoplay, and a zoom on tap. The same component is also used on the home page banner with 3 to 5 slides, so it must be configurable and small.
What must an image carousel component do?
- Navigation: Previous and next arrows, clickable dots, thumbnails below, left and right arrow keys when focused, and swipe with a velocity threshold on touch.
- Lazy images: Only the current slide and its neighbours are loaded; the rest load on demand.
How well must it do it?
- Smoothness: Slide transitions at 60 fps on a mid-range phone; no layout shift when images load.
- Accessibility: Keyboard operable, announces the current slide, respects reduced motion, and does not trap focus.
What scale should you design for?
Use these numbers in your estimates.
The scale numbers unlock with this questionUnlock
Key concepts
- Touch gestures
- Lazy loading
- Image preloading
- ARIA carousel
- Keyboard navigation
- CSS transforms
How you’ll practise
- Requirements
- Components
- State and data
- Network and caching
- Performance and accessibility
- Wrap-up
Lala, personalized to you, gives a hint when you ask and reviews your design when you are ready.
What do interviewers look for?
In any frontend system design round.
- Starts from the user flows and the screens
- Splits the interface into clear components
- Decides where state lives and how it stays in sync
- Plans data fetching, caching and loading states
- Covers performance, accessibility and error states
- Explains how the design holds up on slow networks and small screens
Questions people ask about this interview question
- Which design type is this question?
- It is a frontend system question. You design an image carousel component and explain your choices the way you would in an interview.
- Is this question asked at entry level?
- It is marked Easy, so it suits engineers who are new to frontend system interviews. It is also a good warm-up before harder questions.
- What should I cover first?
- Start with the main user flows, the screens and the data each one needs. Agree on scope with the interviewer before you design anything.
- Can I practise it for free?
- It is a premium question. Sign up and unlock it once for 10 credits; it then stays unlocked. When you finish, Lala, your personalized AI mentor, can review your design for 30 credits.
Related questions
Updated · Written by the SevyDevy team