← Goldman Sachs Interview Insights

Goldman Sachs·Software Engineer·Onsite - Behavioral / Leadership·Junior

Junior
Jun 2026

Summary

Behavioral round for a software engineering role at Goldman Sachs. Two questions, both pretty standard, but the academic integrity one threw me a bit more than I expected.

Questions Asked (2)

Q1

Tell me about a project you're proud of. What did you build, what was your role, and what impact did it have?

Adaptability & AmbiguityTechnical Trade-offs
Author's notes

Pretty standard opener.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Choose a technically challenging project where you navigated ambiguity and made deliberate trade-offs, then structure your answer to highlight your specific contributions and measurable impact. Emphasize how your decisions balanced competing priorities like performance, scalability, and delivery speed, and tie the outcome to business or user value.

Pro tip: Quantify impact with concrete metrics (e.g., latency reduction, cost savings, revenue lift) and briefly mention a trade-off you consciously accepted—this signals engineering maturity and business awareness, which Goldman Sachs values highly.

1. Set the context and problem

Briefly describe the project's purpose, the team size, and the specific problem or ambiguity you faced. Keep it concise so the interviewer understands the stakes without getting lost in details.

2. Clarify your role and ownership

State your exact role and what you personally owned—whether it was architecture, a critical component, or leading a workstream. Avoid vague 'we' statements; use 'I' to make your contributions clear.

3. Explain technical decisions and trade-offs

Walk through one or two key technical choices you made, the alternatives you considered, and why you chose your approach. Highlight how you balanced factors like performance, maintainability, and time-to-market.

4. Show adaptability amid ambiguity

Describe how you handled changing requirements, incomplete information, or unexpected obstacles. Emphasize your ability to make progress and adjust course without losing sight of the goal.

5. Quantify the impact and reflect

Share measurable outcomes (e.g., reduced latency by 40%, saved $X annually, increased user engagement by Y%). End with a brief reflection on what you learned or how it influenced your engineering approach.

Key Points to Mention

  • A specific technical challenge and the trade-offs you evaluated (e.g., consistency vs. availability, build vs. buy).
  • Your individual ownership and contributions, using 'I' statements to distinguish your work from the team's.
  • How you navigated ambiguity or changing requirements with a structured approach.
  • Quantifiable impact on business metrics, performance, or user experience.
  • Collaboration with cross-functional teams (e.g., product, risk, compliance) if relevant.
  • A lesson learned or how the project improved your engineering judgment.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.

Q2

If a classmate takes credit for your work, like submitting your code as their own or claiming your contribution, how do you handle it?

Conflict ResolutionStakeholder Management
Author's notes

This one caught me mid-sentence because I wasn't expecting an academic integrity scenario in a professional interview.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Emphasize a calm, professional response that prioritizes direct communication and evidence-based resolution. Show that you address the issue privately first, escalate only if necessary, and focus on maintaining teamwork and integrity. Highlight your ability to handle conflict constructively while protecting your work and reputation.

Pro tip: Mention that you document your contributions proactively (e.g., via version control, email trails) so you can resolve disputes factually without escalating emotions. This demonstrates foresight and professionalism, key traits at a firm like Goldman Sachs.

1. Stay Calm and Assess

Avoid reacting emotionally; gather facts and evidence of your contribution. Consider the context and whether it might be an honest mistake or intentional.

2. Address Privately

Speak with the classmate one-on-one in a non-confrontational manner. Explain your concerns and give them a chance to correct the record.

3. Escalate if Necessary

If the issue persists, bring it to a supervisor, professor, or team lead with documented evidence. Frame it as seeking guidance, not tattling.

4. Focus on Resolution

Propose solutions such as correcting attribution, implementing clear contribution guidelines, or using collaboration tools to track work.

5. Learn and Prevent

Reflect on how to prevent future issues, such as documenting work consistently and setting clear expectations in team settings.

Key Points to Mention

  • Direct, private communication first
  • Use of evidence (e.g., Git commits, emails) to support your claim
  • Escalation as a last resort, with a focus on resolution
  • Maintaining professionalism and teamwork
  • Preventive measures like documentation and clear role definitions
  • Alignment with company values like integrity and collaboration

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.