Ask HN: How to make a career working remotely?

There are a variety of good sites that allow remote job postings. I'm looking now.

- https://stackoverflow.com/jobs

- https://angel.co

- https://remoteok.io/

- https://weworkremotely.com

Good luck.

Check out nomadlist.com

I have been working remotely for a few months now after spending many years in offices and I agree I am much more productive.

You might want to check out https://www.toptal.com

You might also like reading this book "Remote" written by BaseCamp founders. I read it last weekend and I think it's great.

Check https://teleport.org if you want to compare cities based on life quality data. Also gives you recommendations which cities fit best to your personal preference.

The fundamentals of being a highly effective and valued team member and employee are actually the same.

That said, perception is reality and being remote does add some friction to certain aspects of the job and the way the team works. If you take a proactive approach these can be managed or overcome, leaving you with just the benefits of working remote.

Things that come to mind: - Written communication: Crisp emails and IM that get the message across quickly. Know when to optimise for speed and for run.

Some things that come to mind:

- Verbal communication: take the time to speak with your team mates. Depending on the culture this may mean you never talk work by phone/Skype but you should still speak to everybody occasionally.

- Establish a rythym that works for you and the team. Be present and visible in ways that demonstrate and reinforce your reliability and commmitment. Just make sure you're adding value and not just making noise because you want to compensate for being remote (or not actually delivering).

- Respect other folks' time (and timezone, work arrangements).

- Actively contribute to the team and workplace culture. Don't just follow the lead of others but make suggestions and/or take the lead on initiatives when appropriate.

[edit: Formatting]

  "showing up" (via various communication channels) have more
  value at one of the places I worked than the actual work

  When you don't have anything to do, walk fast and look worried.
  Carry a notebook, it helps.

I own a small web-based company with six employees (plus myself), all of whom work remotely. When I hired our first employee back in 2009, we both worked remotely because there were only two of us. I always assumed that eventually we'd have to get an office, but I had no desire to do so, so wanted to put it off as long as possible. I don't recall exactly when, but at some point between then and now I realized that it was actually possible to run a business (at least one where the product is a website) entirely remotely. Obviously that's old news now, but it was quite a revelation at the time.

Anyway, from this experience I have a few thoughts. What type of company works well? My (obviously biased) perspective is that the best companies for remote work are the ones that are all-remote. While there are certainly exceptions, I've seen plenty of cases where companies allow remote work, but remote employees end up being second class citizens, perpetually out of the loop. If the company is all remote, that won't be an issue. That said, even a mixed team could be effective (with a bit more effort) if they have an excellent set of tools and processes.

Slack is huge, and has made our work much easier than it was before. I know there are other group chat clients that purport to do the same thing, but I haven't found any that do it as seamlessly as Slack. Similarly you want to see that they have good project tracking software (we use Pivotal Tracker, but there are a number of quality options), and that they have clear guidelines in place for how to use it. Some project tracking software is more opinionated, some less, but even with Pivotal being one of the more opinionated options, we have done quite a bit of experimentation and optimization over the years to make our process as effective as possible. Any team that does remote work well will have experimented with their processes for keeping everyone in sync, and they should be able to define the results of that work.

You can also learn a lot from the interview process. The most important element of an effective remote team is effective communication. Since that's what interviews are all about, it gives you a great insight into how they do things. If communication is poor during the interview - if they have you doing silly things like writing algorithms over the phone for instance - it's probably a warning sign. On the other hand, I'm not saying this is the only effective way to interview, but what we've found works well is to give candidates a few 'assignment' problems to work on, on their own time. We set up a repository for these and have them submit pull requests with their solutions. Then we review their code and make comments for discussion, just as we do when a feature is completed by a member of our team. The assignments are as minimal as possible so as not to waste time, while still giving a decent insight into how the person works. (A much better insight than a traditional interview.) Again, this isn't novel, nor is it the only way to do things, but I think it does demonstrate to prospective hires that we've thought this stuff through, and are committed to building an excellent team. I would hope to see something comparable from any hiring team, but I believe it is especially important for remote teams because good communication and effective processes are that much more important without the face to face crutch to fall back on.

