2027-Cycle Capital One TDP New Grad OA / Power Day: 24 Experiences
- Company
- Capital One
- Reports
- 10 interview reports
- Level
- New Grad
- Stages
- OA → Onsite
In fall 2026 the TDP Power Day added an agentic round: fix a bug, then add a feature to a large app with Claude Code.
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.
Other 2027-cycle Capital One roundups: TIP internship 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 | Most recent report |
|---|---|---|
| Technical case (business discussion, then reading and fixing code) | 10 of 15 | 2026-10-23 (interview) |
| Behavioral / job fit | 9 of 15 | 2026-10-23 (interview) |
| Agentic coding round with Claude Code (fix a bug, then add a feature) | 7 of 15 | 2026-10-23 (interview) |
| Online assessment with four coding questions | 8 of 15 | 2026-10-12 (report date) |
| Live coding round in place of the agentic round | 3 of 15 | 2026-08-04 (report date) |
A candidate can count toward several topics, so the rows add up to more than 15.
Questions we found
Algorithms / Data Structures
| Question | Frequency | All last seen dates |
|---|---|---|
| Sort Adjacent Pairs (sort each pair; an odd last element stays put) | 2 reports | Reports: 2026-10-10 (report date), 2026-09; Additional FastPrep history: 2026-09-24 |
| Wait Until the Next Bus (shuttle arrival times) | 1 report | Reports: 2026-10-10 (report date); Additional FastPrep history: 2026-10-12, 2026-10-04, 2026-09-24 |
| Earliest Meeting Time for All Employees | 1 report | 2026-10-10 (report date) |
| Earn the Most (trading strategy optimization) | 1 report | Reports: 2026-10-10 (report date); Additional FastPrep history: 2026-10-04 |
| Count Subarrays Matching a Comparison Pattern (named as LeetCode 3034) | 1 report | Reports: 2026-09; Additional FastPrep history: 2026-10-15, 2026-09-24 |
| Brightest Position on a Street (named as LeetCode 2021) | 1 report | Reports: 2026-09; Additional FastPrep history: 2026-09-27, 2026-09-24 |
AI Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| After a code reset, add a new feature to the same large app with Claude Code (about 20 minutes, then 5 minutes of discussion) | 3 reports | 2026-10-23, 2026-10-05, 2026-09/10 |
| Find and fix a bug in a large full-stack app with Claude Code (about 20 minutes, then 5 minutes of discussion) | 3 reports | 2026-10-07, 2026-10-05, 2026-09/10 |
Technical Case
| Question | Frequency | All last seen dates |
|---|---|---|
| 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 reports | 2026-10, 2026-09/10 |
| Analyze a business problem and its technical trade-offs, then read and change existing code | 1 report | 2026-08-04 (report date) |
| A chatbot feature: what to add to it | 1 report | 2026-07-26 (report date) |
Behavioral (BQ)
| Question | Frequency | All last seen dates |
|---|---|---|
| What draws you to financial technology? (practice) | 1 report | 2026-08-02 (report date) |
| A conflict on a team and how you handled it (practice) | 1 report | 2026-07-26 (report date) |
Online assessments (OA)
OA 01: Four timed questions, two of them medium
Report date: 2026-10-12 · Role: Software Engineer New Grad · Result: Rejected
- Four CodeSignal questions: two easy, two medium. The clock was the hard part.
- Question 3 was a 2D grid problem with a very long statement.
- Question 4 was an optimization task where time complexity mattered.
OA 02: The four problems, named
Report date: 2026-10-10 · Role: Software Engineer, Early Career · Result: Rejected one to two weeks later
The assessment arrived right after the online application.
- Sorting pairs taken from an array: Sort Adjacent Pairs.
- A task built on shuttle arrival times: Wait Until the Next Bus.
- Finding the earliest meeting that works for a group of employees: Earliest Meeting Time for All Employees.
- Optimizing a trading algorithm: Earn the Most.
OA 03: Proctored, camera on
Report date: 2026-09-16 · Role: Software Engineer (TDP Program) · Location: Cary, North Carolina · Result: Rejected
- A Virtual Job Tryout, then the coding assessment. The whole process took about a week.
- Four questions: two at LeetCode-easy level and two at medium.
- It was proctored, with the camera on and the screen shared.
OA 04: One question spelled out, two named by number
Interview date: 2026-09 · Role: New grad (exact title not given)
- Given an array, put each consecutive pair in ascending order. If the length is odd, the last number stays where it is. The example:
[5,4,2,3,7]becomes[4,5,2,3,7]. Practice: Sort Adjacent Pairs. - The candidate named LeetCode 3034 (counting subarrays that match a comparison pattern): Count Subarrays Matching a Comparison Pattern.
- The candidate didn't remember question 3.
- The candidate named LeetCode 2021 (brightest position on a street): Brightest Position on a Street.
No score, timing or outcome was given.
OA 05: A perfect score and still waiting
Interview date: 2026-08 or 2026-09 · Role: Applicant for the February 2027 TDP cohort
- The General Coding Assessment felt fairly simple: no dynamic programming and no bit tricks.
- The questions were mostly arrays, sets, simulation and hash maps.
- They scored 600, but in late September they still hadn't been invited to a Power Day.
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 07 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: 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.
04: 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.
05: 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.
06: 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.
07: 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, 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.
08: 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.
09: 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.
10: 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 U.S. reports
-
The agentic round is two timed tasks: a bug fix, then a feature. Report 07 lays the structure out, and report 05 fixed the bug and then ran out of time before the feature. Reports 01, 04 and 06 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 03 only got the bug fix done and report 04 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 06 and 07 both describe business discussion, then rule tracing or debugging, then writing a function. Report 08 also ends with reading and changing code. Report 03's business part was the one they found hardest.
-
The OA is four questions with a mix of easy and medium. OA 01 and OA 03 both report two easy and two medium questions. OA 02 and OA 04 each list four problems, and both include sorting adjacent pairs.
UK graduate roles
What came up
All seven UK reports stop before a Power Day. Each describes the coding assessment, and three also describe a one-way video interview.
| Topic | Reports | Most recent report |
|---|---|---|
| One-way video interview (HireVue) after the OA | 3 of 7 | 2026-09-23 (report date) |
| Coding assessment with four questions | 7 of 7 | 2026-09-23 (report date) |
| Behavioral questions before the OA | 1 of 7 | 2026-09-16 (report date) |
UK 01: A middling video interview
Report date: 2026-09-23 · Role: Technology Graduate 2027 · Status: Waiting
- Scored 497 out of 600 on the assessment.
- The video interview ran on HireVue, and answers couldn't be re-recorded.
UK 02: Three solved, one skipped
Report date: 2026-09-21 · Role: Technology Graduate 2027 · Status: Waiting
- Solved the first three questions and didn't attempt the fourth.
- The third question scored 200 out of 300 points.
UK 03: Behavioral first, then the OA
Report date: 2026-09-16 · Role: SWE New Grad · Location: London · Result: Rejected
- The first step was a set of behavioral questions.
- Then a CodeSignal assessment: four coding questions in 70 minutes.
UK 04: Two solved and still moved on
Report date: 2026-09-14 · Role: Technology Graduate 2027 · Status: Moved to the next stage
- The first two questions went smoothly. The third answer was wrong, and they didn't reach the fourth.
- The score was around 434 out of 600, and they still advanced.
UK 05: All four solved, then a dropped connection
Report date: 2026-09-10 · Role: Technology Graduate 2027 · Status: Waiting
- Four easy-to-medium coding questions, and they solved all of them.
- The invite to the on-demand video interview came three or four days later.
- Their internet cut out during the first video question.
UK 06: Hash map, matrix, edge cases
Report date: 2026-09-10 · Role: Technology Graduate 2027
- Four questions in an hour, most of them easy.
- Question 1 was a simple hash map problem. They didn't remember question 2.
- Question 3 was a fairly simple matrix problem that they didn't finish in time.
- Question 4 was easy apart from some tricky edge cases.
- The video interview questions felt random, and it didn't go well. They felt the process weighs the behavioral side heavily.
UK 07: Arrays and strings
Report date: 2026-09-08 · Role: Technology Graduate 2027
- Four easy-to-medium questions, mostly on arrays and strings. The first two were quick, and the last two took more thought.
- This candidate called it a Codility test. The original post and another candidate in the same discussion called it CodeSignal.
Patterns across the UK reports
-
The video interview comes right after the coding test. UK 01, UK 05 and UK 06 all took a one-way video interview after the assessment. UK 01 and UK 06 both came away unsure of how it went.
-
Full marks weren't needed to move on. UK 04 advanced with about 434 out of 600.
Canada new-grad developer roles
Both Canadian reports end at the online assessment.
CA 01: Four questions in 70 minutes
Report date: 2026-10-04 · Role: Associate Software Developer (new grad) · Location: Toronto · Status: No reply yet
- The CodeSignal invite came about two weeks after applying.
- Four questions in 70 minutes.
CA 02: Three questions and a hard DP
Report date: 2026-08-19 · Role: Associate Software Engineer · Location: Toronto · Result: Not advanced
- Three LeetCode-style questions, one of them a fairly hard dynamic programming problem.
- Their score wasn't high enough to move on.
Keep practicing
- Practice problems from these reports: Sort Adjacent Pairs (OA 02, OA 04), Wait Until the Next Bus, Earliest Meeting Time for All Employees and Earn the Most (all OA 02), and Count Subarrays Matching a Comparison Pattern and Brightest Position on a Street (both OA 04).
- 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.
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.