Back

Goldman Sachs Software Engineer Interview: Process + Questions

What to expect for the Goldman Sachs's SWE role and how Nora AI helps you prep

Goldman Sachs Software Engineer Interview Logo
05 December 2025

Goldman Sachs Software Engineer Interview: Process + Questions

What to expect for the Goldman Sachs's SWE role and how Nora AI helps you prep

About Goldman Sachs’s Hiring Philosophy

Goldman Sachs hires engineers who can build resilient, scalable systems design solutions for global finance. Their culture values rigorous problem-solving, ownership, and cross-functional collaboration, especially since engineers partner closely with traders, quants, risk teams, and product groups. The hiring process is known for DS&A questions, high coding standards, and strong communication expectations under pressure. Many candidates use an interview cheat sheet, algorithm practice problems, and SWE interview practice routines while preparing.

Quick Stats

• Typical process length: 3–5 rounds over 2–4 weeks

• Core focus areas: Algorithms & data structures, system design interview fundamentals, debugging, object-oriented design, leadership behaviors, and communication

• Interview style: Fast-paced, fundamentals-heavy, high bar for code quality and reasoning

What Goldman Sachs Looks For

• Strong algorithmic and data structures mastery

• Clean, structured coding with optimal complexity

• Clear reasoning during technical phone screen sessions

• Ownership mindset in ambiguous scenarios

• Collaboration skills supported by solid teamwork interview examples

“GS goes deep on DS&A. They expect you to write clean code and explain every step.” — SWE candidate

“Behavioral interview was intense. They care a lot about ownership and why you made certain decisions during tough situations.” — Past Interviewee

Round 1: Recruiter / HR Screening (20–30 mins)

What to Expect

This round verifies eligibility and evaluates communication, motivation, and understanding of software engineer skills Goldman Sachs expects. Some conceptual topics and light collaboration interview questions may surface.

Example / Reported Questions

• “Walk me through your technical background.”

• “Why Goldman Sachs over other firms?”

• “Describe a technical project you’re most proud of.”

• “What tech stack are you most comfortable with?”

Tips

• Speak clearly about impactful projects.

• Show reliability, ownership, and adaptability.

• Prepare leadership interview examples and conflict resolution examples.

• Use STAR-lite structure for concise responses.

• Take advantage of Nora AI's Standard Mode to polish your intro, motivation, and project explanations so you deliver confident, recruiter-ready answers in under 2 minutes.

Round 2: Online Assessment (OA) — Hackerrank / Codility (60–90 mins)

What to Expect

The software engineer coding test typically includes 2–3 medium–hard DS&A tasks. Expect sliding window patterns, dynamic programming interview problems, graphs, strings, and optimal complexity constraints. Many candidates use LeetCode interview prep and easy to understand GS coding preparation references.

Example / Reported Questions

• “Given a list of transactions, detect anomalies using sliding window logic.”

• “Find the minimum operations to transform one string into another.”

• “Determine if a graph contains a cycle and return the cycle path.” (common graph cycle detection)

• “Optimize portfolio allocation given constraints.”

Tips

• Practice LeetCode mediums: graphs, DP, heaps.

• Goldman penalizes inefficient solutions heavily.

• Re-test edge cases: empty lists, large values, duplicates.

• Use DP, graph, and algorithm practice problems that mirror most asked Goldman Sachs coding questions.

Round 3: Technical Phone Interview (45–60 mins)

What to Expect

This technical phone screen is a live coding session. Evaluates clarity, optimization, debugging, and architectural reasoning. Questions often mirror graph interview questions, recursion, and tree algorithms.

Example / Reported Questions

• “Implement LRU Cache from scratch.”

• “Find the longest increasing path in a matrix.”

• “Check if a binary tree is height-balanced.”

• “Design a rate limiter with light low latency design concepts.”

Tips

• Explain as you code; clarity matters as much as correctness.

• Use modular, readable functions.

• Practice dry-running logic out loud.

