Goldman Sachs Software Engineer Superday and DSA Interview Experience
Question Details
Hello everyone, just went through GS Superday. Here are the details: 1 - SDLC + Resume round: The questions from my resume were relatively easy, just some deep dives. They asked me a LC question i
Full Details
Hello everyone, just went through GS Superday. Here are the details: 1 - SDLC + Resume round: The questions from my resume were relatively easy, just some deep dives. They asked me a LC question in this round: avgOfStudentsScore(). You should be able to find it easily. We had around 10 mins remaining in this round, so the interviewers asked me to verbally solve Parking Lot (multiple floors) question. I still wrote down the class design to be safe 2 - Design Round: I was expecting LLD but was asked HLD for twitter and only tweets on home page (global tweets + follower tweets). Asked to draw a diagram. After this, I was asking to write down the entities and their fields. Then the interviewers asked me a bunch of questions about databases: difference between relational databases vs others, why postgreSQL here, can we use any other database, etc. Then they asked me to exolain how OOP principles would apply here (specificially in data entities). Overall, not too hard if you study System Design and solve frequently asked questions from GS. 3 - DSA: This is the round where I struggled a bit. I was asked to design a blackjack game where the Ace could be used as 1 or 11. Tell us if a hand is blackjack or not. I struggled with the egde case part. 2 days after this, I was invited to an additional DSA round. I think probably because feedback from all rounds (Coderpad + Design + SDLC) was really good - only DSA wasn't good.
Additional DSA round: Max area of 1s in a grid with 0s and 1s. Classic leetcode question. They grilled me hard on this one though. 10-20 questions about DFS vs BFS were asked. Waiting for results - USA #Goldman #GoldmanSachs
About This Question
This is a reported interview question from a goldman sachs interview for a swe role reported in 2026.
It covers the following topics: Graph, Sql, System Design, Oop, Queue, Matrix .
Difficulty rating: Easy
More Goldman Sachs Interview Questions
About Goldman Sachs Interview Reports
This question was reported by a candidate who interviewed at Goldman Sachs. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Goldman Sachs are the higher-signal extractions to take from this report.
For broader preparation context, the Goldman Sachs interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Goldman Sachs reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Goldman Sachs Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Goldman Sachs reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.