Goldman Sachs Software Engineer Interview Guide

For campus applicants, the first interview is an approximately thirty-minute video interview conducted on HireVue. Candidates selected after HireVue are invited to Superday, a series of final-round interviews. For campus hires, Superday typically includes between two and five interviews, depending on the division, with a cross-section of people they could work with.

Engineering applicants are also asked to complete a HackerRank assessment. Use screen, coding, system design, behavioral, and onsite as preparation categories, not as names Goldman Sachs gives its rounds.

These are general Software Engineer interview practices, not a Goldman Sachs scoring guide.

• Screen: Explain your interest, experience, and project contributions with concise, direct examples.
• Coding: Clarify inputs, choose suitable data structures and algorithms, write readable code, test edge cases, and explain complexity.
• System design: Clarify requirements, define interfaces and data flows, identify failure cases, and compare tradeoffs.
• Behavioral: Use specific project evidence to demonstrate collaboration, conflict resolution, ownership, and learning.
• Onsite: Keep your technical reasoning and career narrative consistent while adapting the depth of each answer to the interviewer.

For Goldman Sachs engineering applicants, a named part of the process is the HackerRank assessment. Compared with preparation for nonengineering roles, Software Engineer preparation places more emphasis on producing executable code, analyzing efficiency, discussing architecture, and communicating technical decisions.

Other companies may split or combine these skill areas differently. Build reusable coding, design, and behavioral skills instead of memorizing a fixed sequence.

Goldman Sachs does not publish how long the process takes. The campus HireVue interview takes approximately thirty minutes. Superday typically contains between two and five interviews for campus hires, depending on the division.

For preparation, treat the challenge as breadth. Coding requires accurate reasoning and clean implementation, system design requires decisions under ambiguity, and behavioral answers require credible evidence of how you worked with others and took responsibility.

• Spoken responses: Rehearse concise explanations of your background, motivation, and strongest projects for the video format.
• Coding practice: Solve data structure and algorithm problems in an editor, narrate your reasoning, test edge cases, and review code quality.
• Design practice: Work from unclear requirements to a structured design, then explain interfaces, storage, scaling, reliability, and tradeoffs.
• Behavioral evidence: Prepare project stories that identify the situation, your decisions, collaboration, outcome, and lessons.
• Full rehearsal: Combine technical and behavioral practice in a mock interview, then revise answers that lack clarity or concrete evidence.