DEV Community

Cover image for Your Guide to Landing a Remote Developer Job and Securing the Bag
Gabriel De Almeida
Gabriel De Almeida

Posted on • Originally published at sixfiguresengineer.com

Your Guide to Landing a Remote Developer Job and Securing the Bag

Landing a remote developer job and being paid well for it used to be an elusive and hopeless endeavor a few years ago.

But we now live in a time where getting paid to work as a web developer using React, a mobile developer building with Flutter, or a back-end developer programming in Python and even Java, from the comfort of your home, is a real possibility.

One that I seized and will most likely never leave!

  • I get to set my schedule so long as my work gets accomplished
  • I don't have to fake that I'm working or being productive, which leads to resentment and a vicious never-ending cycle
  • I don't have to commute
  • I get to spend more time with my family
  • I get to exercise more often
  • Sorry if I'm rubbing it in

Happy gif
via GIPHY

But how do you land one of these sweet gigs? How do you convince a company that you're worthy of such trust?

I'm going to assume that you have spent some time learning the fundamentals of programming, and if not, I recommend that you check out my article on how I became a software engineer.

Landing a remote software engineering role is not much different than a work-in-the-office-and-hate-every-minute-of-it position.

And no, you don't need to have years of professional experience before working remotely. In fact, my first software engineering job was fully remote.

The most important things to keep in mind are:

  1. Where to apply
  2. How to interview

Where to Apply

Knowing what companies to apply to regarding a remote software engineering position is of the utmost importance.

Think about it, imagine if 99% of your company worked out of an office and you and a few other people were the only ones working remotely. Imagine if you were the only one in your team working remotely!

You might not think that matters, but it does.

That means that that company does not possess a remote culture and is most likely not set up to handle remote employees in the best way.

You're starting from a losing position. All of your coworkers get to stand by the coffee machine and socialize, and when they're working, your manager sees that they're working; you're nowhere to be seen.

I've heard terrible stories from remote workers in such companies where their team members and managers don't speak to them or forget about them altogether!

Talk about making some dough on the low!

Cat making dough
via GIPHY

That leads remote employees to feel obligated to fight for attention, recognition, and proof of effort.

Stay far away from such places. You don't want to work at a company that is "open" to remote possibilities or is "thinking" about it.

You want to work at a company that is either fully remote or has a track record of being remote-friendly.

Why?

Because you won't have to overwork yourself in hopes of proving that you're doing just as much as your colleagues.

Because you want to be recognized for what you do and want to be promoted for all of your efforts.

Whether you're a front-end, back-end, or full-stack developer, your goal should always be to challenge yourself and grow. Working at a place designed to sustain a thriving culture is where you'll be able to excel.

My recommendation of places to find such companies are:

Don't worry. You'll find more places than you'll be able to apply to!

Just make sure that when searching for companies, you filter by remote or remote-only companies.

How to Interview

Monkey thinking
Photo by Juan Rumimpunu

Remote companies don't usually interview any differently than an in-person company. Still, they look for certain qualities and experiences to see if you're someone who can handle such an environment.

So it's essential to keep in mind as you're introducing yourself or answering questions that they're looking for that.

How might you prove that you're able to work in a remote capacity?

Well, if you've worked remotely before, make sure to state that.

If you haven't, maybe you've built a project with friends that you can talk about. Or you've contributed to an open-source project. Orrr, you're part of an online community that you help maintain.

Maybe there's an even weirder thing you've done that you think would show that you'd be able to handle working at a remote company. Talk about that! Unless it's too weird... Then it would be best if you tweeted at me @gabedealmeida so that I and the whole world can be the judge of that 🤪.

And if you really can't think of anything, consider building a project with friends or contributing to an open-source project.

I mean, you don't have to do either of those things, but it's easier to convince your interviewers, who are limited on time and are often just listening for some keywords, that you're a fit if you have previous experience.

The point here is that there are ways to prove that you're someone who can thrive in such an environment.

Bonus

Succeeding at a remote job is also vital. So here are some tips to help you do just that:

  1. Be polite
  2. Be punctual
  3. Air on the side of detail
  4. Be thorough in explaining what you're working on, what you've accomplished, and what you need assistance with
  5. Do great work

Summary

Bag of money gif
via GIPHY

To land a remote developer job and secure the bag, you have to first make sure that you're applying to the suitable types of companies to succeed and not live in a constant state of stress.

When attending your interviews, you have to go in with the understanding that your interviewers are trying to assess whether you're someone who has any previous remote experience or can fit in for whatever reason.

But what do I know?! I'm just some guy... 🤷🏻‍♂️


Thanks for taking the time to read this article! I hope that you found it helpful.

If you did or didn't, give me a follow on Twitter! I always try to share as much as I know or what I'm currently learning. 🤟🙂

Discussion (0)