Goldman Sachs interview notes, page 4 of 4

Large Enterprises

Most of these Goldman Sachs write-ups come from Software Engineers (30), then Product Managers (5) and Machine Learning Engineers (2). The most reported rounds are the technical phone screen (21), the behavioral / leadership round (6), the online assessment (4) and the onsite coding round (4).

37 interview notes · updated Aug 2026

Goldman Sachs·Software Engineer·Technical Phone Screen

Jun 2026

Goldman Sachs linear algebra question, pretty much a pure math screen. One system of equations, three unknowns, figure out what kind of solution set you're dealing with. Short and focused.

Given the system of three linear equations with three unknowns (2x₁ − 2x₃ = 10, 2x₁ + 3x₂ + x₃ = 20, −x₁ + x₂ + 2x₃ = 5), determine whether the system has a unique solution, infinitely many solutions, no solution, or none of those cases.

“Row reduction is the move here.”

View Post

Goldman Sachs·Software Engineer·Technical Phone Screen

Jun 2026

Interviewed for a data science role at Goldman Sachs and got a math question I did not expect to see outside of a pure math class.

As the Fibonacci sequence progresses, what value does the ratio of a term to its preceding term converge to?

“Blanked for a second because I was expecting something about ML or statistics.”

View Post

Goldman Sachs·Software Engineer·Technical Phone Screen

Jun 2026

Goldman Sachs SWE interview with a greedy/sorting array problem. Pretty focused session, one question but they wanted clean code and a clear explanation of the approach.

Given an array of n integers and a number k, find the maximum number of elements whose sum is still less than k, and return that sum.

“Sort ascending, greedily pick the smallest elements until adding the next one would hit or exceed k.”

View Post

Goldman Sachs·Software Engineer·Technical Phone Screen

Jun 2026

Goldman Sachs SWE interview with a pretty meaty in-memory design problem. The whole session was basically one question about building a tree-structured workspace manager, and they cared a lot about edge cases and efficiency under scale.

Design and implement an in-memory workspace resource manager that supports a tree of folders and files, with operations to create, list, delete, and move resources, including cycle detection and recursive deletion.

“This one took me a while to even set up the data model.”

View Post

Goldman Sachs·Software Engineer·Onsite - System Design / Architecture

Jul 2026

Goldman Sachs SWE system design round, one question about building a web scraping engine. Pretty open-ended, which I wasn't fully prepared for.

Design a web scraping engine.

“I jumped straight into the crawler logic and spent way too long on the fetching layer before anyone asked about rate limiting or robots.txt compliance.”

View Post

Goldman Sachs·Software Engineer·Online Assessment (OA)

Jul 2026

Took the Goldman Sachs OA and honestly wasn't sure what to expect, but it ended up being the easiest online assessment I've ever sat through. FizzBuzz and a basic REST API. First time I've walked away from an OA feeling like I actually nailed everything.

Implement FizzBuzz.
Build a basic REST API.

“I've done this so many times it's basically muscle memory at this point.”

View Post

Goldman Sachs·Software Engineer·Technical Phone Screen

Jul 2026

Goldman Sachs SWE interview had me implement a double-ended queue from scratch, which sounds straightforward until you actually have to think through all the edge cases under pressure. Decent problem, nothing too wild.

Implement a double-ended queue (Deque) for strings from scratch, supporting addFirst, addLast, removeFirst, removeLast, peekFirst, peekLast, and getSize, all in O(1) time. Include test cases covering edge cases.

“The O(1) constraint is what makes this non-trivial.”

View Post