Many Goldman Sachs HackerRank guides still describe a two-hour coding test followed by a one-hour math section. That is no longer the best default for 2026. Goldman Sachs' current official guide describes a shorter, role-based assessment with Software Fundamentals, Software Diagnostics, and an optional Math challenge.
The practical consequence is important: candidates who prepare only with LeetCode may be ready for the first section and underprepared for the repository-debugging task that follows. Start with Goldman Sachs Software Engineer questions, then use this guide to build a preparation plan around the current format.
Quick verdict
Prepare for the assessment named in your invitation, not an old universal blueprint. Goldman Sachs currently says all candidates complete a 30-minute Software Fundamentals challenge. Engineering candidates also complete a 45-minute Software Diagnostics challenge, while Quantitative Strategist candidates receive a 22-minute Math challenge.
| Question | Best current answer |
|---|---|
| Is Goldman Sachs using HackerRank? | Yes. Goldman Sachs says HackerRank is one of its tools for evaluating Engineering candidates. |
| What coding should I expect? | Data structures, algorithms, complexity, and a separate existing-codebase debugging exercise for Engineering roles. |
| Does everyone receive math? | No. Goldman Sachs currently associates the Math challenge with Quantitative Strategist applicants. |
| How long is the assessment? | 30 minutes for Software Fundamentals, 45 minutes for Software Diagnostics, and 22 minutes for Math when assigned. |
| What happens next? | Your result is reviewed with the rest of your application. Goldman Sachs says campus candidates should generally receive an update within three weeks. |
If you are specifically taking the India Summer Analyst campus assessment, read the separate Goldman Sachs Summer Analyst OA 2027 India guide. Current campus reports describe a different mix of coding and multiple-choice questions, so combining the two formats would create more confusion than clarity.
The 2026 Goldman Sachs HackerRank format
Goldman Sachs assigns challenge types based on role preferences. That means two candidates can apply to the same firm, receive HackerRank invitations, and still face different sections. Copy the exact job title, division, location, and assessment names from your invitation before comparing your test with another candidate's experience.
| Challenge | Who receives it | Official time | What it evaluates |
|---|---|---|---|
| Software Fundamentals | All candidates in the current technical-assessment flow | 30 minutes | Data structures, algorithms, time complexity, and space complexity |
| Software Diagnostics | Engineering applicants | 45 minutes | Reading an unfamiliar repository, debugging, tests, and targeted fixes |
| Math | Quantitative Strategist applicants | 22 minutes | Probability, statistics, calculus, and linear algebra |
Older candidate reports about 120-minute programming tests or 180-minute combined assessments may have been accurate for earlier applications. They are not stronger evidence than the firm's current instructions. Your invitation remains the final authority because Goldman Sachs can vary a test by role, region, and recruiting program.
Software Fundamentals: coding under a short timer
Thirty minutes changes the strategy. You do not have time for a long tour through several abandoned ideas. Your goal is to recognize the core data structure quickly, state the invariant, implement a clean solution, and protect enough time for edge cases.
Patterns worth prioritizing
Goldman Sachs question-bank records repeatedly reward strings, arrays, hash maps, grouping, ordered scans, and practical data-structure implementation. Review complexity before test day so you can reject an obviously quadratic solution when the constraints require a linear or sorting-based approach.
Do not mistake familiarity for readiness. A frequency-map problem can still fail because you return the value instead of its index, lose original order, mishandle duplicates, or divide averages incorrectly. Practice writing the final implementation in one pass, then test empty input, one element, all duplicates, and the largest plausible case.
How HackerRank scoring affects your strategy
HackerRank says coding submissions are evaluated against predefined test cases. Hidden tests can cover edge conditions, larger inputs, and complexity limits that are not visible in the examples. A sample-passing solution is therefore a checkpoint, not proof of completion.
When stuck, preserve working code and isolate the failure. Check input assumptions, integer boundaries, state reset between cases, and asymptotic complexity before rewriting the whole solution. A targeted repair is usually faster and easier to reason about than a nervous restart.
Software Diagnostics: the section old guides miss
The current Engineering assessment includes a 45-minute Software Diagnostics challenge. Goldman Sachs says candidates work inside an existing application built with Django, Node.js, or Spring Boot. The task is closer to real maintenance work than a blank-editor algorithm problem.
Practice the workflow from PracHub's existing codebase interview guide: reproduce the failure, map the smallest relevant execution path, form a testable hypothesis, make a narrow change, and rerun focused tests before the full suite.
Use the limited AI assistant with engineering judgment
Goldman Sachs says the diagnostics environment includes a limited AI assistant that can help with navigation, syntax, or problem-statement clarity, but will not provide the full solution. Treat it as a tool for reducing search cost, not a substitute for understanding the repository.
Ask bounded questions such as which file owns a route, where a model is validated, or how a framework command runs one test. Then inspect the suggested location, verify assumptions in code, and evaluate the diff yourself. A strong candidate can explain why the change fixes the root cause and what regression test proves it.
Math challenge: what Quantitative Strategist candidates should review
The 22-minute Math challenge is role-specific. Goldman Sachs lists probability, statistics, calculus, and linear algebra, which makes fast recognition and accurate computation more important than lengthy derivations.
For probability, review conditional probability, Bayes' rule, expectation, variance, independence, and common counting setups. For statistics, know distributions, covariance, correlation, estimation, and how sampling changes uncertainty. For linear algebra, practice matrices, vectors, rank, eigenvalues, and transformations. For calculus, refresh derivatives, gradients, optimization, and basic integrals.
Use a two-pass strategy. Answer direct questions first, mark calculations that require more work, and return with the remaining time. Estimate the expected scale before selecting an option; this catches sign errors and implausible magnitudes without repeating the entire calculation.
A timing plan that matches the current assessment
| Section | First pass | Build and verify | Final review |
|---|---|---|---|
| Software Fundamentals | 3-5 minutes to parse constraints and choose an approach | 18-20 minutes to implement and run tests | 5-7 minutes for hidden-test risks and complexity |
| Software Diagnostics | 7-10 minutes to reproduce and trace the failure | 22-27 minutes for the smallest defensible fix and focused tests | 8-10 minutes for regression checks and diff review |
| Math | 10-12 minutes for direct questions | 7-9 minutes for marked calculations | 2-3 minutes for signs, units, and unanswered items |
This is a practice allocation, not a Goldman Sachs rule. The screen timer and section behavior in your invitation control the real attempt. Use a full simulation before test day so the pacing feels routine rather than improvised.
Is the Goldman Sachs HackerRank proctored?
Goldman Sachs' public candidate guide does not promise one universal proctoring configuration. HackerRank supports multiple employer-configured integrity modes, including tab monitoring, full-screen enforcement, copy-paste restrictions, screenshots, screen sharing, webcam checks, and session replay.
That capability does not prove every Goldman Sachs assessment enables every feature. Read the onboarding screen and invitation carefully. If the test requests webcam, screen-sharing, single-monitor, or full-screen permissions, complete the environment check early. Do not use external resources, AI tools, overlays, or another device unless the written rules explicitly allow them.
What happens after the assessment?
Goldman Sachs says the assessment result is evaluated together with other application material and that campus candidates should receive an update within three weeks. A complete coding score is useful, but it does not erase resume fit, role preferences, eligibility, or recruiting capacity.
The firm's broader student process describes a roughly 30-minute video interview for selected applicants, followed by a Superday for candidates who advance. A campus Superday usually consists of two to five interviews depending on the division. Prepare for coding explanation, project depth, technical fundamentals, and behavioral judgment rather than waiting for the portal to change.
| After-test status | What it means | Best action |
|---|---|---|
| Submitted | The platform received your attempt; a hiring decision may not be ready. | Save confirmation and write a private debrief. |
| Under review | Your assessment and application may still be compared with the candidate pool. | Prepare for HireVue and technical follow-ups. |
| Video interview | You have advanced to a recorded first interview. | Rehearse concise project, motivation, teamwork, and judgment answers. |
| Superday | You are entering the final interview series for that process. | Practice technical explanation and behavioral and leadership questions. |
Practice with Goldman Sachs questions from PracHub
These question-bank records are useful practice, not predictions of your exact HackerRank. Each complete title in the first column links directly to the question and written solution.
| PracHub question | Practice focus | Why it helps |
|---|---|---|
| Count Segments and Optimize 3-Server Assignment | Ordered scans, constraints, and optimization | Builds fast problem classification and complexity reasoning. |
| Solve String and Hashmap Coding Tasks | Strings, maps, simulation, and edge cases | Trains compact multi-part implementation under time pressure. |
| Implement an Integer Hash Map | Data-structure design and collision handling | Forces you to connect API behavior with average-case complexity. |
| Implement a String Deque | State transitions and boundary conditions | Practices clean implementation and tests around empty and one-item states. |
A seven-day preparation plan
| Day | Focus | What to do |
|---|---|---|
| Day 1 | Format and baseline | Confirm your assigned sections, then complete one 30-minute coding simulation. |
| Day 2 | Strings and hash maps | Solve two linked PracHub questions and record every missed edge case. |
| Day 3 | Algorithms and complexity | Practice arrays, sorting, windows, and one optimization problem. |
| Day 4 | Repository debugging | Reproduce a bug in a small Django, Node.js, or Spring Boot project and add a regression test. |
| Day 5 | Math or role depth | Quant candidates review probability, statistics, calculus, and linear algebra; others deepen debugging practice. |
| Day 6 | Full simulation | Run the sections and timers listed in your invitation without unapproved resources. |
| Day 7 | Next-round readiness | Review logistics, prepare four interview stories, and stop heavy practice early. |
Frequently asked questions
Is the Goldman Sachs HackerRank still two coding questions in 120 minutes?
Do not assume so. Older reports describe that format, but Goldman Sachs' current guide lists a 30-minute Software Fundamentals challenge and a separate 45-minute Software Diagnostics challenge for Engineering candidates. Follow your invitation.
Does every Goldman Sachs candidate take the math section?
No. The current official guide links the Math challenge to Quantitative Strategist candidates. Its listed topics are probability, statistics, calculus, and linear algebra.
Can I choose Python, JavaScript, or Java for diagnostics?
Goldman Sachs says the existing application may use Django with Python, Node.js with JavaScript, or Spring Boot with Java. Your invitation and assessment environment determine which options are available to you.
Does passing every visible test guarantee an interview?
No. Hidden tests and code quality can affect the technical result, and Goldman Sachs says it evaluates the assessment with the rest of the application. A strong score improves your evidence; it is not an interview contract.
When should I expect a response?
Goldman Sachs currently says campus candidates should receive an update within three weeks. Check the candidate portal and use any timeline in your invitation before sending a concise follow-up.
Final takeaway
The 2026 Goldman Sachs HackerRank is no longer well described by one old coding-and-math template. Prepare for the section mix tied to your role: fast algorithmic reasoning, realistic repository diagnostics, and math only when assigned.
Use Goldman Sachs Software Engineer questions on PracHub to practice the coding patterns with written solutions, then add a repository-debugging simulation and next-round stories. That combination matches the current process far better than memorizing one candidate's past question set.
Sources and Further Reading
- Goldman Sachs: Your Guide to HackerRank Success
- Goldman Sachs: Student Recruiting Process
- Goldman Sachs: Careers in Engineering
- HackerRank: Test Cases in Coding Questions
- HackerRank: Test Integrity Modes
- Current Candidate Discussion: Software Fundamentals, Diagnostics, and Math
- Candidate Discussion: Earlier Combined Programming and Math Format
Research note: This guide was checked on August 22, 2026. Goldman Sachs can change challenge assignments, timing, and recruiting stages by role or region. Your invitation and onboarding screen control your assessment.
Originally published on PracHub.
Top comments (0)