Capital One interview experiences from TDP Power Days and India drives

Capital One’s interview process for Technology Development Program new grads is a CodeSignal assessment (4 problems in 70 minutes) and then a Power Day of three back-to-back one-hour interviews. The behavioral interview asks STAR questions such as how you challenged the status quo, the technical interview is practical coding like parsing data in lists, and the case interview, which engineers get too, can be a product problem or a debugging exercise. Experienced hires add a system design hour.

The February 2027 TDP posting lists a $140,000 base in McLean and $127,000 in Plano and Richmond. Most late-2025 TDP reviewers on Glassdoor did not get an offer but still rated the process positive.

Capital One interview process by round

The case interview is what sets Capital One apart from other bank technology loops: engineers face it too.

Capital One TDP Power Day and case interview experiences (2024-26)

The Capital One TDP reports on Taro and Glassdoor are brief, but they agree on the three-interview Power Day and the weight placed on STAR answers.

• TDP software engineer, November 2025, no offer. CodeSignal assessment, then a recruiter invite to Power Day: three back-to-back one-hour interviews. The behavioral one asked how they had challenged the status quo, the technical one was a data parsing problem with lists, and the case round was debugging plus more data parsing. They rated the experience positive.
• TDP software engineer, Chicago, August 2026, no offer. Described the interviews as system design-esque and very OOP-focused, with “how would you design X?” questions and standard behavioral questions. Their advice was to answer in STAR format.
• TDP Power Day, 2025. Glassdoor reviewers describe a CodeSignal test of 4 questions, then a virtual Power Day of behavioral, technical and case interviews of an hour each. One 2025 candidate’s case asked how they would gather user data for an AI chat assistant. Most late-2025 reviewers did not get an offer but rated the process positive.

Senior Lead Software Engineer, US, June 2024 (passed)

CodeSignal OA: Four problems. The first two were very simple and the instructions said not to worry about an optimal solution. The candidate skipped the third, which was the hardest, and passed half the test cases on the fourth, a medium-hard subarray problem. Raw score was above 750 out of 1200, and above 400 after review.

Power Day: Four back-to-back one-hour interviews in one day:

• Coding: Not LeetCode-style. Write a method for some business logic; the question was easy, with new requirements added as each part was finished.
• System design: Described as similar to other companies.
• Behavioral: Described as similar to other companies.
• Case study: Three linked parts: conceptual questions on software development techniques, analytical reasoning (a simple math problem) and a code review based on that reasoning.

Result: Passed. The candidate did well on the first two case parts but struggled with the third, and by the last interview was drained; their lesson was to ask for a break.

Capital One Power Day questions reported

Technical and case

1. A data parsing problem with lists (TDP, November 2025)
2. A bank account design with credits and debits across users (TDP, 2025)
3. A business-logic method where requirements are added after each part passes (Senior Lead, 2024)
4. Case: how to track cash back on a credit card (TDP, 2025)
5. Case: how to gather user data for an AI chat assistant (TDP, 2025)
6. Case: debugging plus more data parsing (TDP, November 2025)
7. “How would you design X?” questions with an OOP focus (TDP, Chicago, August 2026)

Behavioral

1. Tell me about a time you challenged the status quo
2. Tell me about a mistake and what you learned
3. Standard STAR questions, answered in STAR format; reviewers say interviewers care about the structure

Capital One interview questions with sample answers

Q. Find the longest substring without repeating characters
A. Use a sliding window with a hash map from character to its last seen index. Move the right pointer through the string; when the current character is already in the map at a position at or after the left pointer, jump left to one past that stored index rather than shrinking one step at a time. Update the map with the current index and record the best window length as right - left + 1. This is O(n) time since each pointer only moves forward, and O(min(n, k)) space where k is the alphabet size - the naive check-every-substring approach is O(n^3) and is what the follow-up asks you to improve on.

Q. Given a list of transactions, find the maximum total in any window of k consecutive days
A. This is fixed-size sliding window. Sum the first k elements to seed the window, then for each subsequent index add the incoming element and subtract the outgoing one, tracking the maximum sum seen. That is O(n) time and O(1) space, versus O(n*k) for recomputing each window from scratch. The Capital One variant usually adds a business twist - a variable window that must stay under a spending threshold, which becomes a two-pointer expand-and-shrink instead of a fixed window. Watch the edge cases the interviewer will probe: k greater than the array length, and negative amounts representing refunds, which break any assumption that a longer window is always better.

