Goldman Sachs HackerRank: Sections, Timing, and the AI Assistant

TL;DR: Goldman Sachs publishes its own guide to the HackerRank assessment for Engineering campus candidates. It lists three challenge types: Software Fundamentals (30 minutes, everyone), Software Diagnostics (45 minutes, Engineering roles, with a built-in "limited" AI assistant) and a 22-minute multiple-choice Math challenge for Quantitative Strategist applicants. Proctoring rules, cutoffs and question counts aren't stated anywhere official.

Source note: everything marked official comes from Goldman's Engineering Hub guide to HackerRank and its student application steps, both read on 2026-10-30. Anything else is candidate-reported and labeled that way.

Search for this assessment and you'll find a mix of 120-minute, two-question accounts and newer write-ups that describe something different. The official page reads like a format change, so the older numbers are the ones to be careful with.

What Goldman Itself Says

The guide says candidates "will be assigned technical challenge types based on their role preferences." Three exist:

• Software Fundamentals, 30 minutes, all candidates. Data structures and algorithms problems in the programming language of your choice.
• Software Diagnostics, 45 minutes, Engineering roles. You work inside an existing application built with Django (Python), Node.js (JavaScript) or Spring Boot (Java) and have to diagnose and resolve issues. That's a different skill from solving a blank-page algorithm problem.
• Math, 22 minutes, Quantitative Strategist roles. Multiple choice across probability, statistics, calculus and linear algebra.

On the application path, the student page puts the HackerRank at the first-interview step: a roughly 30-minute video interview, and "Engineering applicants will be asked to take a HackerRank assessment." The Superday is described as two to five interviews for campus hires depending on the division, and it names HireVue in that step.

After you finish, the guide says results are evaluated alongside the rest of your application material and you should hear from campus recruiting within three weeks.

The Software Diagnostics Section

This is the part most older guides don't mention, because it isn't in the 2021-era accounts.

The official wording: candidates "will have access to a built-in 'limited' AI assistant that will not provide the full solution but can help with UI navigation, syntax, or problem statement clarity." The preparation advice goes further: approach it "as you would on the job," using it to move faster while applying your own judgment to "evaluate, refine, and validate the final solution."

Two things worth reading carefully:

1. It's an assistant inside the test, not a general AI policy. The page doesn't say anything about outside tools. If you want the platform-level picture, our HackerRank detection explainer and the Google-during-HackerRank piece cover what the platform itself can observe.
2. "Limited" is the operative word. By Goldman's description it helps with navigation, syntax and clarifying the prompt, not with producing the fix. The skill being measured is reading unfamiliar code.

The prep list in the guide is concrete: understand unfamiliar code, debug, write tests and make targeted changes, "rather than building an application from scratch." If you've only ever practiced LeetCode-style problems, this is the gap. Pull a small Django, Express or Spring Boot project, introduce a bug, and fix it with a timer running.

What Isn't Stated Officially

I looked for these on both pages and didn't find them:

• Camera, screen or proctoring rules
• A pass mark or scoring formula
• How many questions each section has
• Whether the sections are one sitting or separate invitations
• The process for experienced (non-campus) hires

If you see a number for any of these online, it's coming from a candidate or a prep site, not from Goldman.

Candidate-Reported Details (Treat as Unconfirmed)

• Older formats. Guides and snippets quote a 120-minute coding plus 60-minute math format, a 135-minute five-section test, and 75 to 90 minute screens. These likely describe earlier cycles. The official 30/45/22 split is the current published one.
• Monitoring. One 2021 account mentions tab and webcam monitoring. HackerRank lets employers configure integrity settings, and a prep site notes that doesn't show Goldman turns them on. Assume you could be watched and plan for it, but don't state it as fact.
• HireVue. Reports describe 3 to 6 questions with a short per-answer cap and a prep window. One 2026 guide says the exact HireVue configuration Goldman uses isn't publicly confirmed. How HireVue handles screen recording is worth reading before that stage.
• Specific questions. A March 2026 candidate post describes an intern OA. It's one account, so I wouldn't prepare around its exact problems.

How to Prepare

1. Do HackerRank's own practice assessment first. The guide says to. It's the fastest way to get comfortable with the editor, test runner and language picker.
2. Time-box the fundamentals. Thirty minutes is tight. Practice reading a problem, choosing a data structure within a couple of minutes and getting a correct solution down before you optimize.
3. Practice inside someone else's code. For Engineering roles, 45 minutes in an unfamiliar Django, Node or Spring Boot app rewards reading the failing test first and making the smallest fix.
4. Decide how you'll use the built-in assistant. Ask it about syntax and what a requirement means. Check anything it suggests before submitting.
5. If you're a Quant Strategist applicant, drill multiple choice under time. Twenty-two minutes for probability, statistics, calculus and linear algebra leaves little room for slow arithmetic.
6. Read your invitation email for the real rules. It governs your test, not a blog post.

For the same kind of official-versus-reported breakdown on other employers, see Amazon's SDE online assessment and Capital One's CodeSignal and Power Day process.

---

Practicing the live part: a mock interview with follow-up questions is a good way to rehearse explaining your debugging aloud before the video stage. OA Copilot covers online assessments on HackerRank, CodeSignal and Codility, so read your assessment's rules before deciding how to use any tool.

FAQ

What is on the Goldman Sachs HackerRank assessment?

Per Goldman: a 30-minute Software Fundamentals challenge for everyone, a 45-minute Software Diagnostics challenge for Engineering roles, and a 22-minute math multiple-choice challenge for Quantitative Strategist roles.

How long is the Goldman Sachs HackerRank test?

Officially 30, 45 and 22 minutes by section, depending on your role. Longer figures in older guides are candidate reports of earlier formats. Goldman doesn't say whether the sections are taken together.

Is AI allowed on the Goldman Sachs HackerRank assessment?

Software Diagnostics includes a built-in "limited" assistant for navigation, syntax and clarifying the problem, and Goldman tells candidates to use it as they would on the job. Nothing official addresses outside tools.

Is the Goldman Sachs HackerRank proctored?

Not stated. Some candidate accounts mention monitoring, but those settings vary by employer. Check your invitation.

When do you hear back?

The guide says within three weeks from campus recruiting, with live status in the candidate portal.

When do you hear back after the Goldman Sachs HackerRank?

The guide says candidates should receive an update from campus recruiting within three weeks, and points to the candidate portal for live status.

---

Author · Alex Chen. Career consultant and former tech recruiter. Spent 5 years on the hiring side before switching to help candidates instead. Writes about real interview dynamics, not textbook advice.