Anyway, congrats on heading in this direction, and putting thought into the kind of company you'd like to work for. Remote work can be fantastic; These days I would never want to work any other way.

Years ago I got a holiday work visa for Australia. I was working for start-up at the time. I worked remotely for them for a few months, which with my savings, help me get situated in Melbourne. The start-up started struggling. They let go of several critical researchers. Eventually I was let go as well, but I had already found other contracts in Australia.

Years later I had a break in and decided to take off on a year sabbatical. It was the most amazing year of my adult life:

http://khanism.org/perspective/minimalism/

I've lucked into working remotely a few days a week for my current company. I actually find I'm more productive working away from open workspaces.

Still, I'm not satisfied with working as a developer. I've considered saving up for a year and then attempting to find grants or use crowfunding sites so I can take a break and work on my own projects for another year.

Check out Cisco jobs. The company is built around WebEx and working remote.

Source: worked here 3 years, enjoy working with a fully virtual team.

I suggest in spare time contributing to open source. This will build a good profile for prospective employers from future. As working remotely you may not be visible much in scene, however if you have strong presence in open source space, you will stay visible and prove how much you get done being self motivated. And any future company , most remote employers love self motivated, accomplished team members. And your online open source contributions helps validate that.

If you know what you do, pay attention to tennis. There's quite some money in tennis predictions. I know people who don't really know a lot about data mining and don't have a formal education in the field (and some of their 'math apparatus' sounds absolutely lame and laughable) who are making mid to high six figures in tennis. One guy even switched there from such an obviously attractive field as poker - a guy who already has an an excellent lifestyle from passive investments alone, and he's 32. If you can apply real data science there, and big data approach, mining a lot of data about tennis player, tournaments, surfaces, etc. etc., you can probably make millions. This isn't some temporary thing: bookies can't make better quality lines because they aren't offering odds reflecting real probabilities, they offer odds reflecting people's likelihood to bet on either side - and these are different things. And lines at betting exchanges are influenced by bookies, who make the bulk of the market, anyway.

I have been working remotely for some time now (years).

I am not doing it all the time as I like to be around people every once in a while (but having decent noise cancelling headphones for surviving those open spaces).

The key thing is indeed discipline.

Current tools support this fully. The level of proficiency with these tools directly affects the quality of the interactions. This includes their use by the other parties.

In 2014, I spent my whole year working on a project remotely, from idea to release and support. It was super nice and paid nicely.

It is important to be part of an open source community I'd say as it helps in asking trusted people about various things. In that regard, Slack is working well (as is Discord). Appear.in is also very useful.

One thing to look out for is remote-first companies, not just remote-ok companies. Zach Holman has a good post on this: https://zachholman.com/posts/remote-first/

