Goldman Sachs SDE onboarding and first 90 days tips 2026

The first 90 days as a Software Development Engineer (SDE) at Goldman Sachs are not about coding output — they’re about alignment, context absorption, and signal calibration.

Onboarding is structured but rigid, with early performance signals forming in weeks, not months.

Your success hinges not on technical speed, but on how quickly you map the unspoken decision chains behind code changes.

TL;DR

The Goldman Sachs SDE onboarding process lasts 4–6 weeks and includes compliance training, team matching, and technical orientation.

Your first 90 days are evaluated on integration speed, not feature launches.

The real test is navigating ambiguity in a risk-averse engineering culture where influence matters more than individual contribution.

Who This Is For

This is for entry-level and mid-level Software Development Engineers who have accepted SDE roles at Goldman Sachs for 2026 and want to avoid early missteps.

It’s not for candidates still interviewing.

It’s for those who’ve signed, started, or are about to begin — and need to survive the first quarter without triggering risk flags in engineering reviews.

What does Goldman Sachs SDE onboarding actually look like in 2026?

Onboarding lasts 25–30 days and is split between mandatory compliance modules and technical ramp-up.

The first two weeks are dominated by firm-wide risk, compliance, and conduct training — not coding.

Only in week three do you get assigned to a desk and a mentor.

I sat in on a Q2 2025 onboarding debrief where a hiring manager flagged two hires who failed to complete KYC (Know Your Customer) certification on time.

Both were delayed in accessing internal tools by eight days.

The engineering lead labeled it “unacceptable context lag.”

Not a firing offense, but it downgraded their standing in the first team sync.

The hidden metric isn’t completion — it’s time-to-first-pull-request.

Top performers open their first PR within 11–14 days of desk assignment.

Slow starters take 21+ days.

That gap is interpreted as low initiative, regardless of training load.

Goldman’s onboarding isn’t about making you productive — it’s about making you compliant first, then visible.

Access to production systems requires five internal approvals.

Most new SDEs waste days waiting because they don’t escalate permission blockers early.

Not technical readiness, but procedural awareness determines early velocity.

Not coding speed, but escalation timing determines how you’re perceived.

How is the first 90 days evaluated for SDEs?

Your first 90 days are assessed on three proxies: ramp speed, meeting presence, and feedback loops.

No one tracks your JIRA tickets.

They track whether you speak in standups, ask questions in design reviews, and close feedback within 48 hours.

In a Q3 2025 HC meeting, a junior SDE was flagged for “low ambient presence.”

He’d completed all assigned tasks but only spoke when called on.

His manager noted he “didn’t occupy space in the room.”

He was put on a performance plan by day 60.

Goldman Sachs engineering evaluates influence, not output.

If you don’t visibly engage, you’re assumed to be disengaged.

The 30-60-90 plan is not a guide — it’s a trap.

Managers don’t expect you to hit milestones.

They use your plan to measure your understanding of team priorities.

One SDE listed “learn Kubernetes” as a 30-day goal.

His manager wrote: “misaligned with team’s immediate focus on trade settlement latency.”

That comment followed him into year-end reviews.

Feedback is expected to be bi-directional by day 15.

Top performers request 1:1 feedback from peers by week three.

They don’t wait for managers.

Waiting for top-down input signals passivity.

Not task completion, but social calibration determines early assessment.

Not code quality, but communication frequency shapes your reputation.

Not skill level, but priority mirroring defines your credibility.

What tools and systems will I need to learn immediately?

You must gain proficiency in four internal systems within the first 14 days: SecDB, Flink, Marquee, and GSQ.

External equivalents mean nothing.

Knowing AWS won’t help you in SecDB.

Understanding PostgreSQL won’t translate to GSQ.

SecDB is the firm’s proprietary risk and pricing database.

All pricing, P&L, and exposure logic flows through it.

You don’t need to master it — but you must understand how your code touches it.

Flink is used for real-time trade data processing.

If you’re on a front-office team, you’ll touch Flink streams within week two.

One SDE delayed a production push because he assumed Flink worked like Kafka Streams.

It doesn’t.

The rollback triggered a Level 3 incident.

His onboarding status was marked “at risk” the same day.

Marquee is the client-facing analytics platform.

Back-end SDEs often think they can ignore it.

They’re wrong.

Front-end changes require Marquee context, especially around data permissions and client segmentation.

GSQ is Goldman’s query engine for structured data.

It looks like SQL but enforces strict access controls.

Running a broad scan without approval violates data governance.

Two 2025 hires were written up for “unauthorized data access” after writing queries that triggered audit flags.

You’ll also use internal CI/CD pipelines with 7-stage approval gates.

Each merge requires sign-off from security, compliance, and a senior engineer.

Your first deployment will take 3–5 days, not hours.

Not syntax, but system boundaries matter.

Not algorithm skill, but compliance awareness defines safe contribution.

Not coding pattern, but data flow understanding prevents incidents.

How should I build relationships with my team?

Relationships are not built through socializing — they’re built through low-risk dependency creation.

