Goldman Sachs Analyst vs Associate vs VP Engineering Interview: What Each Level Is Tested On (Prep Checklist)

At a bank, titles sound senior early. "Vice President" is a senior engineer title, not a boss, and each title is interviewed differently.

This page is a simple checklist: find your level, tick the boxes, and practise with the free links in each section.

Pay at Each Goldman Sachs Title (India)

Medians from levels.fyi for Goldman Sachs Software Engineer, India (page updated 6 Nov 2026). "Total pay" means base + stock + bonus, per year. Your offer can be higher or lower by team, city and bonus.

Why this matters: the VP title pays about 2× an Analyst, but Associate to Analyst is only about 1.2×. If you prepare for a VP role the way you'd prepare for Associate, you may be offered the lower title, a median gap of about ₹27 L a year. And "VP" here means a senior engineer, not someone who manages a department.

How the Goldman Sachs Interview Loop Works

• Online test: usually a timed test on HackerRank (a coding site), often 2–3 coding problems. Some teams use a recorded video interview (HireVue) instead.
• Live coding: a video call on CoderPad (a shared online editor where your code actually runs). The interviewer watches you type, so the code has to work.
• The Superday: usually 3–5 interviews in one day, back to back, about 45–60 minutes each. It often mixes data structures and algorithms, a high-level design round with a finance flavour, questions on how you build and ship software, behavioural questions tied to Goldman's Business Principles, and a deep dive on your resume.
• After that: team-fit chats and, often, a short chat with a Managing Director.
• Goldman has no Leadership Principles list like Amazon. Expect plain behavioural questions instead.

This comes from candidate reports and prep guides, not from Goldman. Rounds vary by team and level. The split by title below is our best reading of one shared loop, not a published rule.

Start here on InterviewSkool:

• A step-by-step prep planner built around your dates (sign in first)
• Why this company? Practise the answer

Analyst Checklist: Coding That Runs

What they check: can you solve data structure problems and make the code really run, while explaining your thinking? Usually the online test, a live CoderPad round, then a Superday that is mostly coding plus a deep dive on your resume.

• I can solve medium problems on arrays, strings, hash maps, sliding window, BFS/DFS and trees in about 30 minutes.
• I can finish 2–3 problems in a timed online test without hints, and I read the full question before I start.
• In a live editor I get the code to run and pass, not just look right on paper.
• I talk out loud: my idea, the time/space cost, then code. No silent typing.
• I test my own code with a small example and an edge case (empty input, one element, duplicates).
• I can explain every project on my resume: what it did, what I built, and what I'd change. Some tests also add aptitude or maths questions.

Practise on InterviewSkool (free):

• 39 coding questions reported from Goldman Sachs interviews (6 easy, 27 medium, 6 hard), free to browse
• Full DSA problem list by topic
• Topic guides: arrays & strings · hash maps · sliding window · BFS vs DFS · trees & graphs · two pointers · dynamic programming
• Your intro answer: tell me about yourself

Red flag: code that looks fine but fails on the first run, or "I'll just code it" with no plan and 10 minutes of silent typing.

Associate Checklist: Coding Plus a Design Round

What they check: everything from Analyst, plus (usually) a high-level design round, often with a finance flavour, and questions on how you build and ship software.

• All the Analyst boxes above, done faster, with fewer hints.
• In a design round I can: list requirements → estimate numbers (users, requests per second, storage) → draw a simple design → go deep on the hardest part.
• I can sketch a trading-style flow: orders → queue → matching → trades, and say what must never be lost or counted twice.
• I can design the APIs and the data model (tables, keys, which database and why).
• I know when to use a cache, a queue, sharding (splitting data across many databases) and a load balancer, and what each one costs you.
• I can talk about software practice: testing, code review, releases, and how I find and fix a bug in a live system.

Practise on InterviewSkool (free):

• 8 system design problems reported from Goldman Sachs interviews (Sep 2025 – Sep 2026), each with a full solution
• Finance-flavoured case studies: stock trading platform · payment system · account balance ledger · stock price alerts · notification service (all in the case study library)
• The building blocks: what is system design · caching · message queues · sharding · SQL vs NoSQL

Red flag: naming tools ("Kafka, Redis") without saying why. Or a trading design that never says what happens if the same order arrives twice.

VP Checklist: Judgment

What they check: not more buzzwords, but better judgment. Bigger designs, deeper trade-offs, and stories about leading a team and owning production. Often a short chat with a Managing Director at the end (usually about big-picture thinking and career goals).

• All the Associate boxes above, with less prompting from the interviewer.
• For every big choice I give 2 options, a reason, and what could go wrong (speed vs safety, cost vs scale).
• I can design for money-grade correctness: no lost or double-counted trades or payments, safe retries, audit trails.
• I can explain how the system fails and recovers: a node dies, a market-data feed lags, a deploy goes wrong.
• I have stories where I led others: set the plan, got people to agree, and handled a production problem end to end.
• I can say what I'd do in my first 90 days and where I want my career to go (for the Managing Director chat).

Practise on InterviewSkool (free):

• Harder money-and-data case studies: portfolio management system · market data VWAP · credit card authorization · idempotency (duplicate requests)
• Trade-offs and big ideas: CAP theorem · consistent hashing · rate limiting · load balancing
• Leadership stories: showing leadership · tell me about a time

Red flag: a neat diagram with no trade-offs, or stories where you only did your own tasks well. At VP that can read like a strong Associate.

Your Behavioural Story Bank

Write 5–7 stories and reuse them. Goldman has no Leadership Principles list, but behavioural rounds are often tied to its Business Principles, so expect themes like the ones below. Each story should fit the STAR shape: Situation → Task → Action (what you did) → Result (with a number). Pick the right size of story for your level.

Full guides: common behavioral questions · tell me about yourself · why this company

Quick Self-Check: Which Title Are You Ready For?

If you can't tick every must for the title you're applying to, that's your prep list. Go back to that level's section above.

A Simple 4-Week Plan

Want a plan built around your own dates and weak spots? Sign in first, then use the InterviewSkool prep planner.

Test Yourself at Your Level Before Goldman Sachs Does

The fastest way to find out which title you're ready for is a real practice interview. On InterviewSkool you can do a mock interview with Alex, our AI interviewer: coding mocks, and system design mocks at SDE-2, SDE-3 or Staff level, with a score out of 100 and feedback on exactly what is holding you back. Your first demo interview is free. Goldman Sachs questions: coding · system design

Pay figures are levels.fyi medians for Goldman Sachs Software Engineer, India (page updated 6 Nov 2026) and change over time. Years of experience are levels.fyi's typical ranges. Loops vary by team and level, and the split by title is inferred from one shared loop described in candidate reports. InterviewSkool is not affiliated with Goldman Sachs, and this is not an official Goldman Sachs document.