Goldman Sachs Staff Data Engineer Interview (L6)
Goldman Sachs (L6) Staff Data Engineer loop: Investment-bank rigor with Marcus/transaction-banking modernization and strats/quant culture. Bar at this level: organizational impact beyond a single team and tech strategy ownership. Typical 8-12 years of data engineering experience.
Compensation
$230K–$290K base • $470K–$660K total
Loop duration
4 hours onsite
Rounds
5 rounds
Location
New York, Dallas, Salt Lake City, London, Bangalore
Tech stack
What Goldman Sachs staff data engineers actually use
These are the tools that show up in Goldman Sachs's DE job descriptions right now. Click any chip to drop into an interview prep page for it.
Round focus
Domain concentration by round
Where each domain tends to come up in Goldman Sachs's loop, derived from 10 current staff data engineer job descriptions. Longer bars mean heavier weight.
Online Assessment
Phone Screen
Onsite Loop
Walk into Goldman Sachs knowing the Python pattern they'll test.
Practice problems
Goldman Sachs staff data engineer practice set
Interview problems predicted for Goldman Sachs staff data engineers based on their actual job descriptions. Click any problem to work it in a live coding environment.
Full Customer Order List
Return first_name, last_name, and country for every customer in customers. Sort alphabetically by first_name, then last_name.
The Repeat Offenders
Given a list, return the values that appear more than once, each listed only once, in the order of their first appearance in the input.
High Volume Batch Jobs
Surface all batch jobs that processed more than 5000 rows, showing each job's name, priority, and rows processed, ranked from most to fewest.
The Word Inventory
Given a list of words, return a dict with two keys. 'counts' maps each word to its frequency. 'unique' is the sorted list of words that appear exactly once.
Top 2 sellers by revenue in each marketplace
Classic DE round opener. Window function + partition. Edit to tweak the threshold.
The Parentheses Factory
Building balanced brackets is an art form.
Pulled from debriefs where Python parsing was the gate.
The loop
How the interview actually runs
01Recruiter screen
30 minGoldman is formal, traditional, and selective. DE hiring spans Engineering (platform), Strategists (quant-adjacent), and Marcus (consumer tech). Tracks differ materially.
- →Strats roles blend quant + engineering; coding interviews can be harder
- →Marcus is a modern tech stack inside a traditional bank
- →Dress formally; tone formally; Goldman is not casual
02Technical phone screen
60 minSQL + coding with finance-data flavor. Trade data, position reconciliation, risk calculations. Slang is specific; familiarize.
- →Trading-floor vocabulary: ticker, cusip, side (buy/sell), settlement date
- →SQL performance questions are common; Goldman cares about cost
- →Python round can test OO design for financial models
03Onsite: data architecture
60 minDesign a system supporting trading analytics, regulatory reporting (Dodd-Frank, MiFID II), or consumer banking analytics.
- →Regulatory reporting has extreme correctness requirements
- →Trading data has unique latency + consistency demands
- →Goldman's SecDB is the famous internal system; familiarity is a plus
04Architecture strategy
60 minAt staff level, system design expands to multi-system strategy: 'Design the data platform for a 500-person org' or 'We have 40 pipelines producing inconsistent output; how do you fix it?' The evaluator watches for whether you think about developer experience, tech-debt paydown, and multi-quarter roadmaps.
- →Talk about teams and processes, not just technology
- →Name the specific mechanisms you would create (code review standards, shared libraries, data contracts)
- →Be ready to defend why not to build something you would build at senior level
05Onsite: technical + culture
60 minRigorous technical deep-dive blended with Goldman's values interview. Expect high expectations for both.
- →Goldman's 14 Business Principles are actually referenced
- →Intellectual rigor and depth of reasoning are central
- →Don't pretend to know things you don't; Goldman interviewers catch it
Level bar
What Goldman Sachs expects at Staff Data Engineer
Technical strategy ownership
Staff DEs set technical direction for multiple teams. Interviewers ask 'What tech decisions have you influenced across your org?' and probe depth: how did you socialize it, who pushed back, what trade-offs did you accept?
Multi-system design
Staff-level design is not one pipeline; it is the platform that 10 pipelines run on. Think data contracts, metadata stores, standardized ingestion patterns, shared orchestration, and the tradeoffs between standardization and team autonomy.
Tech-debt and migration leadership
Stories about leading a multi-quarter migration: the plan, the phasing, the stakeholder management, the rollback criteria. Staff DEs are expected to have shipped at least one such effort.
Mentorship scale
At staff, mentorship goes beyond 1:1 coaching: you have influenced hiring rubrics, run tech talks, or built onboarding that accelerated new hires.
Goldman Sachs-specific emphasis
Goldman Sachs's loop is characterized by: Investment-bank rigor with Marcus/transaction-banking modernization and strats/quant culture. Calibrate your preparation to that, generic FAANG prep will not close the gap on company-specific expectations.
Behavioral
How Goldman Sachs frames behavioral rounds
Integrity
Banking integrity is existential. Goldman interviewers probe seriously.
Excellence
Goldman's brand depends on it. Sloppy work stands out negatively.
Client focus
Even for engineers, Goldman is client-first. Internal-only product mindset doesn't fit.
Partnership
Goldman's structure emphasizes cross-divisional collaboration. Solo operators fail.
Prep timeline
Week-by-week preparation plan
Foundations and gap analysis
- ·Do 10 medium SQL problems. Note which patterns feel slow
- ·Write out 2-3 behavioral stories per value, Goldman Sachs weights this round heavily
- ·Read Goldman Sachs's public engineering blog for recent architecture patterns
- ·Review your prior production work, pick 3-5 projects you can discuss in depth
SQL and coding fluency
- ·Practice window functions until DENSE_RANK, ROW_NUMBER, LAG, LEAD are reflex
- ·Do 20+ Goldman Sachs-style problems in their domain
- ·Time yourself: 25 min per medium, 35 min per hard
- ·Record yourself narrating approach aloud, communication is graded
Platform-level system design
- ·Design 3-5 multi-system platforms: metadata store, shared ingestion, governance layer
- ·Prepare 2-3 stories where you drove technical direction across teams
- ·Practice mock interviews with another staff+ engineer
- ·Review Goldman Sachs's publicly described platform work for recent architectural shifts
Behavioral polish and mock loops
- ·Rehearse every story out loud. Cut to 2-3 minutes each
- ·Run 2 full mock loops with a senior DE or coach
- ·Identify your 3 weakest behavioral areas and draft additional stories
- ·Review recent Goldman Sachs news or earnings call for fresh talking points
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: the loop is rooting for you to raise the bar, not to fail
See also
Adjacent guides to check
FAQ
Common questions
- What level is Staff Data Engineer at Goldman Sachs?
- At Goldman Sachs, Staff Data Engineer corresponds to the L6 level. The bar emphasizes organizational impact beyond a single team and tech strategy ownership without people-management responsibilities.
- How much does a Goldman Sachs Staff Data Engineer make?
- Total compensation for Goldman Sachs Staff Data Engineer ranges $230K–$290K base • $470K–$660K total. Ranges shift by team and negotiation.
- How is the Staff Data Engineer loop different from other levels at Goldman Sachs?
- The format of the loop matches other levels; difficulty and evaluation shift to organizational impact beyond a single team and tech strategy ownership, and questions at this level dig into multi-team technical strategy and platform thinking.
- How long should I prepare for the Goldman Sachs Staff Data Engineer interview?
- Most working DEs find 10-12 weeks is about right. The technical prep scales with experience; the behavioral story bank is where candidates underestimate time.
- Does Goldman Sachs interview data engineers differently than software engineers?
- Yes, the DE track at Goldman Sachs emphasizes SQL depth, warehouse and pipeline design, and real production data experience (late data, backfills, quality checks), which generalist SWE loops don't test.