Capital One TDP Agentic Power Day: 25 Experiences (Part 1 of 2)
- Company
- Capital One
- Reports
- 11 interview reports
- Level
- New Grad
- Stages
- OA → Onsite
Capital One TDP new-grad reports from the 2027 cycle: a CodeSignal OA, then a Power Day with a case, behavioral and, since fall 2026, an agentic round.
At a glance
- Process: a four-question CodeSignal assessment, then a Power Day of three rounds: a technical case, behavioral, and coding. From September 2026 the coding round was agentic, done with Claude Code (01, 03–08); the July and August Power Days still had live coding (09, 10, 11). UK graduate applicants took a one-way video interview after the assessment (Part 2).
- Asked recently: the agentic round was two timed tasks on a large app, a bug fix and then a feature (08; also 01, 03, 05, 06, 07). The case started with a Capital One product, then moved to tracing business rules, debugging and writing a similar method (07, 08); two candidates had the chatbot case (03, 11). The OA problem named twice was Sort Adjacent Pairs (OA 02, OA 04, in Part 2).
- Difficulty: two OA reports called it two easy and two medium questions (OA 01, OA 03). In the agentic round, 04 and 06 finished only the bug fix while 07 finished both with half the time left. Finishing both tasks wasn't required: 04 and 05 still got offers.
- Practise first: Sort Adjacent Pairs, Earliest Meeting Time for All Employees and Tell me about a conflict with a teammate and how you resolved it..
Coverage: Capital One new-grad software engineering: the Technology Development Program (TDP) and other new-grad SWE postings in the U.S. (or with no location given), the UK graduate scheme, and two Canadian new-grad developer roles. Stages: online assessment, a one-way video interview (UK), and Power Day. Reports dated July–October 2026. For some July and August reports only the posting date is known, so those interviews may have happened earlier.
In this series
- Part 1 (current): overview, the questions found across all 25 reports, and the 11 Power Day timelines (technical case, behavioral and the agentic round)
- Part 2: the online assessments, UK graduate reports and Canada new-grad reports (14 reports)
Other 2027-cycle Capital One roundups: TIP internship reports · experienced-hire reports · reports that don't name a hiring level
TDP and new-grad SWE (U.S. or location not given)
What came up
The September and October 2026 Power Days list three rounds: a technical case, behavioral, and the new agentic coding round. The July and August reports still describe a regular live-coding round instead.
| Topic | Reports | Last seen |
|---|---|---|
| Technical case (business discussion, then reading and fixing code) | 11 of 16 | Oct 2026 |
| Behavioral / job fit | 10 of 16 | Oct 2026 |
| Online assessment with four coding questions | 8 of 16 | Oct 2026 (report date) |
| Agentic coding round with Claude Code (fix a bug, then add a feature) | 8 of 16 | Oct 2026 |
| Live coding round in place of the agentic round | 3 of 16 | Aug 2026 (report date) |
A candidate can count toward several topics, so the rows add up to more than 16. The OA reports are in Part 2.
Questions we found
Algorithms / Data Structures
| Question | Reports | Last seen |
|---|---|---|
| Sort Adjacent Pairs (sort each pair; an odd last element stays put) | 2 | Oct 2026 (report date) |
| Wait Until the Next Bus (shuttle arrival times) | 1 | Oct 2026 (report date) |
| Earliest Meeting Time for All Employees | 1 | Oct 2026 (report date) |
| Earn the Most (trading strategy optimization) | 1 | Oct 2026 (report date) |
| Count Subarrays Matching a Comparison Pattern (named as LeetCode 3034) | 1 | Sep 2026 |
| Brightest Position on a Street (named as LeetCode 2021) | 1 | Sep 2026 |
AI Coding
| Question | Reports | Last seen |
|---|---|---|
| After a code reset, add a new feature to the same large app with Claude Code (about 20 minutes, then 5 minutes of discussion) | 4 | Oct 2026 |
| Find and fix a bug in a large full-stack app with Claude Code (about 20 minutes, then 5 minutes of discussion) | 4 | Oct 2026 |
Technical Case
| Question | Reports | Last seen |
|---|---|---|
| Discuss a Capital One product, trace business rules by hand, debug the code that applies them, then write a similar new method (code can't be run) | 2 | Oct 2026 |
| Analyze a business problem and its technical trade-offs, then read and change existing code | 1 | Aug 2026 (report date) |
| A chatbot feature: what it does for Capital One and its customers, what to add, then explaining and changing code | 2 | Oct 2026 (report date) |
Behavioral (BQ)
| Question | Reports | Last seen |
|---|---|---|
| Tell me about a time you challenged the status quo. (practice) | 1 | Oct 2026 |
| What draws you to financial technology? (practice) | 1 | Aug 2026 (report date) |
| A conflict on a team and how you handled it (practice) | 1 | Jul 2026 (report date) |
Power Day timelines
01: Strong case, stuck on the second agentic task
Interview date: 2026-10-23 · Role: TDP, February 2027 cohort · Result: Waiting
Technical case
- They felt the case went perfectly.
Behavioral
- They felt it was strong.
Agentic coding
- The round had two parts. In the second part they couldn't finish debugging their own implementation before time ran out. (Report 08 describes the second part as adding a feature.)
02: Rejected the day after
Interview date: 2026-10-08 · Role: TDP, February 2027 cohort · Result: Rejected
Technical case, behavioral, agentic coding
- No round-by-round detail was shared.
The rejection arrived on 2026-10-09, one day later, even though they felt it was one of their strongest interview days.
03: Chatbot case and a React and FastAPI app
Report date: 2026-10-08 · Role: New-grad software engineer (exact title not given)
Behavioral
- Classic STAR questions on teamwork, conflict and failure. The candidate's advice was to prepare projects that fit the STAR shape.
Technical case
- The chatbot case. The interviewer started high level: what a chatbot would do for Capital One and for its customers.
- Next came code to explain and improve, then new feature requirements, with the question of how the code would change.
- There was no coding. It was all spoken reasoning.
Agentic coding
- The codebase was full-stack, a React and Vite frontend with a Python FastAPI backend. The task was to fix bugs first, then write a new feature.
- Claude was allowed. The candidate could prompt it to find, analyze and fix the problem, but still had to understand what it did.
04: Only the bug fix, and still an offer
Interview date: 2026-10-07 · Role: TDP, February 2027 cohort · Location: Dallas (chosen) · Result: Offer
Technical case
- It went fine overall. They stumbled on the business-assessment part but landed on an answer that worked.
Behavioral
- Easy conversation, and they got along with the interviewer.
Agentic coding
- Their weakest round. They only got through the bug fix, not the feature, but they kept explaining what they were thinking the whole time.
An email the next morning asked to set up a recruiter call, and the offer came on that call on 2026-10-10. For February, only Dallas and a Virginia office were offered.
05: Didn't finish both agentic tasks, still an offer
Interview date: 2026-10-06 · Role: TDP, February 2027 cohort · Result: Offer (2026-10-16)
Technical case
- They made a few mistakes but caught and fixed them during the round.
Agentic coding
- The round had two tasks, and they didn't finish both before time ran out.
06: Bug fixed, feature not reached
Interview date: 2026-10-05 · Role: TDP, February 2027 cohort · Result: No news as of 2026-10-09
Technical case and behavioral
- Both went decently.
Agentic coding
- They fixed the bug, but time ran out before they could build the feature.
07: Agentic round was the easy part
Interview date: October 2026 · Role: TDP, February 2027 cohort · Result: Asked to schedule a call
Technical case
- The business analysis and the debugging went quickly.
- Tracing the rules and writing a function took more effort, but they got there.
Behavioral
- Standard questions. It went by fast.
Agentic coding
- Their best round: both parts were done with roughly half the time to spare.
About eight business days later, they were asked to schedule a call.
08: The full fall 2026 format, step by step
Interview date: 2026-09/10 · Role: TDP Associate, February 2027 start · Result: Waiting at the time of writing
Online assessment
- The CodeSignal General Coding Assessment.
Agentic coding
- A large full-stack app opens in CodeSignal's web IDE. The candidate gets as many terminals as they want and unlimited Claude Code, with a few settings changed.
- Part 1: about 20 minutes to find and fix a bug, then 5 minutes of discussion.
- The code is reset.
- Part 2: about 20 minutes to add a new feature to the same app, then 5 minutes of discussion.
The codebase was too big to write much by hand; manual edits were only expected when the agent got something wrong. Most agentic prep online copies Meta's version, which has a smaller codebase and more data-structure work.
Technical case
- It opens with a business discussion of a Capital One product.
- Then the candidate traces a set of business rules by hand.
- Then they debug code that applies those rules.
- Then they write another method along the same lines.
Code can't be run at any point, so every line has to be checked by eye. Other candidates told them virtual card numbers come up most often here (Digit-Coded Card Validation is our practice version of a card-rules case), with AI chatbots second. They said the round followed the roughly 30-minute example video closely.
Behavioral
- Straightforward STAR questions. From their own round and from talking with others, they said the status-quo question and questions on how candidates use AI come up a lot.
Of the many candidates they talked with, few felt they aced the day and only one said the agentic round went well. A scheduled recruiter call almost always meant an offer; rejections came by email.
09: Three rounds, the older coding format
Report date: 2026-08-04 · Role: Software Engineer (TDP Program) · Result: Rejected
Technical
- A practical coding problem with an object-oriented part. They explained the data structures they chose, tested edge cases and talked through complexity.
Technology case
- They analyzed a business problem and the technical trade-offs.
- Then they read existing code and changed it.
Behavioral
- STAR questions on ownership, working with a team, conflict, picking things up fast, and getting through a hard situation.
10: Fully online, campus route
Report date: 2026-08-02 · Role: Software Engineer · Location: New York · Result: Offer
Online assessment
- A CodeSignal assessment.
Power Day (three parts, fully online)
- Technical.
- Behavioral, including what draws them to financial technology (practice).
- Case.
They applied through their university and found the interviewers very friendly.
11: Pseudocode allowed, chatbot case
Report date: 2026-07-26 · Role: TDP Software Engineer · Location: McLean, Virginia · Result: Offer
Online assessment
- A CodeSignal assessment.
Power Day
- Technical: a simple LeetCode-style question. Any language, and pseudocode was fine.
- Case: a chatbot feature, and what to add to it.
- Behavioral: a team conflict and how they handled it. Practice: Tell me about a conflict with a teammate and how you resolved it. There was also a chat with leadership.
Patterns across the Power Day reports
-
The agentic round is two timed tasks: a bug fix, then a feature. Report 08 lays the structure out, and report 06 fixed the bug and then ran out of time before the feature. Reports 01, 03, 05 and 07 also describe a round in two parts. Every description comes from September or October 2026.
-
Finishing the agentic tasks didn't decide the outcome. Report 04 only got the bug fix done and report 05 didn't finish both tasks, and both got offers. Report 02 was rejected the next day after an interview day they felt good about.
-
The case keeps the same arc. Reports 07 and 08 both describe business discussion, then rule tracing or debugging, then writing a function. Report 03's chatbot case also starts with a business question and then moves to code to explain and change, and report 09 ends with reading and changing code. Report 04's business part was the one they found hardest.
Common questions
What is the Capital One agentic technical interview?
Report 08 describes it step by step: a large full-stack app opens in CodeSignal's web IDE with unlimited Claude Code. Part 1 is about 20 minutes to find and fix a bug, then the code is reset, and Part 2 is about 20 minutes to add a feature; each part ends with 5 minutes of discussion. Reports 01, 03, 05, 06 and 07 also describe a round in two parts.
Do you have to finish both Capital One agentic tasks to get a TDP offer?
No. Candidate 04 only finished the bug fix and 05 didn't finish both tasks, and both got offers. Candidate 02 felt the day went well and was still rejected the next day.
What is on the Capital One TDP Power Day?
Three rounds: a technical case, behavioral, and coding. The coding round was agentic from September 2026 (01, 03–08) and a regular live-coding round in July and August (09, 10, 11).
How soon do you hear back after a Capital One Power Day?
Quickly for some: 04 got an email the next morning and the offer on a call three days after the interview, and 02 was rejected the next day. Candidate 07 was asked to schedule a call about eight business days later. Candidate 08 said a recruiter call almost always meant an offer, while rejections came by email.
Keep practicing
- Practice problems from these reports (the OA entries are in Part 2): Sort Adjacent Pairs (OA 02, OA 04), Earliest Meeting Time for All Employees and Earn the Most (all OA 02), Count Subarrays Matching a Comparison Pattern and Brightest Position on a Street (both OA 04), and Digit-Coded Card Validation (the card case mentioned in 08).
- Behavioral: the Capital One behavioral question bank has the questions candidates reported, including the status-quo, teamwork and conflict prompts. 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).
In this series
- Part 1 (current)
- Part 2
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.