If you're one of few people in the company working remotely (or worse: one of few in your team), you get cut off really easily. Remote practices won't be up to scratch (because most people aren't using them), meetings will happen in person and dialing you in will be a chore, and things won't work as well. You'll hear about major events by email that everybody knew about last week from office chatter. This isn't to say it'll be a disaster, but it'll be less effective, and less fun.

Companies where everybody works remote by default meanwhile are a different ballgame. Everybody understands how remote interactions should work, and that's what gets used to get everything done. People are good at using the tools and processes required to pull this off well, and the company will be better at managing solutions to the downsides of remote work (by flying everybody into a summit to see each other in person every 6 months, for example, or covering coworking space costs). You're no longer the great developer they want _despite_ you working remotely - you're now one of many people, all working remotely, and all working together on the same playing field.

I have spent last some years working on different projects, mostly remotely. What I have seen is that if you want to have a career in a specific company, try to find a company that has remote work in its DNA. That means, many or even most of the people are working remotely.

I have in practise seen that things usually don't work out well for the remote people, if the company has also a physical location where you have some "higher ranking employees" (project managers, architects, etc) as well as a certain amount of developers. If the company is not actively fighting against it, very soon you will end up with situation where things are discussed offline and those working remotely are left out. This can start very small. On the bigger meetings you hear certain things have already been de facto decided in the offline meeting. Instead on influencing, you are then just reacting.

This then leads to the most important thing for the remote worker trying to build a career: You need to fight this tendency to be left out. It is in remote workers interest that there are regular online meetings or gathering where everybody participates (even on daily basis). You need to gently remind people that you want to be involved in discussions as well. Be pro-active in Slack and try to push discussions to take place there. If the organisation is growing, push for quarterly or twice-a-year get togethers so that you have also physical contact with the new people. It makes a big difference for the remote communication when you've had a few beers with somebody.

About 10 years ago, I met for the first time someone who was working remotely. I hate commuting (As an employee, I have always lived close to my office) and at that point, I had decided this was what I wanted. It took me about 3 years to get to that point. Here is how it worked for me:

- Start freelancing. I started by negotiating with my employer to transform a full-time job into a part-time one. This is a great way to start.

- Accept what you find until you can get 100% freelance, but have a preference for remote work. Be ready to cut your rates to work remotely.

- Grow your network and reputation until you can have 100% of remote work at a decent rate.

Now we moved to a countryside we like with my wife, we have a house for half the price of an apartment in the city we used to live. I now say upfront to clients that I can only work remotely. I occasionally go to meetings in Tokyo (which is a bit less than 2h away from where I live) but Skype works most of the time.

Be available. Be reactive. Be ready to make mistakes that will cost you time and stress. Be ready to have some shitty clients that will bitch and won't pay. It takes a few years before you get to a level where the stress is lower than an employee job but it is worth it IMHO.

Lots of good information here already, but I also wanted to throw in Zapier's Guide to Remote Work[1]. It's very long but provides a ToC for you to jump to what's relevant to you, but the gist is that it discusses the pros and cons of remote work from both the employer and the employee's point of view.

You're probably learning many of the benefits of remote work already (but there might still be some tips for you in there to get the most of it), but it's also handy to know what the upsides (and potential downfalls) are for your employer(s) so you can better see issues from their point of view, make a more compelling case while interviewing for a remote position, and so on.

I definitely second the suggestion to look for remote-first companies. After interviewing around and getting through a half dozen interview processes to finally get an offer "as long as I was comfortable potentially relocating later if remote doesn't work out", I ended up completely omitting all companies that weren't 90+% remote from my job search. When you can actually work remotely, the whole world is your job market -- you can afford to exclude companies that are on the fence about remote work.

Good luck!

[1] https://zapier.com/learn/the-ultimate-guide-to-remote-workin...

I've been working 40% remote (two days from home, three days in office) for just over twelve years. I'm employed as a developer, and I negotiated this arrangement when I joined the company. I have no experience of freelancing or self-employment.

As others have said, the key to making it work is trust and communication. Employers/management need to know that you are being at least as productive as you would be in a conventional office environment. And your team needs to know that you are making a fair contribution to getting things done. Each person in those groups will have a different default belief about what you are doing (working or slacking) in the absence of evidence to the contrary. Understand that, and use communication to address it.

So communicate appropriately. Some people suggest being super proactive on communication as a way of visibly signalling the effort you are making. I'm suspicious of this in a developer role, as you can end-up being thought of as noisy and self-promoting. Recognise that the way you communicate will probably need to change over time.

Find tools that work for you and your team, but don't get too preoccupied with tool selection. Its not the main issue.

Assuming an employer is open to remote working, I'd say that you need to: a) show a realistic understanding of how to make remote working work, and the problems that can occur; b) demonstrate that you are trustworthy and can work independently; and c) demonstrate that you can communicate effectively. This is going to be easier for an existing employer than a prospective one. being familiar with popular tools like hangouts/slack/skype will help.

Scott Hanselman [1] has some useful things to say about remote working. He's a PM at Microsoft.

Finally, recognise that it might not work for you. You might get lonely, or marginalised/overlooked, or just want a change. Don't lock yourself into one way of working for ever.

[1] https://www.google.co.uk/#q=remote+site:hanselman.com

I have the following rules for working remotely. It's more for contractors, so may not be directly applicable to people who work remotely for an employer.

1. More than one customer. Even if you're earning less money, two badly paying customers are better than one well paying customer.

2. Invoicing is always prompt, and payment must also be prompt. Walk away from anyone that holds onto payments.

3. Be scrupulous with the time you charge out, and be aware that if you do this, you'll find it takes 4 hours of a day to do two hours work. Use rescustime or timesnapper to monitor where your time is actually going.

4. Never turn down work.

Don't know if these are especially good rules, but they work for me. I'm on about my 5th year of being a remote worker.

You might find this interview with data scientist Tim Hopper interesting. He works remotely and comments on tools his company uses to enable remote work.

http://computationalimagination.com/interview_tim_hopper.php

I've been working for a 100% remote company for 4 years now, and I'd advise that you market yourself as someone that has done it before. Remote work is a skill set - the discipline to work a full day but not overwork, knowing the tools for communicating without seeing your coworkers more than a few times a year, and having built a space and culture in your home and family to be productive without letting the home life disrupt the work... while at the same time, sometimes you do run off for lunch with your spouse or go see a kid's activity at school, and make up the time later.

There is a whole different work ethic and discipline involved, and being someone who already knows all this is a value to a remote company. Because even though everyone can learn and figure out these details... not everyone ends up being good at being remote, so a successful history is a nice bonus when hiring.

I think everything boils down to finding an actual demand for your skill set. As long as some organization or an investor has a real problem to solve and you could convince them that you really have the ability and necessary training and experience, then it doesn't really matter how do you work and from where. You could always frame a contract not for hourly basis but on completion of the prototype, milestones, whatever you like.

Basically, you should imagine yourself as a specialized company doing sub-contracting in ML.

Finding a real demand and securing a contract is much harder than doing actual coding and modeling. There are literally thousands of guys who are smart enough to apply ML, especially now, when it became mainstream.

PhD is, of course, a huge advantage in the world of pointy haired bosses, HR and paper pushers. With it you, probably, are looking for a very high hourly rate instead of subcontracts. In this you probably would fail, because people who are willing to pay high hourly wages needed certain rituals to be performed publicly in return.

I have been in software development for about 8 years and I have worked remotely for 4 of those. My opinion is that there is no way to have a fully remote-only working career in software. It is a perk that you may be able to get in some situations, but it is never guaranteed. Executives have this image in their mind of developers swiveling their chairs around and bouncing ideas off of each other, or sharing key insights randomly at the water cooler, that they just cannot give up (even though I believe it is a complete fiction). They have many names for this, like "synergy," "collaborative environment," etc. It's a specter that will haunt you as long as you choose to tele-commute.

I've been remote working for 12 years. My opinion as to a successful remote working relationship is as follows:

  - Trust. You need to build it on both sides. Your employer
    needs to trust you to deliver what they expect. You need
    to trust your employer to build their team to include you 
    even though you're sometimes not so visible.

  - Space. Get yourself out of the home office and into a 
    local coworking space. You'll thank me for it, otherwise 
    you'll go slowly crazy at home.

  - Daily contact. Make sure you have daily contact with 
    other members of your team. If you're Agile, then a daily 
    standup by video feed helps people to remember you exist!

If you are skilled you can find it. A couple thoughts:

1 - Go where it's the norm.

2 - If you can't follow #1 then be attached to your desk and phone. People won't give you the benefit of the doubt if you take 30 mins to return a call or email.

3 - Do what you know. It is tougher to learn on the job remotely.

4 - Deliver tremendous value and make sure people know it. People need to know why you're invaluable.

There's some great info/thoughts in this thread already. I'd add that different people would define "Successful career" differently.

If what you're after is essentially setting yourself up for being a "valuable resource no matter if onsite or remote" then as long as you're on top of your game tech chops - wise and there are companies out there willing to allow ppl with your skillset to work remote - you'll be alright.

For some ppl "successful career" entails getting "more responsibility" in their roles which is basically corp speak for getting into management/team lead positions. If that's your goal then your best bet would be looking for a "remote first" type company where everyone/most everyone is remote. Sure, you don't have to do this right away but keep in mind that it's very rare for a distributed tech team to be hiring external team leads/managers etc.

One other thing I'd add from my personal experience. Teams that aren't remote first but are looking for remote folks out of necessity (as in lack of "local talent") are not only more stressful to be on if you get the gig - they also tend to place the bar higher for remote candidates so one- get ready for hackerrank type challenges and two - have a github profile you won't be ashamed to share with the potential employer :)