Interview Guide

Capital One Data Engineer Interview (L4)

At Capital One, the (L4) Data Engineer interview is characterized by Bank-meets-tech culture with heavy data focus and machine-learning-first product framing. To clear this bar you need shipped production pipelines end-to-end and can debug them when they break, built on 2-5 years of production DE work.

Compensation

$150K–$185K base • $210K–$300K total

Loop duration

3.8 hours onsite

Rounds

5 rounds

Location

McLean VA, NYC, Plano TX, Richmond VA, Chicago, San Francisco

Compensation

Capital One Data Engineer total comp

Across 81 samples

Offer-report aggregate, 2018-2026. Level mapped: L4. Typical experience: 4-9 years (median 7).

25th percentile

$125K

Median total comp

$175K

75th percentile

$199K

Median base salary

$160K

Median annual equity

$21K

Median total comp by year

2018
$150K n=3
2022
$201K n=3
2025
$135K n=20
2026
$182K n=44

Tech stack

What Capital One data engineers actually use

Across 15 open roles

Frequency of each tool across Capital One's open data engineer DE postings. The ones with interview prep pages are live links.

Warehouse / SQL
Cassandra
DynamoDB
MongoDB
Redshift
Orchestration
Dagster
Airflow
Compute
Spark
Databricks
EMR
Cloud
AWS
Azure
GCP
Other
Glue
Monte Carlo
Updated from current job listings
Prepare for the interview
01 / Open invite
02min.

Walk into Capital One knowing the Python pattern they'll test.

a Capital One Python query, the same shape a screen would give you.
The diff against expected. Where ties broke. What you missed.
sandbox
1def sessionize(events):
2 sessions = []
3 for e in events:
4 if gap_minutes(e) > 30:
5
Execute your solution0.4s avg.
Capital OneInterview question
Solve a Capital One problem

Round focus

Domain concentration by round

Across 15 job descriptions

Capital One's round-by-round focus, inferred from 15 active data engineer job descriptions. Use this to calibrate which domains to drill for each round.

Online Assessment

Python92%
SQL34%
Architecture8%
Spark8%
Modeling4%

Phone Screen

Python71%
SQL55%
Architecture31%
Spark13%
Modeling6%

Onsite Loop

Architecture58%
Python28%
Modeling27%
SQL26%
Spark11%

Practice problems

Capital One data engineer practice set

4 problems

Capital One-tagged practice problems for the data engineer level. Click any to start practicing.

SQLmedium~18 min

Spending by Account Status

We're segmenting the platform's users by account status to see how revenue splits across them, and each status should count all of its users, even the ones who have never made a transaction. For each status with more than 50 transactions, show the transaction count, the number of unique users, and the total revenue, from highest revenue down.

Open in practice environment→
Pythoneasy~10 min

The Single Bit

Given an integer, return True if it is a positive power of 2 (1, 2, 4, 8, 16, ...). Use bitwise operations: (n > 0) AND (n & (n - 1)) == 0.

Open in practice environment→
Modelingmedium~25 min

The Float

A card issuer needs a warehouse that reconciles what a cardholder can spend right now against what has actually posted to their account. Every swipe creates a temporary hold that later settles, often for a different amount and sometimes never, and a cardholder can dispute a charge after it posts. Model the schema that supports available-credit checks, statement generation, and dispute tracking across accounts that each belong to a customer.

Open in practice environment→
SQLmedium~30 min

The Steady Few

An SRE team is compiling a reliability leaderboard by region, where a probe's effective hours is its uptime minus a tenth of its latency, and a probe with no recorded latency counts as having zero latency. Total each region's effective hours and stand up the three most reliable regions, most reliable first, with equal totals sharing a place.

Open in practice environment→
Prepare for the interview
03 / Real question02 of many
02hand-picked.

The Single Bit

Easy10 min

One particular pattern hides in plain sight.

Pulled from debriefs where Python parsing was the gate.

Daily signup-to-purchase funnel

Count signups and first-time purchases per day. Product-company favorite.

WITH first_purchase AS (
SELECT
user_id,
MIN(event_date) AS first_purchase_date
FROM events
WHERE event_type = 'purchase'
GROUP BY user_id
)
SELECT
e.event_date AS day,
COUNT(*) FILTER (
WHERE e.event_type = 'signup'
) AS signups,
COUNT(*) FILTER (
WHERE e.event_type = 'purchase'
AND e.event_date = fp.first_purchase_date
) AS first_purchases
FROM events AS e
LEFT JOIN first_purchase AS fp
ON e.user_id = fp.user_id
GROUP BY e.event_date
ORDER BY e.event_date

The loop

How the interview actually runs

01Recruiter screen

30 min

Capital One's DE pipeline is unusually formal. They run extensive screening and standardized assessments. Tracks: Card, Banking, Commercial, Tech Platform, Enterprise Data.

  • →Online assessment is common; practice timed SQL + case-study exercises
  • →Capital One moved heavily to AWS; cloud-native experience helps
  • →Their data-ML focus is genuine; ML-adjacent experience is valued

02Case study (take-home)

Multi-hour

