|tips

Medium Goldman Sachs Interview Questions: Strategy Guide

How to tackle 171 medium difficulty questions from Goldman Sachs — patterns, time targets, and practice tips.

Medium questions at Goldman Sachs typically involve applying core algorithms and data structures to realistic financial or data-processing scenarios. They are less about obscure tricks and more about clean, efficient implementations under constraints—think optimizing transaction logs, merging time intervals, or validating structured data. With 171 Medium questions out of their 270 total, mastering this difficulty is essential for passing their technical screens.

Common Patterns

Goldman Sachs Medium problems often focus on arrays, strings, hash maps, and intervals. You’ll frequently see:

  • Array/string manipulation with two-pointer or sliding window techniques.
  • Hash map counting for frequency analysis or lookups.
  • Interval merging and scheduling common in time-based data.
  • Stack-based parsing for validation or transformation tasks.

Here are examples of a sliding window problem across languages:

def max_subarray_sum(nums, k):
    window_sum = sum(nums[:k])
    max_sum = window_sum
    for i in range(k, len(nums)):
        window_sum += nums[i] - nums[i - k]
        max_sum = max(max_sum, window_sum)
    return max_sum

Time Targets

In a Goldman Sachs interview, you’ll typically have 30-45 minutes per coding question. For a Medium problem, aim to:

  • Understand and plan within 5-7 minutes.
  • Code a working solution within 15-20 minutes.
  • Test and debug with edge cases in 5-10 minutes.
  • Discuss optimization if time remains.

Practice solving Medium problems within 25 minutes to build a buffer for interview pressure. Speed comes from recognizing patterns quickly—drill the common types until implementation is automatic.

Practice Strategy

  1. Focus on frequency: Prioritize high-frequency topics like arrays, hash maps, and strings from the Goldman Sachs question list.
  2. Simulate conditions: Use a timer and code without autocomplete to mimic the interview environment.
  3. Write clean code first: Get a brute-force or straightforward solution working before optimizing. Interviewers value clarity and correctness initially.
  4. Test thoroughly: Include edge cases like empty inputs, single elements, and large constraints. Verbally walk through your test cases during practice.
  5. Review and repeat: After solving, analyze optimal solutions and re-implement them a day later to reinforce the pattern.

Practice Medium Goldman Sachs questions

Related Articles