Q. How would you flatten and transform a nested JSON payload?
A. Walk the structure recursively, carrying a prefix path: for a dictionary, recurse into each key appending the key to the prefix with a dot separator; for a list, recurse into each element appending its index in brackets; for a scalar, write prefix-to-value into the flat output map. Time is O(n) in the number of nodes, and recursion depth equals nesting depth - so for untrusted payloads convert it to an explicit stack-based iteration to avoid a stack overflow, which is the answer interviewers want when they ask about a hostile input. Decide explicitly how to handle nulls and empty arrays, since dropping them versus preserving them changes the downstream schema. Guarding depth and payload size also matters because a deeply nested JSON bomb is a real denial-of-service vector for a payments API.

Q. Design a ledger or card-management module in clean OOP code
A. The core insight is that a ledger must be append-only and double-entry: every transaction writes two or more balanced entries whose debits and credits sum to zero, and you never mutate an existing entry - a correction is a new reversing entry. Model an immutable Entry with account, amount, currency, and timestamp, a Transaction grouping balanced entries, and an Account whose balance is derived by folding its entries rather than stored as a mutable field, with a periodic snapshot if reads get slow. Use integer minor units - cents - rather than floating point, because binary floats cannot represent 0.1 exactly and rounding error is unacceptable in money. For the card-management variant, model Card with a state machine (REQUESTED, ACTIVE, BLOCKED, EXPIRED) and enforce transitions in one place so an invalid jump is impossible, and never store the full PAN - store a token and last four digits.

Q. How do you guarantee a payment is not processed twice?
A. Make the write idempotent with a client-supplied idempotency key stored under a unique constraint. On each request, attempt to insert the key alongside the transaction inside a single database transaction: if the insert succeeds you process, and if it violates the unique constraint you return the stored original response instead of processing again. This works because the uniqueness check and the state change commit atomically, so a client retry after a timeout is safe. Retries are unavoidable in distributed systems - network timeouts leave the client genuinely unsure whether the write landed - which is why at-least-once delivery plus idempotent handlers is the standard pattern rather than trying to achieve exactly-once delivery, which is not possible over an unreliable network.

Power Day tips from Capital One candidates

Capital One Power Day FAQ

Capital One India: campus drives, case rounds and interview experiences

India campus placement process includes: 1. Online Assessment (90 minutes) - Coding/aptitude questions. 2. Technical Interview Round 1 (60 minutes) - Technical concepts. 3. Technical Interview Round 2 (60 minutes) - Advanced concepts and projects. 4. HR Interview (30 minutes) - Motivation and company fit. Total duration: 2-3 weeks from application to offer.

Capital One interview process by round (India campus)

Capital One India campus interview experiences

Capital One runs two distinct new graduate tracks in India, software engineer and analyst, and they look nothing like each other. Pick the one your drive is for.

Experience 1: software engineer, on-campus (published write-up)

Source: GeeksforGeeks, SWE on-campus

Funnel as reported: ~100 applied to the coding round → 22 shortlisted for the next round → 7 to the technical interview → 4 to HR → 3 offers. Eligibility was 7+ CGPA, open to CSE, ECE, EEE and ENI.

Problem-solving round (the write-up calls it a case interview)

• A graph / DFS problem that could be optimized with memoization.
• A design-flavoured coding problem: build a data structure for players and ranks supporting add_player, get_rank and update_score in O(1) or O(log n).

Technical interview

• The notable part: no coding questions at all. A senior interviewer went through every project and internship on the resume in depth, plus situational scenarios.
• The candidate’s explicit takeaway was that depth on your own resume mattered more than algorithm practice at this stage.

HR round (20-25 min)

• Led by a team lead manager from the India engineering team: behavioral questions, positions of responsibility, extracurriculars. Described as a general conversation rather than an interview.

Result: Selected; the results list came out the next day.

Takeaways