Capital One is known for case studies. Business problem with data; you solve it. Think: how to segment cardholders for a retention campaign, or optimize an application funnel.

  • →Show business reasoning, not just SQL
  • →Address assumptions explicitly
  • →Metric definition often matters more than the final number

03Technical phone screen

60 min

SQL + Python with banking / card-payments flavor. Fraud, credit risk, marketing-mix problems appear often.

  • →Practice cohort analysis SQL (approval rate by month of origination)
  • →Know basic credit concepts: APR, delinquency, charge-off
  • →Python problems focus on data manipulation, not algorithms

04Onsite: case + business analysis

60 min

Second case study, this time whiteboard with an interviewer. Business framing plus technical implementation.

  • →Speak in metrics and experiments
  • →Acknowledge regulatory constraints (Fair Lending, CCPA)
  • →Conclude with a measurable recommendation, not just analysis

Level bar

What Capital One expects at L4 Data Engineer

Pipeline ownership

Mid-level DEs own pipelines end-to-end. Interviewers expect stories about designing, deploying, and maintaining a data pipeline that has been in production for 6+ months.

SQL + Python or Spark fluency

SQL is the floor. Most teams also expect fluency in either Python for data manipulation (pandas, airflow DAGs) or Spark for larger-scale processing.

On-call debugging

You should have concrete stories about production incidents: what alert fired, how you diagnosed, what you fixed, and what post-mortem action you owned.

Capital One-specific emphasis

Capital One's loop is characterized by: Bank-meets-tech culture with heavy data focus and machine-learning-first product framing. Calibrate your preparation to that, generic FAANG prep will not close the gap on company-specific expectations.

Behavioral

How Capital One frames behavioral rounds

Excellence

Capital One's stated #1 value. Craftsmanship of analytical work matters.

“Describe a piece of analysis you're most proud of.”

Do the right thing

Banking regulation forces ethical attentiveness. Engineers who don't get this fail.

“Tell me about a time you flagged a risk others had missed.”

Deliver what matters

Capital One measures outcomes. Activity without outcome doesn't impress.

“Give me the outcome number from your last major project.”

Work well together

DE at Capital One is matrix-organized. Collaboration across business, tech, and risk is constant.

“Describe collaborating with a credit-risk or compliance partner.”

Prep timeline

Week-by-week preparation plan

8-10 weeks out
01

Foundations and gap analysis

  • ·Do 10 medium SQL problems. Note which patterns feel slow
  • ·Write out 2-3 behavioral stories per value, Capital One weights this round heavily
  • ·Read Capital One's public engineering blog for recent architecture patterns
  • ·Review your prior production work, pick 3-5 projects you can discuss in depth
6 weeks out
02

SQL and coding fluency

  • ·Practice window functions until DENSE_RANK, ROW_NUMBER, LAG, LEAD are reflex
  • ·Do 20+ Capital One-style problems in their domain
  • ·Time yourself: 25 min per medium, 35 min per hard
  • ·Record yourself narrating your approach aloud. Interviewers weigh how you explain it, not only what you write
4 weeks out
03

Pipeline awareness and behavioral depth

  • ·Review pipeline architecture basics: idempotency, partitioning, backfill
  • ·Practice explaining a pipeline you've worked on end-to-end in 5 minutes
  • ·Refine behavioral stories based on mock feedback
  • ·Do 10 more SQL problems at medium difficulty
2 weeks out
04

Behavioral polish and mock loops

  • ·Rehearse every story out loud. Cut to 2-3 minutes each
  • ·Run 2 full mock loops with a mid-level DE or coach
  • ·Identify your 3 weakest behavioral areas and draft additional stories
  • ·Review recent Capital One news or earnings call for fresh talking points
Week of
05

Taper and logistics

  • ·No new content. Review your notes only
  • ·Sleep. Mental energy matters more than one more practice problem
  • ·Confirm logistics: laptop charged, shared-doc tool tested, snack and water nearby
  • ·Remember: interviewers want to find reasons to hire you, not to reject you

FAQ

Common questions

What level is Data Engineer at Capital One?
On Capital One's ladder, Data Engineer sits at L4. Expectations center on shipped production pipelines end-to-end and can debug them when they break.
How much does a Capital One Data Engineer make?
Across 81 offer samples from 2018-2026, Capital One Data Engineer total compensation lands at $125K (P25), $175K (median), and $199K (P75), median base $160K and median annual equity $21K. Typical experience range: 4-9 years..
How is the Data Engineer loop different from other levels at Capital One?
Round structure is shared across levels; what changes is what each round tests. For Data Engineer the emphasis is shipped production pipelines end-to-end and can debug them when they break, with particular attention to production pipeline ownership and on-call debugging.
How long should I prepare for the Capital One Data Engineer interview?
6-8 weeks of focused prep is typical for candidates already working as a DE. Less than 4 weeks is tight; the behavioral story bank usually takes longer than candidates expect.
Does Capital One interview data engineers differently than software engineers?
Yes. DE loops at Capital One weight SQL heavier, include pipeline/system-design rounds tuned to data workloads, and probe for production data experience (ingestion patterns, data quality, backfill) that generalist SWE loops skip.