
Goldman Sachs Data Analyst candidates report an HR screen followed by a practical analytics interview covering SQL, data cleaning, dashboards, business insights, and stakeholder communication.
$95K
Avg. Base Comp
$140K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Goldman Sachs Data Analyst interview preparation should center on explaining an end-to-end analytics workflow clearly. The direct Data Analyst account begins with an HR conversation about the candidate’s background, SQL experience, and data-analytics experience. Treat this as more than a résumé recap: be prepared to connect prior work to the role’s practical requirements.
The technical discussion described by the candidate covered SQL queries, cleaning data, producing dashboard reports, and problem-solving scenarios. A strong answer connects the analysis to a decision, rather than stopping at a query or visualization. One reported prompt asked how the candidate would examine a large dataset, identify useful business insights, and present findings to stakeholders. Practice narrating your sequence: define the question, check and clean the data, analyze it in SQL, choose an appropriate dashboard view, validate the takeaway, and tailor the recommendation to the audience.
Behavioral questions also addressed teamwork, deadlines, and stakeholder communication. Prepare specific examples that show how you delivered analysis under constraints and made findings understandable to nontechnical partners. The available Data Analyst evidence is limited to one detailed candidate account, so exact format and depth may vary by team.
Synthesized from 1 candidate report by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Goldman Sachs process.
What stood out most was how closely the interview stayed tied to practical analytics work rather than purely theoretical questions. I applied online and was then invited to an HR screening call. The recruiter walked through my background and asked about my experience with SQL and data analytics. It was a straightforward initial conversation designed to establish whether my previous work matched what the role required.
The next stage was a technical round covering several parts of a typical analyst workflow. I was asked about writing SQL queries, cleaning data, producing dashboard reports, and approaching problem-solving scenarios. One broader question asked how I would work through a large dataset to identify useful business insights and then present those findings to stakeholders. That question required me to think beyond the analysis itself and explain how I would communicate the results in a way that supported business decisions.
There were also behavioral questions about working with a team, managing deadlines, and communicating with stakeholders. Overall, the process felt organized and professional. I would describe the difficulty as moderate for someone who already has hands-on analytics experience, since the questions covered both technical execution and the practical communication expected from an analyst. I ultimately did not receive an offer. My main takeaway is to prepare examples that show your full process, from querying and cleaning data through building a dashboard and explaining the resulting insights to a nontechnical audience.
Prep tip from this candidate
Prepare a concrete walkthrough of how you would analyze a large dataset, clean it with SQL, turn the results into a dashboard, and present actionable insights to stakeholders. Also have specific examples ready about teamwork, deadline management, and stakeholder communication.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Goldman Sachs
Given that it is raining today and that it rained yesterday, write a function to calculate the probability that it will rain on the nth day after today.
| Question | |
|---|---|
| Bagging vs Boosting | |
| Google Maps Improvement | |
| Append Frequency | |
| Minimum Absolute Distance | |
| Comparing Search Engines | |
| Target Indices | |
| Production Model Monitoring | |
| SageMaker Deployment Architecture | |
| Deciding Between Solutions | |
| Company Acquisition Choice | |
| Client Solution Pushback | |
| Alternative Vendor Tradeoff | |
| Credit Score Estimation | |
| Using APIs for Downstream Tasks | |
| Direct Mail | |
| Risk Model for a Mortgage Bank | |
| Analyzing Multiple Data Sources | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| Employee Salaries | |
| Comments Histogram | |
| Closest SAT Scores | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Slacking Employees Salaries | |
| Experiment Validity | |
| Find the Missing Number | |
| Compute Deviation |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reports applying online before an HR screening call. The recruiter discussed the candidate’s background and asked about SQL and data-analytics experience, apparently to assess whether prior work aligned with the role. Prepare a concise walkthrough that connects your tools, datasets, and business impact.
The reported technical round covered SQL queries, data cleaning, dashboard reports, and analytical problem solving. Candidates may be asked to describe how they would work through a large dataset, find useful business insights, and turn those findings into a clear recommendation.
The same account included questions about working with a team, managing deadlines, and communicating with stakeholders. Use concrete examples that show how you prioritize work, explain findings to a nontechnical audience, and keep analysis tied to a business decision.