Your Goldman Sachs Prep Plan

By now you have seen how the Goldman Sachs Engineering loop is built and how it is judged, so this lesson turns that into a plan you can run. The spine is steady across pathways: a HackerRank online assessment, a live CoderPad phone screen, then a Superday of roughly three back-to-back rounds on one day, scored per round and run as elimination. What varies is the coding surface you meet and how much weight design and behavioral carry, and both of those turn on your pathway and level. The plan below weights your time toward everyday medium coding, then toward the surface that is yours, and sizes design and behavioral to where you sit on the ladder.

The Goldman Sachs angle

Before you drill a single problem, settle which of Goldman's two coding surfaces you will really face, because they barely overlap. The US and experienced live rounds, the CoderPad screen and the Superday, are standard data-structures work: Trapping Rain Water, two Premium questions, interval scheduling, strings. The campus and India HackerRank assessment is a different animal. It leans on math and number theory, the Goldbach a Premium problem or Binet's Fibonacci formula or a digit-manipulation puzzle, and that flavor barely shows up in the live-round reports. Both are real Goldman surfaces, and preparing the wrong one is the most expensive mistake on this page. Read the interview process and leveling and how decisions are made first, so your pathway and level are clear, and with them the surface you should plan around.

The plan, phase by phase

Each phase carries one focus and a checkpoint that tells you when you have earned the next. A phase is a slice of your prep time, so the plan holds whether your runway is two months or one hard week. The proportions are the message. Everyday medium coding takes the largest single slice because it is the spine of the loop at every level, and the second-largest slice goes to whichever coding surface is yours. SQL, design, and behavioral follow, each scaled to your pathway. Do not step past a checkpoint until you can clear it cold.

To make the proportions concrete, picture a five-week runway whose first few days go to orientation and to settling your pathway and level, and with them your surface. Weeks one and two are the heart of it. Work the everyday medium families until you recognize a reskin on sight, with Trapping Rain Water, LRU, and a Premium question average problem drilled cold. Then spend a focused block on the surface that is yours, the math-leaning assessment or the live fix-and-extend screen. Week three sharpens SQL and, if your level calls for it, opens software design. Week four takes design proper to its follow-ups, again scaled to your level, and builds your STAR stories and a true answer to why Goldman. Save the last stretch for mock rounds and for shoring up whatever felt weakest. On a shorter runway you compress the same order without reordering it, because coding fluency and the right surface are the spine of this loop.

Why the phases are weighted this way

The weighting tracks where Goldman departs from a generic loop. Coding leads at every level, so a handful of recurring families drilled cold will carry more of the loop than a hundred hard puzzles will. The surface phase earns its own large slice because Goldman runs two nearly separate coding worlds and preparing the wrong one is quietly fatal. SQL sits higher than it would in most software guides because it shows up live and surprises people. Design sits low for most readers because it is level-gated, and behavioral carries real weight because a bank hires for judgment as much as for code.

The Goldman Sachs angle

Lean into the Goldman-specific coding tells. Trapping Rain Water is the single most recurring problem by a wide margin and is often paired one-easy-one-hard with a buy-and-sell-stock variation. Own both, and the escalation between one transaction and two. The finance flavor shows up again and again. Buy-and-sell-stock, transaction queues reskinned as LRU or a circular buffer, and a Premium question best-average-grade problem, which Goldman poses as name-and-grade aggregation, all fit the domain and all recur. A Premium question is the other repeat offender, and interviewers push you through more than one approach with complexity follow-ups, so knowing a single solution is not enough. Drill these named problems specifically, because they carry a real Goldman signature that a random medium set will miss.

The design round is the one most candidates misjudge, and it turns less on raw skill than on reading your own level correctly.

The Goldman Sachs angle

Software design at Goldman rewards calibration over volume. It is absent for interns, new grads and Analyst candidates, and appears from experienced and senior up as a single Superday round. Match your effort to your level instead of over-preparing a scale-a-planet script no one asks for. When it does appear it is lighter than a FAANG design round and often low-level or discussion-only, a trade-off you argue in plain terms with frequently no diagram required. The tilt is finance and systems. Think a real-time risk engine or order book, an external sort over more data than fits in memory, banking-module low-level design backed by design patterns, ACID, and JVM behavior. A grounded decision you can defend under questioning is what this round scores, well above a memorized reference architecture.

Behavioral is the last front, and at a bank it counts for more than a pure coding loop would give it.

The Goldman Sachs angle

The behavioral round is a conversation without a scorecard, and its Goldman edge is that values get tested through scenarios instead of recited. The relaxed SDLC-and-resume format hides real teeth. Expect the integrity dilemma about a client's confidential data, the teammate who takes credit, and technical trivia dropped mid-story. Prepare stories deep enough to survive follow-ups on how you debugged, logged, or made a system thread-safe. Integrity, teamwork, client focus, and quality of work are assessed implicitly, so meet them with real work rather than a values list. And treat the why-Goldman answer as load-bearing, since a bank reads commercial interest and judgment as part of the fit it is buying.

In the room

• Fix your pathway, level, and surface first, then let them set the depth. Campus and new-grad Analyst loops are lighter and coding-weighted; experienced, Associate, and VP loops add rounds and lean on design and past-project depth. A Goldman Vice President is a senior individual contributor, so read any title through its engineering grade.
• Give the largest single slice to everyday medium coding, and drill the Goldman signatures by name. Trapping Rain Water is the most recurring problem and often paired with a buy-and-sell-stock variation; two Premium questions, interval scheduling, first-non-repeating-character, and a Premium question best-average-grade problem all recur. Know a reskin on sight.
• Prepare only the coding surface that is genuinely yours. The campus and India HackerRank assessment is math and number-theory heavy, Goldbach primes, Binet's Fibonacci, digit manipulation; the US and experienced live screen is standard data structures, sometimes framed as fix-the-failing-tests. Drill the one that applies.
• Treat live SQL as a real round. Deleting duplicates, union or intersect with a source-tag column, top-three departments by average salary, and current salary for active employees recur, most often in DBMS-heavy loops. Write joins, group-by and dedup without notes.
• Scale design to your level, and bring real STAR depth with a true reason for Goldman. Design is absent for juniors and light and finance-flavored from senior up, so learn the risk-engine and external-sort shapes as your model. Behavioral is a conversation with teeth, where integrity, teamwork and client focus are tested through scenarios rather than by a scorecard.