did the capital one frontend engineer interview loop for a mid-level role (targeting their consumer card product team) a couple months back. leaving this here because frontend-specific write-ups for capital one are rare. most posts are SWE general or backend.
the loop structure. recruiter call, then two technical rounds, then one behavioral/values round. recruiter mentioned they occasionally add a design system or accessibility round depending on the team but my loop didn't have that.
technical round 1: coding. this was not a pure javascript puzzle. they gave me a real-ish scenario: build a component that fetches user transaction data and renders a filterable table. the catch was error handling and loading states needed to be explicit. i used vanilla javascript with fetch (they didn't require a framework). they cared a lot about: do you handle the loading state before data arrives, what happens on network error, can you write this without 10 layers of abstraction.
one follow-up was about performance: 'if this table had 10,000 rows, what would you change?' we talked virtual scrolling and pagination. they seemed impressed that i brought up requestAnimationFrame and layout thrashing proactively.
technical round 2: web fundamentals. this round was more conversational but dense. topics covered: the browser rendering pipeline (parse HTML, build DOM, CSSOM, render tree, layout, paint, composite), event delegation vs event listeners on each element (when and why), how closures work and where they bite you in loops, and a CSS specificity question. also a quick accessibility question: what makes a modal dialog keyboard-accessible?
the accessibility question threw some people in my cohort. if you don't know aria-modal, focus trapping, and restoring focus on close, brush up. capital one has a real focus on accessibility given they serve a wide consumer base.
behavioral round. four STAR questions, very standard. the one that stood out was 'tell me about a time you pushed back on a UX decision from design.' they want to see you can collaborate cross-functionally without being a pushover or dismissive.
offer. mid-level frontend in richmond VA (hybrid 3x/week): around $145-155k total comp (base + bonus). mclean/dc tends to run $10-15k higher for same level.
overall: the bar is high for web fundamentals. don't skip the browser internals and a11y basics.