Goldman Sachs HackerRank Assessment (2026): Format, Sections and How to Prepare

Goldman Sachs publishes a guide to its HackerRank test, and it is more specific than most employers. Everyone completes a 30-minute Software Fundamentals challenge (data structures and algorithms, any language). Engineering applicants also complete a 45-minute Software Diagnostics challenge: fix problems inside an existing Django, Node.js or Spring Boot application. Quantitative Strategist applicants add a 22-minute multiple-choice math challenge. Goldman says the result is evaluated along with your other application materials and that you should hear back from campus recruiting within three weeks.

That official description (from Goldman Sachs's Engineering Campus Recruiting guide, as of October 2026) differs from older third-party write-ups that describe a single longer test of two or three problems, so lead with your invitation and Goldman's page. For a broader view of the whole process see our Goldman Sachs interview guide and the Goldman Sachs coding patterns guide.

At a glance

Question	Answer (as of October 2026)
Platform	HackerRank
Software Fundamentals	30 minutes, data structures and algorithms, language of your choice. All candidates
Software Diagnostics	45 minutes, work inside an existing Django, Node.js or Spring Boot app. Engineering roles
Math challenge	22 minutes, multiple choice on probability, statistics, calculus and linear algebra. Quantitative Strategist roles
AI assistant	A built-in "limited" assistant in the diagnostics challenge. It will not provide the full solution
Score or cutoff	Not published
What next	Evaluated with your application; update from campus recruiting within three weeks
Proctoring	Not published by Goldman. HackerRank supports proctoring, which employers configure

The three challenge types

Software Fundamentals (30 minutes)

Goldman describes this as assessing "software engineering fundamentals through data structures and algorithms problems, using the programming language of their choice." Its preparation advice: review core computer science concepts such as data structures, algorithms, and time and space complexity. The guide does not state the number of problems, so do not assume one. Expect the classic HackerRank layout: a problem statement, a code editor, visible sample tests and hidden tests.

Software Diagnostics (45 minutes, engineering roles)

This is the part most generic guides miss. Candidates work within an existing application built using Django (Python), Node.js (JavaScript) or Spring Boot (Java) and diagnose and resolve issues in a realistic engineering environment. Goldman's advice: practise working in an existing codebase, focusing on understanding unfamiliar code, debugging issues, writing tests and making targeted changes rather than building an application from scratch.

During this challenge, Goldman says candidates have a built-in limited AI assistant that will not provide the full solution but can help with UI navigation, syntax or problem statement clarity. Goldman's guidance is to treat it as you would on the job: use it to speed up your work while applying your own judgment to evaluate, refine and validate the result. Use only the assistant provided in the test environment, and follow whatever rules your invitation states.

Math challenge (22 minutes, Quantitative Strategist roles)

Multiple-choice questions on probability, statistics, calculus and linear algebra. If your role is a strat position, this is a separate prep track.

What is asked: realistic example types

Goldman does not publish questions and the sets change, so these are examples of the kinds of work the sections point to, not actual questions.

Fundamentals:

• Array and string manipulation with hash maps (frequency counts, grouping, pairs)
• Sorting with custom ordering, intervals, and binary search
• Stacks, queues, and a graph or tree traversal
• Simple dynamic programming (1D)

Diagnostics (examples of tasks in an unfamiliar service):

• A failing endpoint where the bug is a wrong status code, a missing null check, or an off-by-one in pagination
• A test that fails because of an incorrect query filter or sort order
• A configuration or dependency problem that stops the app starting
• Adding a small guard or validation and a test that proves it

Math (examples): conditional probability, expected value, a limit or derivative, a matrix or eigenvalue basics, a basic distribution question.

Third-party sites describe different formats, such as longer tests with two or three coding problems or large multiple-choice sets, and some are for specific regions or older cycles. We cannot verify those, so we do not repeat their numbers.

How it is scored

Goldman does not publish a score threshold or weighting. HackerRank tests are typically auto-graded by hidden test cases, so partial credit is common. Goldman says results are evaluated with your other application material, which means the score is one input, not a pass line. Do not trust a number quoted online as "the Goldman cutoff".

Is the Goldman Sachs HackerRank test proctored?

Goldman has not published its proctoring settings. HackerRank's Proctor Mode documentation describes features employers can turn on, including flagging tab switches and full-screen exits, webcam presence checks, periodic screenshots and session replays. Whether any of those apply to your test is the employer's choice, so read the rules shown on your invitation and before the timer starts. Follow them, work in the single test window, and practise under the same conditions. See also are online assessments proctored.

What comes next

Goldman says candidates should expect an update from campus recruiting within three weeks, and you can check the candidate portal for status. Later stages are reported to include a technical screen and a Superday; details differ by team, region and level, and are covered in our Goldman Sachs interview guide. If you are applying for the summer analyst program see the 2027 summer analyst engineering guide, and for the India machine coding round see the machine coding guide.

Prep plan

7 days

Day	Focus
1	Take HackerRank's sample assessment to learn the interface. Hash maps, arrays, strings
2	Sorting, intervals, binary search. Timed: 2 problems in 30 minutes
3	Stacks, queues, trees, BFS and DFS
4	Diagnostics: clone a small Django, Express or Spring Boot sample app, break it, then find and fix bugs and add tests
5	Diagnostics again with a different stack, 45-minute timer, read the logs and stack traces first
6	Full dry run of fundamentals plus diagnostics back to back; strats add 22 minutes of timed math
7	Review misses, rest

3 days

Day 1: fundamentals timed sets. Day 2: diagnostics in the stack named in your invite (if you know it). Day 3: dry run and review.

The DSA Patterns Sheet and Goldman Sachs's company page cover the fundamentals patterns. The company kits are the deeper option.

Common mistakes

• Preparing only for algorithms. Engineering candidates who skip the diagnostics practice lose their biggest unknown.
• Writing new code instead of reading first. In an existing app, read the failing test and trace the path before changing anything.
• Using 25 of 30 minutes on one problem. Fundamentals is short. Get a working solution, then improve.
• Trusting the AI assistant blindly. It is limited by design, and you are responsible for verifying the fix.
• Not running the tests. In diagnostics, running the existing tests early tells you where to look.
• Poor setup. Test your connection, browser and any camera or screen requirements in advance.

Practising

HackerRank tests are silent, so practise timed and solo, then rehearse explaining your reasoning for the interviews. Thita's AI mock interview runs your code against test cases, asks follow-ups when your explanation is thin and ends with a written report. It is not a replica of HackerRank or Goldman's tests. The Starter plan is free. For more on the platform see LeetCode vs HackerRank, and for the equivalent bank test see the JP Morgan HackerRank guide.

FAQ

What is the Goldman Sachs HackerRank assessment?

It is the online test Goldman uses to assess Engineering candidates. According to Goldman, everyone takes a Software Fundamentals challenge, engineering applicants add Software Diagnostics, and strats add a math challenge.

How long is the Goldman Sachs HackerRank test?

Goldman lists 30 minutes for Software Fundamentals, 45 minutes for Software Diagnostics and 22 minutes for the math challenge. Total time depends on which challenges your role includes.

What questions are on the Goldman Sachs HackerRank test?

Fundamentals covers data structures and algorithms, and diagnostics covers fixing issues inside an existing Django, Node.js or Spring Boot application. Strat roles add multiple-choice math. Question banks are not published.

Is the Goldman Sachs HackerRank test proctored?

Goldman has not published its settings. HackerRank can proctor tests when employers enable it, so read the rules on your invite and follow them.

Can I use AI on the Goldman Sachs HackerRank?

Goldman says the diagnostics challenge includes a built-in limited AI assistant that will not give the full solution. Use only what the test environment provides and whatever your invitation allows.

What score do I need on the Goldman Sachs HackerRank?

Goldman has not published a cutoff. Results are evaluated with your other application materials.

How long until I hear back after the Goldman Sachs HackerRank?

Goldman's guide says you should receive an update from campus recruiting within three weeks, and you can check the candidate portal for status. Timelines for non-campus roles may differ.

Can I choose my programming language?

For Software Fundamentals Goldman says you can use the language of your choice. Diagnostics uses the stack of the application you are given (Python with Django, JavaScript with Node.js or Java with Spring Boot).

Is there a Goldman Sachs HackerRank test for non-engineering roles?

Goldman says HackerRank is used for Engineering. Reports for finance roles describe different assessments, so check your invitation.

Next steps

Take HackerRank's practice assessment, run timed fundamentals sets from the DSA Patterns Sheet, practise diagnostics in a real project, then rehearse with an AI mock interview. Then read the Goldman Sachs interview guide for the rounds ahead.

Sources: Goldman Sachs: Your Guide to HackerRank Success, HackerRank Proctor Mode documentation. Diagnostic task examples are illustrative, not reported questions.