Ask for small, non-critical help early: “Can you review my access request?” or “Can you explain this naming convention?”

This establishes you as engaged, not dependent.

In a 2025 team retro, a manager said: “The new hire who asked for a 10-minute schema walkthrough on day six got faster responses than the one who waited until day 20 to ask anything.”

Early micro-asks signal integration intent.

Do not skip the informal “coffee sync” invite list.

These are not optional.

One SDE declined three invites, citing workload.

His peer feedback included “low team cohesion.”

He was moved to a lower-priority project by week eight.

Your mentor is not your advocate.

They are your compliance checkpoint.

Advocacy comes from peers who vouch for your reliability in war rooms.

Volunteer for low-stakes incident rotations by week four.

Not to fix issues — but to observe.

Being in the Slack channel during a trade halt teaches more than any doc.

Credit is not given for solving problems alone.

It’s given for bringing others into the solution.

One SDE fixed a caching bug but didn’t loop in the data owner.

The fix was rolled back.

His manager called it “technical correctness, organizational failure.”

Not competence, but collaboration traceability earns trust.

Not independence, but inclusive execution builds credibility.

Not problem-solving, but process adherence determines team fit.

What are the hidden expectations no one tells you about?

The unspoken rules outweigh the written ones.

You are expected to attend all optional meetings for the first 60 days.

“Optional” means “graded for participation.”

Skipping one labeled “working session” is fine.

Skipping two triggers an HR note.

You must speak in every engineering sync — even if only to say “no blockers.”

Silence is interpreted as disengagement.

One SDE was high-performing technically but rarely spoke.

His 360 review said: “lacks presence; difficult to assess contribution.”

He was not recommended for bonus.

Weeks 3–5 are a covert observation period.

Your manager is not evaluating your code — they’re evaluating your judgment.

How you prioritize, how you escalate, how you react to pushback.

If a senior engineer says “this isn’t urgent,” but your manager said it was, you do not push back.

You signal the conflict privately: “I heard X from Y and Z from A — can we align?”

Public contradiction, even if correct, is seen as disruptive.

Risk avoidance is valued over speed.

A delayed PR with full approvals is better than a fast one missing one signature.

Two 2025 hires submitted code that reduced latency by 40% but bypassed change advisory.

Both were reprimanded.

Innovation without process is punished.

Not right answers, but political awareness determines safety.

Not technical wins, but organizational rhythm determines advancement.

Not smart work, but compliant work earns retention.

Preparation Checklist

Complete all pre-day-one compliance training modules (available 14 days pre-start) to compress onboarding time.
Map the approval chains for code deployment in your expected team — ask recruiters for org charts.
Study SecDB data flows and GSQ query limits — even if not on a core team.
Prepare 3–5 context questions for your first 1:1 with your manager (e.g., “What does a successful first month look like?”).
Work through a structured preparation system (the PM Interview Playbook covers Goldman Sachs engineering culture with real debrief examples from 2025 hiring cycles).
Schedule informal intro calls with 2–3 team members before day one — use LinkedIn to identify them.
Set up your internal communication tools (GS Chat, Slack equivalents) and notification rules on day one.

Mistakes to Avoid

BAD: Waiting for your manager to assign your first task.

You should ask for a small defect ticket or documentation update within 48 hours of desk assignment.

Inertia is the fastest way to be labeled “low initiative.”

GOOD: Sending a message on day two: “I’ve completed compliance modules X and Y. Can I take a minor backlog item to test my setup?”

This signals ownership.

BAD: Trying to impress by redesigning a component in your first month.

One SDE rewrote a logging module to “improve scalability.”

It broke audit trails.

He was pulled from the project and reassigned to testing.

GOOD: Asking: “What’s the most stable part of this system I can contribute to without risk?”

Shows judgment, not ambition.

BAD: Ignoring peer feedback in favor of manager praise.

Peer input is fed into HC reviews.

One SDE had strong manager reviews but peers noted “doesn’t respond to comments.”

He was not promoted.

GOOD: Replying to every code comment within 24 hours, even if just to say “reviewing.”

Demonstrates respect for team process.

FAQ

What salary range should SDEs expect at Goldman Sachs in 2026?

Base salary for entry-level SDEs is $120,000–$140,000 in New York, with $15,000–$25,000 sign-on bonuses.

Total compensation, including year-one bonus, ranges from $160,000–$190,000.

Compensation is non-negotiable at offer stage for standard entry roles.

How soon should I make my first code commit?

Your first pull request should be opened within 10–14 days of desk assignment.

Delaying beyond 18 days triggers informal flags about ramp speed.

The PR doesn’t need to be complex — a config update or doc fix is sufficient to establish momentum.

Is remote work allowed during onboarding?

Yes, but in-office attendance is expected for weeks 1–2 for compliance and identity verification.

Remote onboarding is permitted after day 10, but attending in-office for team syncs in weeks 3–4 improves integration speed.

Fully remote new hires take 22% longer to open first PR, based on 2025 internal data.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.