Goldman Sachs SWE Interview: OA and HireVue Guide

Estimated read time: 7-9 minutes

Summary: The Goldman Sachs SWE OA/HireVue stage is path-dependent and appears more common in campus, intern, new-grad, engineering analyst, and technology analyst paths. The source supports HackerRank-style timed coding and HireVue-style recorded responses in some technology paths, but it does not prove that every experienced SWE candidate receives this stage. Prepare for coding fundamentals plus concise recorded communication.

TL;DR + FAQ (read this first)

At-a-glance takeaways

• OA/HireVue is most clearly supported for campus and analyst-style technology paths.
• Experienced SWE paths may differ, so confirm whether this stage applies.
• OA evidence supports timed coding, DSA, arrays, strings, hash maps, and test-passing under time pressure.
• HireVue evidence supports recorded motivation and behavioral/technical responses.
• Exact wording and current duration are not officially verified.

Quick FAQ

Is OA/HireVue universal?
No. It is possible or role-dependent, especially outside campus paths.

What tools might appear?
Candidate reports mention HackerRank-style coding and HireVue-style recorded video.

What should I prepare?
Timed coding, clear explanation, motivation for Goldman Sachs, and why engineering in finance.

What is the main mistake?
Preparing only for coding and then giving weak recorded answers, or assuming HireVue applies to every SWE role.

---

1) What OA/HireVue measures

The OA measures whether you can solve coding tasks under time pressure. The source points to correct code, efficient algorithms, and passing tests. The HireVue side, when present, measures whether you can communicate motivation, background, and role fit clearly in a recorded format.

The stage is especially important for candidates in intern, new-grad, analyst, or technology analyst paths. For experienced SWE roles, ask whether the process uses the same assessment gate or moves directly to live interviews.

---

2) How the tasks may feel

A coding task may start with arrays, strings, hash maps, or common DSA patterns. The hidden difficulty is time management: read carefully, choose a simple correct approach, pass core tests, and leave time for edge cases. A recorded response may ask why Goldman Sachs, why engineering, or how you handled a team challenge.

For recorded answers, use a direct structure: situation, action, result, and connection to the role. You do not need a theatrical answer. You need a credible one.

---

3) Questions and tasks to prepare

These are representative tasks based on the source themes, not confirmed verbatim Goldman Sachs wording.

• Solve a timed coding challenge involving arrays or strings, then explain the runtime and edge cases.
• Given a list of transactions or records, group them by key and return an aggregate. Now handle missing fields and duplicate records.
• Use a hash map to improve a nested-loop solution. What test cases prove the optimized version is equivalent?
• Given a string, detect whether it satisfies a constraint after at most one edit or transformation.
• Why Goldman Sachs, and why engineering or technology?
• Tell me about a time you worked on a team under a deadline.
• Describe a technical project you are proud of and what you personally built.

---

4) Level-specific expectations

The slug table marks OA/HireVue as relevant for intern, new grad, junior, mid-level, and senior+ possible or role-dependent. The research says campus and analyst paths are more likely.

• Intern and New Grad: prepare seriously for both timed coding and recorded motivation/behavioral responses.
• Junior: expect possible assessment depending on path and location.
• Mid-Level and Senior: confirm applicability directly, since experienced SWE paths are less clear in public evidence.
• Staff+: public evidence is too weak to assume OA/HireVue.

---

5) Common failure modes

Assuming this applies to every role. Verify the path before over-indexing on OA/HireVue.

Weak recorded communication. Prepare concise answers for motivation and project ownership.

Ignoring edge cases in timed coding. Passing obvious examples is not enough.

Overcomplicating solutions. Time-limited assessments reward simple, correct code.

Path confusion. Analyst, SWE, strats, and quant developer loops can differ.

---

6) How to prepare

• Practice timed array, string, hash-map, and basic DSA tasks.
• Write edge cases before submitting: empty input, duplicates, negative values, large input, malformed records.
• Prepare a 60-second answer for why Goldman Sachs and why engineering.
• Prepare one project story and one teamwork story.
• Confirm with the recruiter whether OA, HireVue, or both apply to your exact role.

---