2027-Cycle Capital One TIP Intern OA / Power Day: 12 Experiences
- Company
- Capital One
- Reports
- 12 interview reports
- Level
- Internship
- Stages
- OA → Onsite
The newest TIP report, from October 2026, already includes an agentic round where the candidate builds something with Claude Code.
Coverage: Capital One software engineering internships: the Technology Internship Program (TIP) in the U.S., one early-internship program, and SWE intern roles in Canada and India. Stages: online assessment and Power Day (called a "super day" by some), plus the shorter loops in Canada and India. Reports dated July–October 2026. For many of these reports only the posting date is known, so the July reports in particular may describe interviews from the previous cycle.
Other 2027-cycle Capital One roundups: TDP new-grad reports · reports that don't name a hiring level
U.S. TIP (Technology Internship Program)
What came up
Seven of the nine U.S. reports describe a Power Day with a coding round, a case and a behavioral round. In the behavioral round, "a time you challenged the status quo" was the question that came up most.
| Topic | Reports | Most recent report |
|---|---|---|
| Power Day: three interviews in one day | 7 of 9 | 2026-10-18 (report date) |
| Agentic round: build something with Claude Code | 1 of 9 | 2026-10-08 (report date) |
| Behavioral: a time you challenged the status quo | 4 of 9 | 2026-10 (report date) |
| Coding problem built on hash maps | 3 of 9 | 2026-10 (report date) |
| Technical case on virtual card numbers | 2 of 9 | 2026-10 (report date) |
| Four LeetCode-style coding questions (OA or technical stage) | 2 of 9 | 2026-09-09 (report date) |
A candidate can count toward several topics.
Questions we found
Low-Level Design (LLD/OOD)
| Question | Frequency | All last seen dates |
|---|---|---|
| Design a class that takes in transaction events and organizes them (practice) | 1 report | 2026-07-17 (report date) |
AI Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Build something with Claude Code during the interview (what was built isn't described) | 1 report | 2026-10-08 (report date) |
Technical Case
| Question | Frequency | All last seen dates |
|---|---|---|
| Virtual card numbers: discussion, then walk through sample data and code (practice) | 2 reports | 2026-10 (report date), 2026-08-29 (report date) |
Behavioral (BQ)
| Question | Frequency | All last seen dates |
|---|---|---|
| Tell me about a time you challenged the status quo. | 4 reports | 2026-10 (report date), 2026-08-29 (report date), 2026-07-13 (report date), 2026-07-09 (report date) |
| Why do you want to work at Capital One? | 1 report | 2026-10-08 (report date) |
| Why should we pick you? (practice) | 1 report | 2026-10-08 (report date) |
| Tell me about a time you worked on a team to reach a goal. | 1 report | 2026-08-29 (report date) |
| A time you learned something (practice) | 1 report | 2026-08-29 (report date) |
9 detailed candidate timelines
01: Three hours, and it felt comfortable
Report date: 2026-10-18 · Role: Software Engineering Intern · Location: Richmond, Virginia · Result: Offer
- Three hours in total: two hour-long interviews in a row, a one-hour break, then a final hour.
- The interviewers were senior staff, a manager and engineers. No questions were shared.
02: A language round, "why us", and an agentic build
Report date: 2026-10-08 · Role: Software Engineer (Internship) · Location: Plano, Texas · Result: Rejected
- A technical interview about a programming language that was only named at the start of the interview.
- A behavioral interview built around why Capital One and why them: Why do you want to work at Capital One? and Why would you be a good fit?
- An agentic interview: build something with Claude Code. What they built isn't described.
03: Virtual card numbers, OOP, status quo
Report date: October 2026 · Role: Software Engineer Intern · Location: McLean, Virginia · Result: Offer
They came in through an employee referral. The super day ran three hours:
- Technical case (1 hour): virtual card numbers. Practice: Digit-Coded Card Validation, our practice version of a card-rules case.
- Technical (1 hour): an object-oriented problem using hash maps, plus a question on time complexity.
- Behavioral (1 hour): Tell me about a time you challenged the status quo. Two more questions weren't described.
They felt the interviewers draw from a fixed set of questions.
04: OA and behavioral only
Report date: 2026-09-09 · Role: Software Engineer Intern · Result: Offer
- A standard CodeSignal assessment with four questions: one easy, two easy-to-medium and one medium. They said the medium one, question 3, is always some kind of matrix problem.
- About five STAR-style behavioral questions.
They had applied two years earlier and again in this cycle.
05: OOD with heaps, a virtual credit card case
Report date: 2026-08-29 · Role: Software Engineer (Internship) · Location: McLean, Virginia · Result: Offer
- Technical: an object-oriented design problem around LeetCode-medium level. It needed hash maps, heaps, sorting and tuples.
- Case: an open-ended talk about virtual credit cards, going through some sample data and code. Practice: Digit-Coded Card Validation.
- Behavioral: Tell me about a time you challenged the status quo. Also a time they worked on a team and a time they learned something (practice).
06: Four LeetCode-style questions, no final round
Report date: 2026-07-20 · Role: Software Engineer (Internship) · Location: McLean, Virginia · Result: Not advanced
- A technical stage at medium difficulty: one medium-to-hard LeetCode question, two easy ones and one medium.
- A behavioral interview. They found it hard to tell how it went.
The process took two weeks, and they didn't reach the final round.
07: A class for transaction events
Report date: 2026-07-17 · Role: Software Engineer (Internship) · Location: McLean, Virginia · Result: Offer
- The CodeSignal General Coding Assessment.
- Super day, technical case: they suggested preparing with business cases.
- Super day, two coding questions. One was to design a class that takes in transaction events and organizes them; practice it with Transaction Event Store. The second wasn't described.
They found the super day fairly easy. The whole process took four weeks.
08: A case that was more talk than code
Report date: 2026-07-13 · Role: Software Engineer (Internship) · Location: Chicago · Result: Offer
- Three interviews in one day: technical, behavioral and case.
- Behavioral: a time they changed the status quo. Practice: Tell me about a time you challenged the status quo.
- The case had some coding, but most of it was explaining their thinking about business logic.
09: Hash maps in any language
Report date: 2026-07-09 · Role: Software Engineer (Internship) · Result: Offer
- Technical: applying hash maps, in any language.
- Case: they were shown a sample Capital One technology and asked to discuss it.
- Behavioral, standard STAR: a time they went beyond the status quo. Practice: Tell me about a time you challenged the status quo.
Patterns across the U.S. reports
-
The status-quo question keeps coming back. Reports 03, 05, 08 and 09 all got a version of it.
-
The case centers on a product or business logic. Reports 03 and 05 had virtual card numbers. Report 08's case was mostly business logic with some coding, and report 09 was asked to talk about a Capital One technology.
-
The coding round is object-oriented work with hash maps. Reports 03, 05 and 09 mention hash maps. Report 05 also needed heaps and sorting, and report 07 designed a class for transaction events.
-
The day is three one-hour interviews. Reports 01 and 03 describe three hours, with report 01 taking an hour's break in the middle.
Early internship program
10: Two behavioral rounds, no coding interview
Report date: 2026-07-28 · Role: Software Engineer Intern (early-internship program) · Location: McLean, Virginia · Result: Offer
- A coding assessment.
- Two behavioral interviews about their interest in technology, plus general STAR questions.
The candidate said this early-internship program has since been discontinued, and its loop had no live coding.
Canada SWE intern
11: BFS and a manager conversation
Report date: 2026-07-05 · Role: SWE Intern · Location: Toronto · Result: Offer
- A technical interview that cared more about clean code design than hard algorithms. The question was a shortest-path problem solved with breadth-first search: Shortest Path in an Unweighted Graph.
- An engineering manager round about the work they had done before.
The process took two months, and nothing was harder than BFS or DFS.
India SWE intern
12: A one-day campus process
Report date: 2026-08-02 · Role: Software Engineering Intern · Location: Kharagpur, India · Result: Offer
- Round 1, technical discussion: their own solution to the online assessment, then the projects on their resume.
- Round 2, right after, with India's Director of Engineering: resume, projects and standard HR questions, including a recent achievement they were proud of. Practice: What is a recent accomplishment you are proud of?
They applied through their college, and everything happened in one day.
Keep practicing
- Practice problems from these reports:
- Digit-Coded Card Validation: the card-rules case (reports 03 and 05).
- Transaction Event Store: the transaction-events class (report 07).
- Shortest Path in an Unweighted Graph (report 11).
- Behavioral: the Capital One behavioral question bank has the questions candidates reported, including the status-quo, teamwork and "why Capital One" 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.