Goldman Sachs Phone Screen: What It Covers, How It's Scored, and How to Pass
- Goldman Sachs phone screen is three separate filters: a HackerRank OA, a HireVue video interview, and a live CoderPad coding session — all before the Superday.
- The HackerRank OA targets medium-difficulty DSA across five pattern families: arrays, two pointers, sliding window, graph traversal, and dynamic programming.
- HireVue uses AI scoring on structure and verbal clarity; rambling answers score worse even when the underlying story is strong.
- CoderPad problems are medium LeetCode difficulty; Goldman engineers score on approach discussion, complexity analysis, and self-testing, not just working code.
- Finance-flavored problem framing is a Goldman-specific wrinkle — the DSA pattern underneath is standard, but the setup involving prices or transactions can mislead you.
- The process runs two to four months from application to Superday; align your prep intensity to the actual timeline so you don't peak too early.
Goldman Sachs moves slowly. You apply, you wait a month, you do a video screen, you wait another month, and then, if you're still standing, a senior engineer calls you on CoderPad and asks you to write code. The Goldman Sachs phone screen isn't one thing. It's a three-stage filter, and most candidates don't realize that until they're already in the middle of it.
This guide breaks down every stage, what each one tests, and what you need to do to get through.
Three Screens, Not One
Most companies run a single technical phone screen before the onsite. Goldman Sachs runs three separate filters before the Superday:
| Stage | Format | Duration | Who scores |
|---|---|---|---|
| HackerRank OA | 2-3 DSA problems + MCQs | 60-120 min | Automated |
| HireVue video | 5-8 behavioral questions, recorded | ~15 min | AI + recruiter |
| CoderPad screen | 2 live coding problems | 45-60 min | Senior engineer |
You have to clear all three to reach the onsite. Most candidates who fail do so at the HackerRank stage and never hear back. That silence is the rejection. Goldman won't tell you to your face. The inbox just stops.
Stage 1: The HackerRank Online Assessment
This is the gate most people don't treat seriously enough. The OA arrives one to two weeks after the application, and it's proctored.
Format: Two to three DSA problems, sometimes with multiple-choice questions. You get 60 to 120 minutes depending on the role and region.
Difficulty sits in the medium LeetCode range, with the occasional easy problem. Goldman's OA isn't trying to trick you with hard problems. It's filtering out candidates who haven't put in foundational work. Think of it less as a test and more as a "did you actually prepare, or did you just have a great resume and a lot of confidence?" checkpoint. Common patterns:
- Arrays and hash maps (frequency counting, prefix sums)
- Two pointers and sliding window
- Binary search
- Basic graph traversal (BFS, DFS)
- String manipulation
The biggest mistake is treating the OA as a warmup. A borderline OA performance gives recruiters an easy reason to stop the process. And they will take it.
Stage 2: The HireVue Video Interview
HireVue comes after the OA clears. You get a link, you open it, and you record yourself answering behavioral questions with no human on the other end. Just you, your webcam, and the cold, unblinking eye of an AI that is absolutely judging the hesitation in your voice.
Format: Five to eight pre-recorded questions. Thirty seconds to prep, two minutes to answer. Goldman's recruiters review the recordings, but the initial pass uses AI scoring on verbal communication, tone, and structure.
The questions are standard: tell me about working under pressure, describe a disagreement with a teammate, why Goldman. Nothing exotic. The format is the weird part.
Two things matter that candidates underestimate. Structure your answers clearly. The AI scoring responds to organized, complete responses. Rambling answers score worse even if the underlying story is strong. Second, answer directly. The 30-second prep time is enough to pick a story and decide your opening line. Use it. Don't spend it staring into the middle distance while the timer quietly ruins you.
The behavioral substance is covered in the Goldman Sachs behavioral interview guide, which walks through the themes Goldman actually probes. For HireVue specifically, your job is to not be vague.
Stage 3: The CoderPad Technical Screen
This is the interview people mean when they say "Goldman Sachs phone screen." A 45 to 60 minute live session with a senior Goldman engineer on CoderPad. Shared browser-based editor, code that executes, real-time conversation.
You'll get two problems. Both will be medium difficulty.
The format is consistent across Goldman roles. The interviewer watches you code, asks follow-up questions, and submits an independent scorecard after the call. They are taking notes. The whole time. Even the moments you think are fine.
What Actually Gets Asked
Goldman's CoderPad problems cluster around five pattern families consistently enough that you can prep for them specifically.
Two pointers and sliding window show up constantly. Expect problems about subarrays, windows, or contiguous segments with some property. If you find yourself writing a nested loop, stop and ask whether a window applies. A O(n²) solution to a sliding window problem is the algorithmic equivalent of bringing a fax machine to a sprint planning meeting.
Dynamic programming at the medium level is common. Not the hard variant where you invent state from scratch, but problems like coin change, climbing stairs with constraints, or grid path optimization. Goldman likes problems with an obvious recursive solution where you're expected to memoize or convert to tabulation. The dynamic programming framework is worth reviewing before this screen.
Graph traversal appears regularly: connected components, shortest paths, island-counting variants. BFS and DFS both show up. Union-Find occasionally.
Hash maps and frequency counting come up more than you'd expect for a bank. Two-sum style, anagram detection, first unique character.
Finance-flavored problems are a Goldman-specific wrinkle. The problem setup sometimes involves prices, transactions, or profit windows. The DSA pattern underneath is standard, but the framing can throw you. Candidates see "buy and sell stock" and their brain goes "finance problem" instead of "sliding window." Read the problem carefully before assuming you know the pattern.
How Goldman Actually Scores You
Goldman engineers use structured scorecards. They're evaluating four things simultaneously, and correctness is only one of them.
Correctness is necessary but not sufficient. Working code that handles edge cases gets you in the door. It doesn't get you through. Candidates who only solve the problem and say nothing memorable rarely advance.
Talk through your approach before you write the first line. Not a long monologue, but a 30-second sketch: here's the pattern I'm seeing, here's my approach, let me check if that makes sense. Then code. Goldman operates across global markets with tight coordination requirements. They're evaluating whether you can explain a complex idea clearly under pressure. If you can't narrate a sliding window to one person in a quiet room, that's a signal.
Efficiency matters, and they'll ask about it explicitly. When you finish, expect: "What's the time and space complexity?" Then: "Can we do better?" If your first solution is O(n²) and a linear approach exists, the interviewer wants to see whether you can find it unprompted.
The interviewer is specifically watching for how you handle the moment you get stuck. Going silent is wrong. Articulating what you know and what you're unsure about is right. Goldman wants calibrated thinking, not performance confidence. "I'm not sure, let me think out loud" is genuinely better than 90 seconds of staring at the screen while the interviewer slowly fills in their scorecard.
Edge cases matter. Before you say you're done, test against empty input, single-element cases, and any negative numbers or overflow scenarios the problem implies. Interviewers notice when you do this without being prompted.
What Interviewers Are Not Looking For
A few behaviors consistently hurt candidates in Goldman CoderPad screens.
Jumping to code without discussing the approach. Goldman interviewers penalize this specifically. Take 60 seconds to talk through the problem before writing anything. It earns more credit than it costs time.
Silence when stuck. If you don't know how to proceed, say what you do know. "I see that we need to track frequency, I'm thinking a hash map, but I'm not sure how to handle the ordering constraint." That's useful. Ninety seconds of staring is not. It reads as "I give up" when the interviewer still has 40 minutes on the clock.
Over-engineering the solution. Medium problems have clean solutions. If you're building elaborate abstractions or writing 80 lines for a sliding window problem, step back. Goldman interviewers respect simplicity. A five-line solution that works beats a 40-line solution that almost works.
Declaring done without testing. Walk through your code on the provided example. Then invent your own edge case and trace through it. Interviewers explicitly reward self-testing. It signals you'd catch bugs before code review, which is the entire reason anyone gets hired.
How to Prepare for the Goldman Sachs Phone Screen
For the HackerRank OA: solve two to three medium problems per day for two weeks before your expected OA date. Focus on the five pattern families above. Practice under timed conditions. The OA clock creates pressure that casual practice doesn't, and "I'd get this if I had more time" is not a passing grade.
For the HireVue: prepare three to four behavioral stories using the STAR structure. Record yourself on your laptop camera and watch the playback once. You'll see immediately whether you're meandering or being direct. It's uncomfortable. Do it anyway.
For the CoderPad screen: practice narrating while you code. This sounds simple and is genuinely hard. Most engineers are accustomed to thinking silently. The CoderPad screen requires simultaneous thinking and talking, and you can't train that by solving problems alone in a browser tab. The best way to train it is mock interviews with a live listener. SpaceComplexity runs voice-based mock interviews with rubric scoring built for exactly this kind of practice. If you go quiet under pressure, that's the gap to close before the real call.
Time your prep to the Goldman timeline. The process is slow. If you applied and haven't heard about the OA yet, use that time for deep-dive pattern work.
The Timeline Reality
Goldman is one of the slowest-moving interviewers in the industry. Candidates regularly report two to four months between application and Superday.
A rough actual sequence based on recent reports: application, then two to three weeks for the OA invitation, one to two weeks after OA for HireVue, two to four weeks after HireVue for the CoderPad screen, one to two weeks after CoderPad for a Superday invite or rejection.
If you're interviewing with Goldman in parallel with other companies, align your prep intensity to this schedule. Don't peak too early. Don't burn out in week three when you've still got eight more weeks of waiting left. Goldman will get to you eventually. It just moves at Goldman speed.