DEV Community

Cover image for First job in software development industry. Remote or Onsite?
Nikos Koikas
Nikos Koikas

Posted on • Updated on

First job in software development industry. Remote or Onsite?

Most of the time remotely jobs have flexible working schedule. You can work at night or early in the morning.

But, how would an entry level software developer react to a problem without help?

Top comments (6)

sudiukil profile image
Quentin Sonrel • Edited

I would recommend on site for a few reasons:

Working on site is "standard"

It's still the "norm" and chances are one day your will have to work on site (while remote is often optional), so you might want to start your career with the "standard" way and then make the switch when offered the opportunity.


For an entry level developer, on site is better for being mentored and helped when needed. Instant messaging and video conference have a lot of limitations in that regard, especially if you work "non-standard" hours.


Working remotely requires a lot of commitment and seriousness, more than working on site. When you work on site, you are at work, you are there for working, surrounded by people working. At home, you are just at home, your mindset will be different and it will be harder to keep focused. Since it's already hard to get into the "working mindset" when you are a beginner, mixing the two is not the greatest idea.


Working remotely means that most of the time you will have to solve problems alone and that requires experience, which you won't have at first. Even if you can ask for help online (Slack or wathever) to your colleagues, as I said in my point about mentoring, it's just not as efficient as a physical presence.

Also "experience" doesn't just mean "coding experience", experience with your job and your company is just as important. Since every company is different and has different ways of doing things, you'll need to get experienced with that also, and being remote will make that harder.


This answer is already too long so let me conclude by saying: working remotely is not a bad idea at all and it has a lot of perks, but I don't think starting remotely is a good idea, I believe on site is best for an entry level for all the reasons above. That being said, once you are experienced enough, switching to remote work can definitely be worth a try if that's what you want.

nkoik profile image
Nikos Koikas

I think you have substantiate your answer, but a question then arises.

Why do companies open remote positions for entry-level developers?

sudiukil profile image
Quentin Sonrel

I'm no company owner but my two guesses would be:

  • Money: it's my understanding (I might be wrong) that remote workers (dev or not) are less expansive to a company than on site ones. Mainly because the less people you have on site, the less "site" you need... "site" being the premises, the hardware for it, etc... which all costs a bunch of money.
  • Convenience: a remote worker can be, on average, further away of the company's site than the typical on site worker who needs to go there every day, so by accepting any worker remotely (entry level or otherwise) they have more candidates for the job.

Also, the year is 2018, working remotely is fashionable and modern, giving this opportunity to your employees might also be a way to be more attractive than the competition.

Once again, these are just my 2 cents, I'm not an expert on the matter.

Thread Thread
ben profile image
Ben Halpern

We've done the entry-level remote thing and would favor in person for this kind of role in the future for most of the reasons you've outlined.

However, we'd also do the remote thing again. We learned a lot about the pitfalls and would approach it with more awareness this time.

xngwng profile image
Xing Wang

I think for senior developers perhaps can work more independently/remotely.

For entry level developers, most likely you'll need to learn from others to create production ready code. If you work remotely, even with slack or video conference, it is just not the same.

From the employer perspective, without a lot of guidance and feedback, the software delivered from entry level developers almost isn't usable in production. And it is really hard to give guidance over the chat or video calls.

It will just create frustration from both sides.

In fact, even for senior developers, if there is an existing product, I would still highly recommend at least for the few month to work on site, to get ramped up on processes, code base, roles of other engineers (who is expert in what) etc.

rhymes profile image

I might be wrong but I think it's worth it working on site at first. It's easier to be mentored and to understand how companies work. After all, on site jobs are still the majority :-)

Then when the junior devs gain experience they can make their own mind, maybe ask for some flexibility regarding presence in the office or go work for a fully remote company.