Academic snapshot
Marks: 7.5+ CGPA / 75% (candidate-reported)
Degree: B.Tech / B.E. / M.Tech / MCA
Backlogs: None active preferred
Year: Final-year and recent grads
Capital One is a US-based bank known for credit cards, consumer banking, and data-driven financial products. India technology centers in Bengaluru and Hyderabad build digital banking applications, cloud platforms, and analytics systems supporting Capital One’s US operations.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus India | Batch OA window, PPT, college CGPA list (7.5 / 75% often printed) | Coding bar, interview depth |
| Careers portal / referral | Resume screen volume; sometimes no hard published CGPA | Still expect OA + tech loop |
| Two-OA India reports | OA1 longer DSA set; OA2 shorter DSA + design slice | Live technical still defends the OA work |
| US Power Day | CodeSignal then four interviews in one day | Passing tests + communication |
Off-campus does not mean a 7.0 cutoff. If you sit at 7.2, do not invent a Capital One exception from a Walmart blog. Spend energy on mocks and referrals.
Is 7.5 CGPA enough? It matches the commonly reported floor. Selection still hinges on OA correctness and interview narration. A 7.6 with clean timed coding beats an 8.8 that freezes on LRU eviction.
Is 70% / 7.0 enough? Usually no for campus lists that print 75%. Off-campus and referral routes sometimes weigh portfolio + OA more - still confirm the posting. Do not burn a week arguing cutoffs on Reddit.
Branches: CS/IT/ECE dominate. ECE and related streams show up when DSA is solid. Data roles may list stats/maths more explicitly.
Gaps and backlogs: Active backlogs are the usual blocker. Integrity questions are not decorative at a bank - lying about CGPA is an instant fail.
What helps the resume screen: One project you can defend (stack, hardest bug, metric), any internship with ownership language, and honest keywords (Java, SQL, APIs) you can explain. Certificates are optional. See certifications after fundamentals.
Academic snapshot
Marks: 7.5+ CGPA / 75% (candidate-reported)
Degree: B.Tech / B.E. / M.Tech / MCA
Backlogs: None active preferred
Year: Final-year and recent grads
Branch & skills
Preferred: CS / IT / ECE and related
Languages: C, C++, Java, Python
Focus: DSA, SQL, payments / credit-risk basics
Differentiator: Ledger, rate limits, session intervals
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 7.5+ CGPA / ~75% across 10th, 12th, graduation | 70% is usually below campus lists |
| Degree | B.Tech / B.E. / M.Tech / MCA | Related computing degrees on many posts |
| Branch | CS, IT, ECE (and related) | Data/cyber JDs may add stats or security |
| Year | Final year + recent grads | Intern → conversion also appears |
| Backlogs | No active backlogs preferred | Clear them before paperwork |
| Coding languages | C, C++, Java, Python | Stick to one for OA + interviews |
Minimum CGPA required (candidate-reported): 7.5+ CGPA / 75% is the commonly cited campus floor. Treat it as a shortlisting filter when printed. Clearing CGPA only gets you into the funnel - OA correctness and a coherent payments story decide the rest.
Capital One does not publish one universal India cutoff. Your placement cell mailer always wins.
Download 2026 Capital One placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Capital One does not publish one permanent official paper set. “Previous year papers” on this site are pattern trainers for the first filter and early technical rounds - not leaked live assessments.
| Round (typical) | What to practice |
|---|---|
| Online assessment | Timed accuracy on Capital One OA (~90 min) or CodeSignal-style multi-question sets |
| Technical 1 | Live coding: LRU, rate limiter, intervals, hashing |
| Technical 2 / design | Payments, ledger, simple service + schema, sometimes threading/inbox prompts |
| HR | Why fintech?, integrity, Bengaluru/Hyderabad relocation |
| Power Day (US colour) | Four interviews in one day after OA - not default India campus |
| Theme you saw in a set | What to drill next | Why Capital One asks it |
|---|---|---|
| LRU cache | HashMap + DLL; TTL variant | Session / hot-key caches |
| Rate limiter | Sliding window, token bucket | API abuse, card-auth bursts |
| Merge / sweep intervals | Max concurrent sessions | Logins, overlapping authorizations |
| Weighted job scheduling | DP on intervals | Batch jobs, SLA windows |
| Coin change / knapsack | Unbounded DP | Amounts, denominations |
| Second-highest / SQL analog | Track top-two unique | Analyst-style coding |
| Valid parentheses | Stack | Expression / rule engines |
2025 PDFs often drill “weighted job scheduling.” Own the sort-by-end + DP template, then drill a related problem with overlapping card-settlement windows. Memorising the story text does not transfer.
Capital One India hires freshers through campus placement cells, the careers portal, and referrals. After resume screen, the shape is product-fintech: timed OA (sometimes two), then coding + payments/ledger interviews, then HR.
Campus recruitment
Through college placement cells - PPT, then OA and interviews on a batch timeline.
Online applications
Apply on capitalone.com careers for early-career / fresher tech roles; follow the invite for platform and duration.
Referrals
Employee referrals improve visibility. You still need passing OA code and clear interviews.
Placement cell or recruiter checks degree, CGPA floor when printed (7.5+ / 75% commonly reported), backlogs, and year of passing. Projects and internships help when volumes are high. This is a gate - coding is the filter.
Many campus notes describe a ~90-minute mix of coding and aptitude. One India SDE fresher report described two assessments: OA1 120 minutes / three DSA problems; OA2 45 minutes with Weighted Job Scheduling plus a Slack-like threading system-design section. Treat the table as a working map.
| Section (typical single OA) | Questions (reported range) | Time feel | Focus |
|---|---|---|---|
| Aptitude / reasoning | ~15-25 (when present) | ~30-40 min | Quant, logic |
| Technical MCQs | ~8-15 (when present) | ~20-30 min | CS / SQL-flavoured |
| Coding | 1-3 problems | ~25-50+ min | Arrays, hashing, DP, intervals |
Languages: C, C++, Java, Python. Platforms: HackerRank, CodeSignal (especially US), and similar - confirm yours.
Pass bar: Fully passing solutions beat a brilliant half-answer. Some campus write-ups cite roughly 30-40% clearing OA - colour, not a promise.
Student tip: Skim all prompts. Bank the solvable one. For two-OA loops, write down your OA2 approach - the live technical may replay it.
| Minute | Move |
|---|---|
| 0-5 | Skim full paper / all coding statements |
| 5-35 | Aptitude / MCQ if present |
| 35-70 | Coding: restate → brute → optimize → code → tests |
| 70-85 | Second prompt or harden edges |
| 85-90 | Flagged aptitude only |
Deeper OA notes: Capital One Online Assessment.
Video or onsite shared editor. Expect 1-2 DSA plus a project warm-up. Patterns: LRU cache, rate limiter, merge overlapping intervals, hashing, SQL-flavoured logic.
You should:
Example narration (LRU): “Get and put in O(1) means HashMap from key to node, plus a doubly linked list for recency. I’ll move a node to head on get; evict tail on overflow.” Capacity 0 and null keys - I’ll state the rule before coding.” That 40-second plan already signals readiness.
Fresher depth. Typical prompts:
Start with users → data → APIs → consistency. Plain language beats “event-driven microservices” with no requirements.
Worked mini-outline - transfer with double-write risk:
Why Capital One / fintech (not “big US bank” only), relocation to Bengaluru or Hyderabad, integrity under pressure, joining vs exams. Know the ₹18-28 LPA fresher band. Ask one real question about the team’s product surface (cards, servicing, fraud) - it beats “what is the culture?”
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | OA (coding + aptitude) | ~90 min (or 2 OAs) | Timed accuracy |
| 2 | Technical 1 (DSA) | 45-60 min | Code + narration |
| 3 | Technical 2 (design + domain) | 45-60 min | Payments / ledger reasoning |
| 4 | HR | 20-30 min | Fit, integrity, location |
A Senior SWE Full Stack (US, May 2025) described recruiter screen → CodeSignal OA (4 questions / 70 minutes: 2 easy, 1 medium, 1 hard) → Power Day: four interviews - technical coding (~55 min on CodeSignal), code-based case, behavioral, and system design - then a next-business-day decision (Jointaro). Freshers on India campus should not schedule their week as if Power Day were the default.
What does transfer from Power Day to India campus: stamina (you may still do two technicals in a short window), platform discipline (CodeSignal vs HackerRank - read the mailer), and a code-based case habit: talk trade-offs on a messy spec instead of jumping to a class diagram. What does not transfer: assuming four interviews in one day, or staff-level design depth on a fresher India loop.
If your invite actually says Power Day: sleep the night before, keep water, and treat the behavioural slot as scored - integrity and ownership stories are not a cooldown. Same-next-business-day outcomes appear in write-ups; do not vanish from email.
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | PPT week then OA window |
| OA → shortlist | Few days common | Two-OA loops add a second window |
| Interview loop | ~1-2 weeks | Tech 1 → Tech 2 → HR |
| Offer / paperwork | Days after final round | Written offer wins |
| End to end | ~2-3 weeks campus often | Off-campus 2-4+ weeks; Power Day can be consecutive days |
| Component | Focus | Prep move this week |
|---|---|---|
| Aptitude / logic | Speed + accuracy | Timed mock quiz |
| Coding | LRU, intervals, DP, hashing | Two timed mediums |
| Domain follow-ups | Payments, ledger, SQL | Explain one flow in 3 minutes |
| HR | Why fintech, integrity | Two STAR stories + relocation |
| If CodeSignal | 70-min 4-question stamina | One full sim on a weekend |
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
If a Capital One invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Capital One sits around ₹18-28 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Capital One eligibility for freshers 2026 is candidate-reported. Common campus/SWE baseline: B.Tech/B.E./M.Tech/MCA in CS, IT, ECE, or related fields; final-year students and recent graduates; typically 7.5+ CGPA / 75% across 10th, 12th, and graduation; no active backlogs preferred. A 70% / 7.0 usually sits below the typical campus floor. Always verify the drive notice.
What you are training for: India fresher loops commonly run: Online Assessment (~90 min, coding + aptitude; some reports describe two OAs) → Technical 1 (DSA / backend / payments, ~45-60 min) → Technical 2 (system design for payments/ledger, ~45-60 min) → HR (~20-30 min). US-style loops may use CodeSignal and a Power Day of four interviews. Campus batches often finish in about 2-3 weeks.
Short version of the prep split: Treat Capital One like a fintech product company, not a generic bank aptitude test. Split time roughly: 50% DSA (LRU, rate limiter, intervals, hashing, DP), 20% domain (payments, ledger, credit-risk basics, SQL), 15% CS + projects, 15% behavioral. Clear timed OA mocks first. Languages: Java, Python, C++ (C also listed on some invites).
Week 1 - pattern, not vibes. Timed aptitude + one easy coding problem a day, plus a one-page cs fundamentals sheet. Open the Capital One previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Capital One drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Capital One usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Capital One?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Two full mocks, then only error-log topics - no new patterns. If you still have energy, redo only the questions you failed in week 2.
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Capital One-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Use this hub for the Capital One story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed Capital One papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Capital One papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Capital One-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Days 1-3: one timed Capital One paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why Capital One. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on level, location (Bengaluru / Hyderabad), hiring year, and written components.
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Software Engineer / Analyst (fresher) | ₹18-28 LPA | Primary band for this hub |
| Data / specialist early-career | Overlaps, role-dependent | Offer letter wins |
| Mid-level / senior | Higher / US bands differ | Outside fresher campus default |
Confirm base, bonus, and benefits on the written offer. Do not treat blog midpoints as guarantees.
Policies vary by BU and year. Candidates commonly care about:
Know the ₹18-28 LPA fresher context, ask how the package splits (fixed vs variable), and clarify joining date vs exams. One calm question beats aggressive negotiation with no market anchor.
Typical India fresher path: Online Assessment (~90 min, sometimes two OAs) → Technical 1 (DSA / payments) → Technical 2 (ledger / design) → HR. Campus batches often finish in about 2-3 weeks. US loops may use CodeSignal + Power Day. Confirm on your invite.
Most India fresher SWE loops report four stages. Some India write-ups add a second OA. Power Day is typically four interviews in one day after OA. Count the mailer.
Yes. Free Capital One placement papers PDF and 2024-2026 style practice sets are on this site - pattern trainers with solutions, not leaked live papers. Start with the 2026 PDF or the paper archive.
Often ~90 minutes with coding and aptitude. One India fresher report: OA1 120 min / 3 DSA; OA2 45 min with Weighted Job Scheduling + a threading design slice. US senior: CodeSignal 4 questions / 70 min. Languages: C, C++, Java, Python. Verify yours.
Commonly reported floor: 7.5+ CGPA / 75%, CS/IT/ECE-related degrees, final-year or recent grads, no active backlogs preferred. Your drive notice overrides this page.
Usually no for campus lists that print 75%. Off-campus/referral may weigh DSA more - still confirm the posting. Do not assume a 7.0 retail-tech cutoff.
Candidate-reported Software Engineer / Analyst fresher CTC often lands around ₹18-28 LPA (as of August 2026), mainly Bengaluru and Hyderabad. The written offer letter is the only number that matters.
Those are the main India hubs candidates report. HR usually checks relocation. Be honest about constraints early.
Split time roughly 50% DSA, 20% domain (payments, ledger, SQL, credit-risk basics), 15% CS/projects, 15% behavioral. Clear timed OA mocks first. Details: preparation guide.
Yes - fresher depth: simple services, schema, payments/ledger, sometimes an inbox/threading prompt. Not staff-level architecture. Sketch actors, APIs, failure modes.
A US-style final loop: typically four interviews in one day after a CodeSignal OA (coding, case, behavioral, design). India campus freshers more often see a multi-day 4-round loop. Do not mix scripts.
C, C++, Java, and Python are the usual set. Confirm on the invite. Do not switch the week of the drive.
All three care about DSA and integrity. Capital One India loops often emphasise product-fintech vocabulary (ledger, rate limits, SQL) and a 7.5 academic floor, with Bengaluru/Hyderabad hubs. Superday/Power Day branding differs by firm - prep DSA once; customise domain stories.
For campus SWE, DSA + OA mocks + one strong project beat certificate stacks. See certifications.
Bank solvable OA problems first, keep an error log, and rehearse one ledger or rate-limiter explanation out loud. If you have two OAs, write down OA2 - the live round may replay it. Correctness under time beats a half-finished clever solution.
Start with Capital One interview experience on this site, then cross-check recent community write-ups for India vs US. Patterns shift - use them as maps, not scripts.
Profile patterns that got selected: B.Tech CSE/IT/ECE, often ~8.0 CGPA in write-ups (floor 7.5), tier-2 mix, one internship or a strong project, steady DSA.
Online assessment: Timed coding on HackerRank or similar. Clean, fully passing solutions beat partial cleverness. Shortlist mail often arrived in a few days.
Technical rounds: Design an LRU cache (HashMap + doubly linked list), implement a rate limiter (sliding window / token bucket), merge overlapping intervals. Domain chat around credit-risk basics and SQL - plain explanations worked better than buzzwords. Project deep dive: stack, hardest bug, what you would rebuild. Later rounds leaned Java: APIs, data choices, failure modes.
HR / managerial: Why fintech / payments? A production bug or outage? Integrity under pressure? Keep answers short: situation → what you did → result.
Takeaway: clear DSA plus a coherent ledger story beats a high CGPA with weak explanation.
What hurt other candidates: coding before clarifying constraints; treating HR as a formality; system-design jargon without a bottleneck; freezing on “what if the credit leg fails?”
An India Capital One SDE fresher candidate reported two online assessments before a live technical: OA1 was 120 minutes with three DSA problems; OA2 was 45 minutes with Weighted Job Scheduling plus a Slack-like threading system-design section (Interview Experiences). They noted: “The Technical Round, lasting 70-80 minutes, was entirely based on my performance in Online Assessment 2,” revisiting DSA approach and ER/API design before rejection.
If your invite has two OAs, treat OA2 as interview homework - rewrite the solution the same evening.
A Capital One Senior SWE (Full Stack, US) candidate dated 1 May 2025 described recruiter phone screen → CodeSignal OA (4 questions / 70 minutes) → Power Day of 4 separate interviews, then a same-next-business-day do-not-reply rejection (Jointaro). Freshers should not copy senior system-design depth blindly - the transferable signal is stamina across multiple interviews and passing tests on the platform they name.
More fresher narratives: Capital One interview experience.
JP Morgan · Goldman Sachs · Bank of America · Wells Fargo · HSBC · Barclays