Remote vs In-Office: What New Grads Should Actually Pick

Every new grad job posting now has a little tag: Remote, Hybrid, or On-site. And you probably have a strong opinion about which one you want. But the honest answer for most new grads is more nuanced than "remote is always better."

The case for going in

This isn't a boomer take. Here's the reality:

You learn faster in person. When you're stuck on something and the senior engineer is ten feet away, you can ask a quick question and get unstuck in two minutes. Over Slack, that same question might take an hour to get answered — or you burn two hours going down the wrong path because you didn't want to "bother" anyone.

You build relationships that matter. The people you work with early in your career become your professional network for the next decade. It's a lot easier to build those relationships over lunch than over Zoom calls with cameras off.

You get more visibility. Promotions and interesting projects tend to go to people that managers actually know. When you're remote, you have to be much more intentional about making your work visible. In the office, some of that happens naturally.

The case for remote

Money. A remote job at a Bay Area company while living in Austin or Denver means you pocket a massive cost-of-living difference. Some companies adjust pay by location, but many don't — and even adjusted remote pay in a low-cost city often goes further than full pay in SF.

Focus time. Open offices are loud. If you do your best work in long uninterrupted blocks, remote is hard to beat. You can set up your own space exactly how you want it.

No commute. Getting two hours of your day back is real. That time compounds — over a year, you're getting back an entire month of waking hours.

The honest recommendation

If this is your first job out of school, lean toward in-person or hybrid for at least the first year. The learning acceleration is real and it compounds. You'll ramp up faster, build stronger relationships, and have a much easier time figuring out how a real engineering org works.

After that first year, when you know what you're doing and have a network in place, go fully remote if you want. You'll have the context to be effective independently.

The exception

If the remote job is at a meaningfully better company — better engineering culture, better comp, more interesting problems — take the remote job. Company quality matters more than location policy. A great remote job beats a mediocre in-office one every time.

Browse remote SWE roles or all jobs on Reblet to see what's out there.