Surviving Your First Software Engineering Job

The first job is where most of the real learning happens — and also where a lot of new engineers make avoidable mistakes that set them back for months.

The First 90 Days #

Your only job in the first 90 days is to build trust and understand the system. Ship some things, ask a lot of questions, and be the person who does what they say they’re going to do.

Resist the urge to immediately propose sweeping rewrites or “improvements.” You don’t understand the context yet. What looks like legacy code to you might be a carefully maintained system with a very good reason for existing the way it does.

Week 1–2: Orientate #

• Set up your dev environment and get something small shipped
• Learn how the team communicates (Slack channels, standup norms, PR review expectations)
• Figure out where the actual decisions get made — it’s rarely in the meetings you’d expect

Month 1: Start Contributing #

• Take on well-scoped tickets from the backlog
• Ask questions aggressively, but try to make one real attempt at finding the answer yourself first
• Start building your mental model of the codebase

Month 2–3: Show Ownership #

• Look for problems nobody has put a ticket on yet
• Start doing code review, not just receiving it
• Make your work visible without being annoying about it

The Things Nobody Tells You #

Your Technical Skills Are Enough #

New grads spend enormous amounts of time worrying about not being technically good enough. In most cases, if you got the job, you’re fine. The things that trip up new engineers aren’t usually algorithmic puzzles — they’re soft skills: communication, asking for help at the right time, managing expectations.

Find a Mentor, Formally or Informally #

Most companies have formal mentorship programs. Use them. If yours doesn’t, identify a senior engineer on your team who seems to enjoy helping people and ask them to have regular 1:1s with you.

Your Manager Is Your Most Important Relationship #

Invest in this relationship from day one. Understand their priorities. Communicate proactively. Ask them regularly: “What could I be doing better?” Most managers are shocked when someone actually asks this.

Slow Down to Speed Up #

The instinct when you’re new is to move fast to prove yourself. Often the opposite is more effective. Taking time to read docs, understand context, and ask clarifying questions before diving into code leads to better outcomes and fewer reverts.

When You’re Struggling #

If you’re struggling — technically, socially, or emotionally — tell someone. Your manager, a mentor, HR. Early intervention is almost always better than white-knuckling it until things collapse.

Most companies have dealt with new engineers struggling and have support structures in place. You’re not the first person to feel lost.

The Bottom Line #

Show up consistently. Do what you say you’re going to do. Communicate when you’re stuck. The technical part will come — the professional habits are what make or break the first year.