• What decided it: Clearing the coding round, then depth on every resume project in a technical interview with no coding
• Common fail: Practicing only algorithms and being unable to explain your own projects in depth
• How to practice: A timed coding set; a two-minute ownership story for each project and internship

Experience 2: analyst / business analyst, on-campus (published write-up)

Source: GeeksforGeeks, Analyst profile

This track is case-interview driven and closer to a consulting process than a software one.

Resume shortlist: almost everyone above a 6.5 CPI; roughly 270 candidates cleared from the batch.

Data interpretation test (35-40 min, 30-35 questions)

• Pen and paper, calculators allowed, no negative marking; time is tight.
• Content: average profit percentage, simple and compound interest, inflation rates, with many questions on one passage. The candidate found comprehension harder than the maths.

Day 0 case interview (65 students in, 24 out)

• A micro-finance company in a village choosing between two possible customer segments.
• The decision had to rest on the maths; the candidate made calculation errors three times and the interviewer corrected each one.
• Then questions on projects and an algorithmic trading internship.

Final interview day (slot from 6:00 am to 2:30 pm): two cases plus HR

• Case: choosing broadband plans for a telecom company to maximize profit, including the break-even point.
• Case: maximizing profit, gaining market share and expanding; the interviewer challenged the candidate’s calculations, and the candidate held their position after rechecking.
• Behavioral: a problem faced in an individual project, who helped you and your mentor (the candidate regretted criticizing a previous employer here), why Capital One.

Result: Offer received but declined for another offer.

Takeaways

• What decided it: Analyst-track data interpretation plus case answers defended with the maths
• Common fail: Treating analyst OA like pure coding, or a case without clear recommendation and checks
• How to practice: DI/quant timed drills; practice stating recommendation first then supporting maths

Takeaway across both tracks: the case interview is the component that surprises people. Capital One uses it for engineers too - US Power Day reports pair coding (and system design for experienced hires) with a behavioral and a case. Practicing structured, out-loud quantitative reasoning is not optional here.

Experience 3: fresher SDE, dual online assessment + technical (published account)

Source: InterviewExperiences.in

OA 1 (~120 min): Three DSA problems - connected components, bit manipulation, dynamic programming.

OA 2 (~45 min): Weighted job scheduling (DP + binary search) plus a written system design for threaded replies in a team-chat product (data model, APIs, non-functional requirements).

Technical (~70–80 min): Deep review of OA2 solutions - approach alternatives, test cases, edge cases; design follow-ups on ER modeling and API efficiency.

Outcome: Did not advance; candidate reported managerial/HR stages would have covered resume and culture fit.

Prep takeaway: India off-campus/full-time flows are not always identical to the US Power Day - confirm whether you face one OA or two and a separate design section.

Experience 4: SDE intern, Mangalore (August 2024)

Source: Taro, August 2024

OA: Three medium-hard competitive-programming style problems; the candidate solved two and a half.

Technical rounds (two): Mostly DSA, including a BFS question and a question combining data structures and DBMS.

HR: One HR interview; no details given.

Result: No offer, though the candidate rated the experience positively.

India HR questions that come up often

1. Positions of responsibility and extracurriculars
2. Why Capital One
3. A problem you faced in a project, and who helped you
4. Mentoring experience

For India OA practice, see Capital One placement papers.

Sources

• Taro TDP report, November 2025
• Taro TDP report, Chicago, August 2026
• Glassdoor Capital One TDP interviews
• Capital One Sr. Lead Software Engineer, US, June 2024 - LeetCode Discuss (candidate report)
• February 2027 TDP posting (job posting)
• Capital One Interview Experience for SWE (On-Campus) - GeeksforGeeks
• Capital One Interview Experience Set 1 (On-Campus, Analyst Profile) - GeeksforGeeks
• Capital One India interview questions - Glassdoor (aggregated candidate reports)
• Capital One SDE intern, Mangalore, August 2024 - Taro
• Capital One SDE fresher dual OA account - InterviewExperiences.in

The Capital One interview guide covers the case interview, mini case and pay in more detail.

Similar companies

JP Morgan · Goldman Sachs · Bank of America · Wells Fargo · HSBC · Barclays