Round 4.1: Coding Round 1 (45–60 mins)

What to Expect

This round focuses on advanced DS&A problems where Goldman Sachs evaluates your ability to optimize, reason through constraints, and handle tricky edge cases. Expect questions aligned with algorithm mastery and the best way to study data structures for GS.

Example / Reported Questions

• “Design a data structure for O(1) insert, delete, and getRandom.”

• “Given intervals, merge and detect overlaps efficiently.”

• “Shortest path in a weighted graph (Dijkstra).”

• “Reconstruct an array given all subset sums.”

Tips

• Think in invariants, constraints, and optimal complexity.

• Use modular, production-quality code with clear naming.

• Review algorithm practice problems and core DS&A patterns.

Round 4.2: Coding Round 2 (45–60 mins)

What to Expect

Another DS&A-heavy session designed to test your ability to reason under pressure using recursion, BFS/DFS, hashing, tree algorithms, and classic graph interview questions. This round stresses optimization and communication clarity.

Example / Reported Questions

• “Count islands with diagonal adjacency.”

• “Serialize and deserialize a binary tree.”

• “Check if a graph is bipartite.”

• “Find median from a data stream.”

Tips

• Start with brute force → refine → final optimized solution.

• Explain trade-offs and decision-making at each step.

• Revisit dynamic programming interview questions and sliding window patterns.

Round 4.3: System Design / Architecture Round (45–60 mins)

What to Expect

Assesses your approach to scalable, reliable, low-latency systems — essential for financial workloads. Expect topics covering API design, queues, partitions, load balancer strategies, distributed cache system design, and high-throughput architectures.

Example / Reported Questions

• “Design a real-time trade processing system.”

• “Design a messaging queue from scratch.”

• “How would you scale a load balancer for high-frequency trading?”

• “Explain how you’d design a distributed cache system.”

Tips

• Prioritize latency, reliability, replication, and fault tolerance.

• Break systems down step-by-step: routing → processing → persistence → scaling.

• Reference distributed systems interview preparation concepts.

Round 4.4: Behavioral / Culture Fit Interview (30–45 mins)

What to Expect

Goldman digs deep into ownership, resilience, teamwork, conflict navigation, and decision-making under pressure. Expect questions tied to teamwork interview examples, conflict resolution examples, and leadership stories.

Example / Reported Questions

• “Tell me about a time you solved a high-pressure technical issue.”

• “Describe a conflict with a team member and how you handled it.”

• “Explain a decision you made that others disagreed with.”

• “How do you ensure reliability in production systems?”

Tips

• Use STAR with measurable results and clear reasoning.

• Prepare vivid examples showing ownership and calm under pressure.

• Show introspection, collaboration, and communication discipline.

• Most candidates struggle because their behavioral stories sound flat, unclear, or too long. Boost through Nora AI's Behavioral Mode to tighten your STAR stories, highlight impact, and practice delivering confident answers that match what Goldman Sachs screens for.

Frequently Asked Questions (FAQ)

1) How many rounds are there?

Typically 3–5 rounds: recruiter → OA → technical phone → onsite.

2) What topics are most common?

• Trees and graphs

• Dynamic programming

• Hashing and window techniques

• OOP + clean code

• System architecture basics

• Behavioral ownership themes

3) How long does the process take?

Usually 2–4 weeks.

4) How should I prepare?

• Study DS&A daily, especially graphs and DP.

• Use LeetCode interview prep strategies.

• Practice system design interview formats.

• Focus on how to prepare for Goldman Sachs SWE interview by studying real patterns and easy to understand GS coding preparation.

• Review concurrency, recursion, and OOD.

• Power your workflow with Nora AI's Mock Interviewer to simulate and practice this role.

Related Articles

More articles you might find interesting.

Ready for a Mock Interview?

Candidate avatar 1
Candidate avatar 2
Candidate avatar 3
Candidate avatar 4
Candidate avatar 5