Capital One Experienced Engineer Power Day and OA: 6 Experiences
- Company
- Capital One
- Reports
- 4 interview reports
- Level
- Full-time
- Stages
- OA → Onsite
Capital One experienced software and AI engineer reports from fall 2026: two OAs and four Power Day loops built around cards, system design and cases.
At a glance
- Process: the Power Day had four rounds in three reports: a technical case, behavioral, system design, and a coding or AI-coding round (02, 03, 04). Two reports are online assessments only (OA 01, OA 02).
- Asked recently: card and banking topics ran through the loops: a virtual credit card case (02, 03), a credit card system design (04), and an account system design (02). The Senior Lead AI Engineer was asked to design an enterprise agent platform (03), and one candidate had the chatbot case (01).
- Difficulty: candidate 02 called the AI coding round and the case easy but the system design hard. Candidate 01 rated the day easy and was still rejected.
- Practise first: Virtual Card Transaction Validator, Sort Colors and Branch with the Most Files.
Coverage: Capital One experienced-hire reports: five software engineer reports (one for a Staff Software Engineer posting) and one Senior Lead AI Engineer loop. All six candidates said they were already employed and changing jobs. Stages: online assessment and Power Day. Reports dated October to early November 2026; for the OA and Power Day reports with only a quarter given, the interviews happened between July and December 2026.
Other 2027-cycle Capital One roundups: TDP new-grad series · TIP internship reports · reports that don't name a hiring level
What came up
System design and the technical case each appeared in three of the six reports, and every Power Day report touched cards or banking in some form.
| Topic | Reports | Last seen |
|---|---|---|
| System design (credit card, account or agent platform) | 3 of 6 | Oct 2026 (report date) |
| Technical case (virtual credit cards or the chatbot case) | 3 of 6 | Oct 2026 (report date) |
| Online assessment with coding questions | 2 of 6 | Oct 2026 (report date) |
| Behavioral round | 2 of 6 | Oct 2026 |
| Coding with AI help, or AI fundamentals | 2 of 6 | Oct 2026 |
A candidate can count toward several topics. This article mixes five software engineer reports with one AI engineer loop, so the topic counts are across both.
Questions we found
Algorithms / Data Structures
| Question | Reports | Last seen |
|---|---|---|
| First Value Below Both Neighbors | 1 | Oct 2026 (report date) |
| Sorted Cyclic Shift Difference Sums | 1 | Oct 2026 (report date) |
| Find a Symbolic Matrix Pattern | 1 | Oct 2026 (report date) |
| Forward Block Placement Queries | 1 | Oct 2026 (report date) |
| Branch with the Most Files | 1 | Oct 2026 (report date) |
| Sort Colors (in place) | 1 | Oct 2026 (report date) |
| Evaluate Arithmetic Equations (three arrays and a list of signs) | 1 | Oct 2026 (report date) |
| Rotate a Matrix While Preserving Its Diagonals | 1 | Oct 2026 (report date) |
System Design
| Question | Reports | Last seen |
|---|---|---|
| A credit card system, with deep dives on payment latency and sensitive data | 1 | Oct 2026 (report date) |
| Design an Enterprise Agent Platform | 1 | Oct 2026 (report date) |
| An account-related system | 1 | Oct 2026 |
Technical Case
| Question | Reports | Last seen |
|---|---|---|
| Virtual credit cards: trade-offs, then reading and fixing code (card validator, digit-coded validation) | 2 | Oct 2026 |
| The chatbot case | 1 | Oct 2026 (report date) |
AI Coding
| Question | Reports | Last seen |
|---|---|---|
| Fix a code base with Claude Code (the candidate found it simple) | 1 | Oct 2026 |
Project Coding
| Question | Reports | Last seen |
|---|---|---|
| Debug a Python Flask cosine-similarity API from given code and tests | 1 | Oct 2026 (report date) |
AI fundamentals
| Question | Reports | Last seen |
|---|---|---|
| Guardrails, agent versus workflow, and latency | 1 | Oct 2026 (report date) |
Online assessments (OA)
OA 01: Staff Software Engineer posting, then a hiring pause
Report date: 2026-10-14 · Role: Staff Software Engineer · Result: No decision: Capital One said it wasn't hiring
- Three Python questions.
- Evaluate Arithmetic Equations: given three arrays of numbers and an array of signs, decide for each position whether the equation holds, and return an array of booleans.
- The log of a version-control tool is given as a list of "switch branch" and "push file" actions. Return the branch that received the most files, or
Noneif nothing was pushed: Branch with the Most Files. - Rotate a Matrix While Preserving Its Diagonals: apply a number of 90-degree clockwise rotations, then put both diagonals back as they were.
A week after the OA, an email said business needs had changed and the company was not hiring for the role.
OA 02: Four questions, reached through a recruiter
Report date: 2026-10-02 · Role: Software Engineer (title not given) · Result: Passed
The candidate was approached by a recruiter. The assessment had four questions:
- In an array, find the first element whose two neighbors are both strictly larger: First Value Below Both Neighbors.
- Given two arrays of equal length, shift the first one cyclically by each possible amount, compute the sum of absolute differences against the second, and return all the sums sorted in non-decreasing order: Sorted Cyclic Shift Difference Sums.
- Given a 2D matrix and a smaller pattern where each letter stands for a number (the same letter, the same number), return the coordinates of the matching submatrix with the lowest row, then lowest column: Find a Symbolic Matrix Pattern.
- A list of operations: one kind places a block at a position, another checks a run of a given length starting at a position. The answers come back as a string of 1s and 0s such as
1010: Forward Block Placement Queries.
4 detailed candidate timelines, loops, and screens
01: The chatbot case, and still rejected
Report date: 2026-10-23 · Interview date: July to September 2026 · Role: Software Engineer (title not given) · Result: Rejected
- Onsite. The case was the chatbot case that other candidates had already posted about, and the candidate described it as a special Capital One format.
- They rated the interview easy and felt positive about it, but were rejected.
02: Four parts: AI coding, behavioral, system design, case
Interview date: 2026-10-12 · Report date: 2026-11-06 · Role: Software Engineer (title not given) · Result: Not disclosed
A referral candidate who was already employed. The loop had four parts:
- AI coding: they used Claude Code and found it simple.
- Behavioral.
- System design: an account-related system. They found it hard.
- Case: a code base around virtual card numbers, which they found easy. Practice: Digit-Coded Card Validation.
03: Senior Lead AI Engineer, four rounds
Report date: 2026-10-03 · Interview date: late September 2026 · Role: Senior Lead AI Engineer · Result: Rejected
Round 1: AI engineering and system design
- Design an Enterprise Agent Platform, with follow-up questions on AI, agents and platforms.
Round 2: technical case
- Virtual credit cards. The candidate said it was the same as a virtual-credit-card validator problem: Virtual Card Transaction Validator. They felt their own performance here was weak.
Round 3: behavioral
- Booked for 60 minutes and finished in about 40. The questions were about leadership and ownership.
Round 4: coding and AI fundamentals
- Sort Colors in place: Sort Colors.
- A Python Flask API that computes cosine similarity. They were given the code and tests, then had to find the bug and fix it.
- AI fundamentals: guardrails, agent versus workflow, and latency.
04: Credit card system design, latency and sensitive data
Report date: 2026-10-02 · Role: Software Engineer (title not given) · Result: Waitlisted
A video interview loop with four rounds. The candidate said the rounds were basically the same as another candidate's report.
- System design: again a credit card system. The deep dives were the latency target for payment authorization (how many milliseconds is reasonable, and how to reach it) and where to store a user's sensitive data.
Patterns across the reports
- Cards ran through the Power Day. Report 02 had a virtual card numbers case, 03 had a virtual credit card case, and 04 had a credit card system design. Report 03 matched its case to our card validator problem.
Common questions
What is in the Capital One Power Day for experienced engineers?
Three reports describe four rounds: a technical case, behavioral, system design, and a coding or AI-coding round (02, 03, 04). Report 03's behavioral round was booked for 60 minutes and ended after about 40.
Does the Capital One Power Day include system design?
In three of the four Power Day reports: an account system (02), an enterprise agent platform (03) and a credit card system (04).
What are the Capital One experienced-hire OA questions?
OA 01 had three Python questions and OA 02 had four. Both included array and matrix work, and OA 01 added a version-control log question.
Keep practicing
- Practice problems from these reports: Branch with the Most Files (OA 01); First Value Below Both Neighbors, Sorted Cyclic Shift Difference Sums, Find a Symbolic Matrix Pattern and Forward Block Placement Queries (OA 02); Digit-Coded Card Validation (02); Virtual Card Transaction Validator and Sort Colors (03).
- System design: the Capital One system design question bank (sign-in required).
- Everything Capital One in one place: the Capital One interview page.
- More firsthand reports: the Experience feed.
- Capital One coding bank: every Capital One algorithm problem in the question bank (sign-in needed).
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.