Software Engineer

Software EngineerAnalystMedium

This interview process is for an Analyst-level Software Engineer position at Goldman Sachs. It is designed to assess a candidate's technical proficiency, problem-solving abilities, and cultural fit within the firm.

Rounds·3

Timeline·~14d

Experience·1 - 3 yrs

Comp band·US$90000 - US$120000

Interview time·120 min

Evaluation

What they measure.

  • Technical Skills (Data Structures, Algorithms, System Design)
  • Problem-Solving Approach
  • Communication Skills
  • Teamwork and Collaboration
  • Cultural Fit and Motivation

Preparation

How to prepare.

Tips

  1. Review fundamental computer science concepts, including data structures and algorithms.
  2. Practice coding problems on platforms like LeetCode, HackerRank, or AlgoExpert.
  3. Understand core financial concepts relevant to the role (e.g., trading, risk management).
  4. Prepare for behavioral questions by reflecting on past experiences using the STAR method.
  5. Research Goldman Sachs's culture, values, and recent news.
  6. Prepare thoughtful questions to ask the interviewers.

Study plan

Fig · Study plan — 04 phases

01 / 04
01

Phase 01 of 04

Data Structures and Algorithms

Weeks 1-2: Data Structures & Algorithms fundamentals. Practice 2-3 problems daily.

Weeks 1-2: Focus on Data Structures (Arrays, Linked Lists, Trees, Graphs, Hash Tables) and Algorithms (Sorting, Searching, Dynamic Programming, Recursion). Practice implementing these in your preferred language. Solve at least 2-3 problems per day.

Questions

Commonly asked.

  • What is the time and space complexity of your solution?
  • Can you optimize this code further?
  • Describe a challenging bug you encountered and how you debugged it.
  • How would you design a URL shortener service?
  • Tell me about a time you failed and what you learned from it.
  • Why are you interested in working at Goldman Sachs?
  • What are your strengths and weaknesses as a software engineer?

Locations

Regional differences.

Fig · Regions — 03 locations

01 / 03

Location

New York

Interview focus

Understanding of local market trends and financial technology.Adaptability to the specific work culture in the region.

Common questions

  • Explain a complex technical project you worked on.
  • How do you handle tight deadlines and high-pressure situations?
  • Describe a time you disagreed with a colleague or manager and how you resolved it.

Tips

  • Research common financial regulations and practices relevant to the location.
  • Network with current employees in the specific office to understand local nuances.

Rounds

Round-by-round.

Expand a step for evaluation criteria, sample questions, and prep notes.

Med

Technical Interview - Data Structures And Algorithms · 45 min · Software Engineer / Senior Software Engineer

This round typically involves a coding challenge, often presented as a problem to solve on a shared online editor or whiteboard. The interviewer will assess your ability to translate a problem into code, your understanding of data structures and algorithms, and your approach to testing and optimizing your solution. Expect to discuss the time and space complexity of your code.

What they look for

Clean, readable, and efficient code.Logical approach to problem-solving.Ability to explain trade-offs.Understanding of edge cases.

Evaluation

  • Coding proficiency
  • Algorithmic thinking
  • Problem-solving skills
  • Efficiency of solution (time and space complexity)

Sample questions

  • Given an array of integers, return indices of the two numbers such that they add up to a specific target.

    ArrayHash TableTwo Pointers
  • Reverse a linked list.

    Linked ListRecursionIteration
  • Find the kth smallest element in a sorted matrix.

    MatrixHeapBinary Search

Prep for this round

  1. 01Practice coding on a whiteboard or shared editor.
  2. 02Be prepared to explain your code line by line.
  3. 03Think out loud and communicate your thought process.
  4. 04Ask clarifying questions if the problem is unclear.

Common rejection reasons

  • ×Inability to articulate thought process clearly.
  • ×Lack of fundamental programming knowledge.
  • ×Poor problem-solving approach.

DSA

Coding questions at Goldman Sachs.

Frequently reported on Goldman Sachs loops

Other guides

More at Goldman Sachs.