Goldman Sachs Interview Questions (120)

Goldman Sachs is one of the most competitive financial institutions for software engineers, known for building large-scale trading systems, risk platforms, and data infrastructure that power global financial markets. Because of this, the Goldman Sachs coding interview strongly evaluates a candidate’s ability to write clean, efficient algorithms under pressure.

The interview process typically starts with an online assessment or phone screen focused on data structures and algorithms. Candidates who pass move to multiple technical rounds where interviewers test coding ability, problem solving, and sometimes system design for experienced roles. Expect real-world problem solving scenarios similar to production systems used in finance and trading environments.

From analyzing hundreds of real candidate reports, Goldman Sachs commonly asks problems involving:

• Arrays and hashing for data processing tasks
• Binary search and sorting for financial data queries
• Graphs and BFS/DFS for dependency or network-style problems
• Dynamic programming for optimization challenges
• Strings and sliding window for log and transaction analysis

The difficulty distribution usually leans toward medium-level DSA problems, with a mix of easier warm-up questions and a few harder algorithmic challenges in later rounds.

FleetCode helps you prepare with 120 real Goldman Sachs interview questions collected from candidate experiences. Problems are organized by difficulty and topic, allowing you to focus on patterns Goldman Sachs interviewers ask most often. Each problem includes explanations and solutions in Python, Java, and C++, helping you build the speed and confidence needed to succeed in the Goldman Sachs coding interview.

Preparing for the Goldman Sachs coding interview requires more than just solving random problems. The company follows a fairly structured evaluation process focused on algorithmic thinking, code quality, and communication.

Typical Goldman Sachs interview format:

• Online Assessment (60–120 minutes): Usually 2–3 coding problems focused on arrays, strings, and basic algorithms.
• Phone or Technical Screen: One or two coding questions solved in a shared editor. Interviewers evaluate problem solving and code clarity.
• Onsite / Virtual Onsite (3–5 rounds): Multiple coding interviews plus behavioral discussions. Experienced candidates may also face a system design round.

Most common DSA topics asked by Goldman Sachs:

• Arrays, prefix sums, and hashing
• Two pointers and sliding window techniques
• Binary search and sorted data structures
• Graph traversal (BFS / DFS)
• Dynamic programming and optimization problems
• Stack or heap based problems

Unlike some tech companies that emphasize extremely complex algorithms, Goldman Sachs often focuses on well-structured medium difficulty problems. Interviewers care about how clearly you reason through the problem and whether your solution is efficient and production-ready.

Preparation strategy that works well:

• Solve around 80–120 curated problems focused on common Goldman Sachs patterns.
• Practice writing code without relying on autocomplete or heavy libraries.
• Explain your thought process out loud while solving problems.
• Review time and space complexity for every solution.

Common mistakes candidates make:

• Jumping straight into coding without clarifying edge cases
• Ignoring time complexity improvements after a brute-force solution
• Writing messy code without clear variable naming
• Not testing the solution with example inputs

Most successful candidates spend about 6–8 weeks preparing, focusing on consistent daily practice rather than cramming. Working through a curated set of Goldman Sachs interview questions—like the 120 problems on FleetCode—helps you quickly recognize patterns and perform confidently during the actual interview.