Started on site, early on asked for remote which wasn't possible at the time, circumstances changed and I asked again. It felt like forever it was in the hands of higher-ups but after two years fro my my start date with the company I went on a 3 month remote trial.
Trial went well and I'm now permanently remote.
Ask, provide reasons why you should be permitted to work remotely & if denied ask why so that you can change and try again.
Edit: In this situation, he was hardly local first, given the short time between his hire and his moving far away. All of which is to say I agree with the poster I replied to.
> - You need to demonstrate, without a doubt, that you can/have worked autonomously, that you can/have been self managing in the past
Do you simply state your experience of having worked autonomously, or having self-managed? If yes, how would you still stand out, because it's like every other candidate also states the same thing "Oh yeah, I require minimum supervision, always get my sh*t done on time by self-managing".
and
> that you provide a better bang-for-the-buck than anyone else who has applied
This is even more vague and fuzzy. How do you demonstrate that you "provide a better bang-for-the-buck than anyone else who has applied" during a phone interview? References?
This is what you'll be up against when interviewing for good remote companies. I work for a remote first company, not just a remote friendly company, so the competition really is stiff.
With the wage I went in for, it was a no brainer. Was hired days later, and it's been the best job I've had so far.
As a remote worker, you really do have to be a self-manager, you're trusted by your team – in the same way you trust your team – to get shit done.
Another thing I did was ace the interview. I went into it with the confidence to present myself as I knew myself, as I knew they didn't. I switched the interview around and interviewed them, and in the end, we were all laughing.
What I would say is "show, don't tell".
In 8 hours that's very impressive. Thank you for your feedback. I wasn't aware that remote companies gave coding assignments, but it makes sense.
Yes, and you back that up with evidence of a project completed, references backing up their positive experience, etc.
I only contract remotely, with no intention of taking regular employment any time soon, and I still get asked if I'd like to join the team full time as a remote fairly often. Not because I'm so amazing but because they don't need to guess or take risks, they already have proof I can do it successfully for them.
https://www.google.com/search?q=average+programmer+hourly+wa...
I clicked on the second link:
http://www.salaryexplorer.com/hourly-wage.php?loc=18&loctype...
Maximum: 698 BDT / hr
Average: 326 BDT / hr
Median: 279 BDT / hr
Minimum: 58 BDT / hr
Maximum: $8.6 / hr
Average: $4.0 / hr
Median: $3.4 / hr
Minimum: $0.72 / hr
I would say it is easier to become remote if you are already working with a company that knows you. As for establishing such a relationship, I kind of agree with codingdave's advice in this thread.
Competing on price or selling yourself to the lowest bidder is a losing proposition.
That said, most of the best Indian devs aren't making that money remotely, they're making a lot more (or at least, I've seen them getting paid a lot more).
I got contacted and worked remotely through Hacker News and, although it didn't pan out (I wasn't a good fit) it was a great experience and I met really good people from around the world.
Not really. There aren't many companies who are considering both American and Indian remote developers for the same positions.
Well paying remote jobs tend to have time zone constraints, and require better English communication skills than the average Indian developer has (there definitely are Indian developers with excellent communications skills, but they aren't average).
People think that because they are out of the office that politics doesn't affect them and they don't need soft skills. But communicating effectively is even more important in remote work because of the inherently lower communications bandwidth.
Other times, particularly if the project has complicated architectural requirements, it's too hard to get the night shift on the same page a super the parent.
Assuming all of your demonstrating points are just from previous employment?
Going remote isn't as easy as what many devs are probably accustomed to, especially if you're new to the game (as the tech hiring market has been :fire:).
If you're going to go remote, you need to realize a few things:
- You're competing against waaay more candidates. You need to stand out, not just be another warm body.
- You need to demonstrate, without a doubt, that you can/have worked autonomously.
- You need to demonstrate, without a doubt, that you can/have been self managing in the past.
- You need to demonstrate that you provide a better bang-for-the-buck than anyone else who has applied
Source: Working and hiring remotely for the last 7-ish years.