With remote work, it's about what you can show for it, not just the words. What do you have to show for what you've learned?
That said, your advice is good in general: a portfolio is essential for junior developers who want to distinguish themselves enough to qualify for a remote position.
In this period, I learned a lot about remote collaboration and the importance of communication. A lot of people go on about tools like Slack etc. but in my experience, the phone is still the most important tool. And good desktop-sharing software like Webex, of course.
Eventually I got tired of contracting and took a remote job with a Very Large Silicon Valley Company. Crucially, to get this job, I needed to point to both my depth of experience and my time as an effective remote worker.
So in my opinion, to start with it's important to work a normal go-to-the-office job for a number of years and successfully ship software.
I'm revamping all my projects and my site based on some new things I've learned. I'll be sure to post some here for feedback this month. I don't want to embarrass myself in this community (done that before under my old username, not fun).
Thanks though for the real question I should be asking myself and the mindset I should have.
So, I started Moonlight [2], and started working for a variety of companies remotely on a contract basis. We're working to expand the marketplace, and are adding more projects every week. One of the factors that helps getting remote contract work is having a track record - meaning, at least 3 years of experience working professionally in technology.
About a month ago, I sold all of my stuff (I currently own a carry-on suitcase and backpack) and hit the road. I'm currently in Mexico City until the end of August, working about 10 hours per week through Moonlight to pay for all of my living costs.
[1] https://blog.staffjoy.com/staffjoy-is-shutting-down-39f7b5d6...
I wasn't sure about whether we have webRTC specialists, but I just queried the list of 1000 Moonlighters, and we do have a couple people who build real-time webRTC projects professionally. We can put you in contact if you fill out this form: https://www.moonlightwork.com/start
I'm a Sr software engineer, and was hired because I taught one of the co-founders while I was a teacher at a coding bootcamp.
We've hired one Jr engineer who I knew personally beforehand (a former student). And we've hired one mid-level engineer whom none of us has ever met in person.
My thoughts based on personal anecdotal evidence:
- Hit the job boards hard and don't stop. Persistence wins. Here are some great resources[1]
- 100% remote companies are the way to go. You don't want to be the sole remote employee (or one of a few) at a mostly on-site company. You'll be a 3rd class citizen. I've seen this numerous times.
- It is entirely possible to be a Jr engineer and get successfully integrated into a remote company. We've done it this year. We allocate some extra time for our engineers to further their own learning. We also do lots of screen-sharing sessions, etc.
[1] SO remote jobs: https://stackoverflow.com/jobs/remote-developer-jobs
Hacker News monthly job listings (search in-page for REMOTE): https://hn.algolia.com/?query=who%27s%20hiring&sort=byPopula...
The company downsized and they closed the office and I was sent to work from home.
I worked from home for 2 years as a senior dev. My wife reminds me that at first I wasn't happy about working from home. But after a month, remote is the only way to go.
I left that company and went remote for a startup for 90 days, and left before it imploded.
Now I'm stuck in a cube! Help me!
(also when applying to remote jobs, it seems that having remote experience is very beneficial.)
I'm a senior developer. Company contacted me about a position in the Bay area. I told them I recently moved across the country and asked if they would accept remote. They said that's ok (they had other remote workers and almost everyone is remote now). Phone interview the next day and an offer the day after. Flew out about a week after that for two weeks on-site. I go back for a week every now and then on-site. The irony is that I was looking for a full-time, remote position in the Bay area for years and less than six months after I moved, there it was.
Definitely recommend looking for companies with a remote culture. At another company, they flew me in for an interview, told me they wanted to make me an offer, then refused when I told them, as I had made it clear before the interviews, that I was not interested in moving back to the bay area. I've never been so speechless in an interview as when they asked me, "What would it take to get you to come back to SF?" and I knew the figure I wanted was nowhere near what they would want to pay. I also would recommend not doing any sort of take-home assignment for any company, but especially for remote jobs. That will be a lot of wasted time and the company might not even look at your work after you've spent hours or days on it.
I spent 2 years as a digital nomad while fulfilling that role. It was a bumpy ride as our 4-5 person team figured out the logistics and managing expectations and productivity. But now 3 years later, even after I got my US work visa we don't have an office, meet up in coffee shops a few times a week as 2-3 people, and each of us take a month to work remotely from a different city or country regularly for a change of pace at our convenience.
The biggest reason we support remote work is that once we learned how to make it work, not paying office rent and increasing our salaries proportionally was seen as a win-win all around.
I agree with that outlook and strive to reach that point one day with my side project. Travel, work, save, and serve all at once.
Having said that I have a colleague who is very good at the travel/work thing, so it's not that it's impossible -- it's just that I wouldn't recommend going into remote work with that as a near term goal. Spend a couple of years finding out how you work remotely before experimenting with some travel.
Thanks:)
The nice thing is, you can pull this off on a tourist visa.
Majority of the work I got via my website/blog.
A few months back I wrote a blog post how developers can have exposure to their work. Check link at:- http://blog.adnansiddiqi.me/5-ways-developers-can-have-multi...
I am now back in an office- I received an offer I couldn't refuse, and they unfortunately are hard-line, at least for the moment, about not allowing remote work on any consistent basis. I did receive offers that were ok with remote, and one that was a completely remote job. Unfortunately, they were all about 20% less than I was making before. Hopefully this job works out in the long term, but my main driver in taking it was to bank enough such that in all future jobs I can afford to take a pay cut (have retirement fully funded/become financially independent) and work remotely if I want to.
Anyway, to answer your question- Amazon supports remote work, as do a lot of consulting firms- NearForm, NodeSource, Joyent, etc. Auth0 is a fully remote firm as well.
My next remote position found me through my existing network. I was asked to do some work for an agency that they didn't have enough bandwidth to handle, and that eventually turned into a full-time gig.
I did it like that:
1. Saving money in my non-remote job where I worked for 7 years, so I didn't need to work for like 2 years.
2. Quitting my non-remote job, so I had time I could pour into working remote.
3. Doing some remote OSS work. Most OSS projects are remote anyway, people like free developer help, so this was an easy way to get into remote teams without much barriers like interviews etc. I also did a masters degree in computer science and had to do 2 projects, which were remote too. Never finished the master, lol, but still got that remote experience. Also I did a few projects, started doing all the coding at coffee shops etc.
4. Put my resume on online job websites that allowed me to say I only want remote jobs. Took me 4 months till I got a job, but I never wrote any company. Two companies wrote me and one gave me a job in the end.
5. Started working remote 2 years at a startup that was about 300km away from my home.
6. Quit the startup and started freelancing, which I'm doing for 6 months now.
---
I mostly learned about myself in the process. For example that the wish for remote work was just a wish for no bosses, more free time, etc.
I went through their rigorous interview process which was definitely harder than any I've encountered, but once in, I've had the best work experience in my life.
My clients have been amazing, Toptal handles payments for me so no problems getting paid, and they're always there to help me out. I chose my hours, and rate, and being a part of the community alone has taught me so much.
Prior to Toptal my only source for questions was Stack Overflow, since I'm self-taught. Never before had I discussed the new features of a Rails launch in a Slack channel, or discussed the best ways to handle my SQL queries.
[1] Toptal Referal Link: https://www.toptal.com/#contract-just-respected-software-arc...
Disclosure: Shortly after joining the Toptal Network, I joined their Core team. However, their community and company culture is definitely the best I've ever seen.
Personally I don't think being a junior remote employee is a bad thing, but a lot of the time hiring manages are afraid of hiring remotely.
I have worked remotely for a couple years now, and I found both of those jobs via Hacker News' "who is hiring" threads. A lot of companies on that thread are hiring for remote folks.
If you are in a situation where you are junior, but cannot work in an office for whatever reason, there are ways to dig into certain positions.
Companies with significant open source projects are a good place to start. If you can make significant contributions to a company's code via open source they might be more open to hiring you.
Be careful to not slave away for a company as free labor, but if you're learning and trying to grow your skills, some strategic open source development could be a good start.
lmk if you have any questions I can help with
http://gigworks.blogspot.com/2017/04/moonlight-work-for-soft...
I'll post a more full comment about the company above.
I was incredibly lucky and know it put pressure on them to find special remote opportunities or 'fly and build/fix it' type opportunities for many clients. I work in network security and networking.
my employer already knew me and was very happy with all of my work, otherwise I cannot see anyway I would have obtained this opportunity.
If you worked for company A at one point in your career and left on good terms, you might do some part time contracting for them from home. If you worked for companies A, B and C and you can swing the same arrangement you're now a consultant.
After my interview, circumstances changed and I needed to leave NYC, I told the company and they decided it would be ok for me to work remotely from Boston. Haven't looked back since, love being remote.
I was moving away from the city for personal reasons and discussed options with my manager/team. It helps if you've demonstrated your ability as a self-directed high performer.
I got out there and then I got lucky.