← Goldman Sachs Interview Insights

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

Intermediate
May 2026

Summary

Behavioral round at Goldman Sachs for a Software Engineer role. Two scenarios, both leaning into the messier side of professional life: navigating a team that doesn't want you there, and figuring out what to do when your manager asks for data you probably shouldn't just hand over.

Questions Asked (2)

Q1

You've just been made team lead by your manager, but one collaborator openly pushes back on the decision and challenges your authority. How do you handle it, and how do you communicate with the collaborator, the rest of the team, and your manager?

Conflict ResolutionStakeholder ManagementCross-functional Alignment
Author's notes

This one is trickier than it looks because the instinct is to either avoid the conflict or immediately escalate to your manager, and both feel like the wrong move.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Acknowledge the pushback as a signal to listen first, then address it privately with the collaborator to understand their concerns and find common ground. Reinforce your leadership through actions and transparent communication with the team, while keeping your manager informed and aligned on expectations. Frame the situation as an opportunity to build trust and strengthen team dynamics.

Pro tip: In finance-driven tech environments like Goldman Sachs, emphasize data and results over authority—demonstrate leadership by delivering quick wins and involving the collaborator in decisions, turning resistance into collaboration.

1. Listen and Understand

Schedule a private one-on-one with the collaborator to hear their concerns without defensiveness. Ask open-ended questions to uncover the root cause of their pushback, whether it's about the decision process, past dynamics, or role clarity.

2. Address Concerns and Set Expectations

Acknowledge their perspective, clarify your role and responsibilities as lead, and collaboratively define how you'll work together. If needed, involve your manager to reinforce the decision and align on expectations.

3. Communicate with the Team

Reinforce team goals and your commitment to inclusive leadership in a team setting. Avoid singling out the collaborator; instead, emphasize shared objectives and invite input to build consensus.

4. Keep Manager Informed

Update your manager on the situation and your approach, seeking guidance and ensuring alignment. Highlight steps taken to resolve the conflict and any impact on team performance.

5. Monitor and Adapt

Observe the collaborator's behavior and team dynamics over time. Adjust your approach as needed, and be prepared to escalate if the behavior undermines team performance or violates company values.

Key Points to Mention

  • Emotional intelligence: staying calm and empathetic rather than defensive
  • Private conversation to avoid public confrontation and preserve dignity
  • Clear communication of expectations and boundaries as a new lead
  • Involving the manager as a sponsor, not a rescuer, to reinforce authority
  • Focus on shared goals and team success over personal authority
  • Data-driven leadership: using results to demonstrate competence and build credibility

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

Q2

You're the sole engineer on a project that holds sensitive data like customer PII or security credentials. Your manager asks you to share that data or grant them access. What do you do?

Stakeholder ManagementAdaptability & Ambiguity
Author's notes

Genuinely stumped me for a second because the instinct is just to comply, it's your manager.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Acknowledge the request and clarify the business need, then verify whether the access or data sharing is compliant with company policy and regulatory requirements. Propose a secure alternative that meets the manager's goal without exposing sensitive data, and escalate through proper channels if the request is inappropriate.

Pro tip: Frame your response as a partnership: 'I want to help you achieve X, and here's how we can do it safely.' This shows you're solution-oriented, not obstructive, and it's exactly what Goldman Sachs expects from engineers handling sensitive data.

1. Clarify the request

Ask open-ended questions to understand what the manager actually needs—the underlying business goal, not just the data itself. This avoids jumping to conclusions and shows you're collaborative.

2. Assess policy and risk

Check company policies, data classification, and regulatory requirements (e.g., GDPR, SEC, FINRA) to determine if sharing is permissible. Consider least-privilege and need-to-know principles.

3. Propose secure alternatives

Offer options like aggregated/anonymized data, temporary access with approval, or using a secure internal tool. Focus on enabling the manager's goal without violating security.

4. Escalate if necessary

If the request is clearly inappropriate or the manager insists, escalate to your security team, compliance, or a trusted senior leader. Document the request and your response.

5. Follow up and document

Ensure the chosen path is executed securely and keep a record of decisions. This protects you and the firm, and demonstrates accountability.

Key Points to Mention

  • Least privilege and need-to-know access principles
  • Regulatory compliance (e.g., GDPR, SEC, FINRA) and company data policies
  • Secure alternatives like anonymization, aggregation, or temporary access with approval
  • Escalation paths: security team, compliance, or legal
  • Documentation of requests and decisions
  • Professional communication that balances security with business enablement

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