## Problem Build a reusable `Accordion` component in vanilla JavaScript (or React). Each section has a header and collapsible content. Only one section can be open at a time. Clicking an open header collapses it. **Requirements:** - Toggle open/closed state on header click. - Only one panel open at a time (single-expand mode). - Keyboard accessible: Enter/Space opens/closes; Arrow keys navigate between headers. - Animate expand/collapse with CSS transitions on `max-height`. ```html Section 1 Content 1 ... ``` ```javascript function initAccordion(container) { // wire up event listeners and ARIA attributes } ``` **Example behavior:** ``` Click "Section 1" -> panel 1 opens, aria-expanded=true Click "Section 2" -> panel 2 opens, panel 1 closes Click "Section 2" again -> panel 2 closes ``` ## Follow-ups 1. How would you support multi-expand mode as a configuration option? 2. What ARIA attributes are required for full screen reader compatibility? 3. How do you handle dynamic content added to panels after initialization? 4. How would you write a unit test for the keyboard navigation behavior?

InterviewDB Experience

Build an Interactive UI Element: Implement an Accessible Accordion Component

Onsite

Interview Experience

Problem Build a reusable Accordion component in vanilla JavaScript (or React). Each section has a header and collapsible content. Only one section can be open at a time. Clicking an open header collapses it. Requirements: Toggle open/closed state on header click. Only one panel open at a time (single-expand mode). Keyboard accessible: Enter/Space opens/closes; Arrow keys navigate between headers. Animate expand/collapse with CSS transitions on max-height. Example behavior: Follow-ups How would y…

Full Details

🔒

Unlock all Stripe questions

Full insider details, leaked discussions, and candidate experiences.

Get full access — from $50/mo

About This Question

This is a candidate experience report from a stripe interview during the onsite round.

It covers the following topics: Coding, Frontend, Onsite .

Topics

Coding Frontend Onsite

About Stripe Interview Reports

This question was reported by a candidate who interviewed at Stripe. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.

Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Stripe are the higher-signal extractions to take from this report.

For broader preparation context, the Stripe interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.

How To Practice This Type of Question

Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.

Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Stripe reports consistently are the ones worth investing in; one-off niche problems are not.

During Your Stripe Round

Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.

The single most predictive failure mode in Stripe reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.