You Can’t Look for a Job from a Remote Location – It Doesn’t Work
bothsidesofthetable.com
bothsidesofthetable.com
Two years later, I got laid off due to economic factors. This led to getting a job in the Bay Area. I had multiple phone interviews and a short programming test before getting the job, but I didn't have to fly over to California once.
The author does raise some good points, though. While I obviously don't have any proof, I have always suspected that some job offers were passed over me due to my location at the time, especially while in Puerto Rico (two prospective employers strongly suggested that I get a visa to work in the U.S. - ignoring the fact that Puerto Rico is a U.S. territory, making me a U.S. citizen). So while I would say it's a bit more difficult to go job-hunting in remote locations, it's definitely not impossible.
It would also be foolish to move to somewhere like the Bay area or Los Angeles where the location of your new job could result in a 90 minute commute both way. (e.g. you move to North Beach and land a job in Palo Alto). Moving sucks. Moving twice sucks more :)
What you must be prepared to do however is fly to city XYZ at a few days notice, and potentially on your own dime, for one or more interviews. And if you do land that job, be prepared to start the next week.
Yeah, crap, I made the mistake of not being prepared for that when I moved out here (Cambridge area, MA). I interviewed, they wanted me right away, so I had to literally pack my things and get my ass out there before I could do basic stuff like look for a place to live. I had my laptop and a suitcase full of clothes and other stuff and that was it.
Personally, I'd be wary of a company wanting to hire me without having to meet me in person. Inversely, if I'm running a company, I won't hire somebody I haven't even met.
I asked one of the higher-ups this same question after being hired, and they said that they scouted my blog, Twitter and Github accounts, among others, and with what they heard over the phone, they felt I was a really good fit in their company. Had I not taken the time to build my online persona, I doubt I would've had been hired. This doesn't just apply to job-hunting in remote locations, but nowadays it should be a big part of it.
I specially carved out “young people” from my argument. Most young people are infinitely mobile. Also, I need to carve out mid-level developers. They tend to be fairly mobile. Finally, I should carve out international people. I talk about that in the comments.
So that leaves senior execs: Directors, VP, CEO types. This is the group I’m mostly talking about.
...in other words, this article is specifically targeted at well under 1% of the viewership of HN (I suspect we have many aspiring "CEO types" here, but mostly they are building up companies from scratch, not attempting to get inserted into them once they're up and running), and explicitly excludes the rest of us from this advice.
I was leaving MT and thought it'd be great to move to the Bay Area but figured I couldn't afford it without a job lined up so I decided on Denver. While in the process of moving, a job opportunity came up in the Bay Area (I wasn't looking but it's the exact job I wanted) so I pursued it, not thinking I would get it but for the interview experience. Well, while trying to figure out what area of Denver to settle in I got a job offer. I repacked the U-Haul and headed West. Now I'm here and loving it!
I think it's silly people still say things like "You can't do this, it'll never happen and here's why." It might be unlikely but "never" is a pretty strong word.
What type of position does he think his readers are looking for?
That presumes that you already know where that job is. The rest of us have to do some remote searching and be willing to move when we find it.
However, he still has a good point, which is that you're better off (more likely to get a better job) if you move first. That leave room to succeed without moving first.
I got a job in Boston from Toronto, and then one in New York from Boston. Getting flown out to Silicon Valley or Seattle for the bigger companies is also pretty common. It's even easier when you have a friend working in another city. The best places to work don't care where their candidates come from if they're good and willing to move.
I think the guy who wrote this article meant to say that it's easier to find a local job. But he's seriously out of touch with reality if he believes it's really hard to find a job in another city.
That being said, the bar is always higher (even if unconsciously) for candidates that require visas or relocation. If you're good, however, that's not a worry.
(1) OTOH, Wernel Vogels had certainly been relocated from Cornell to work at Amazon. I'd definitely say he has "the" job. One anecdote doesn't make a counter example, but this example shows that if you're great, you can find a job anywhere.
It was a successful process for the two most often cited reasons: timing and connections.
I was specifically targeted by someone who followed my work (blog/twitter/github)..which means I didn't have to work so hard to sell myself on technical merits to people half-way around the world.
Also, personal changes in my life suddenly made me mobile for the first time since graduating (a decade ago). Had the recruiting happened a few weeks earlier, I would have said no.
In most of Europe asking questions about where someone grew up or family connections to the locality can be considered as discriminatory (against married people, against people who grew up in the "wrong" neighbourhoodm etc.)
Enough people have that kind of information out there on the net nowadays that I'd expect the company to be able to find it for most candidates.
If it's the asking that's issue, then, sure, Facebook/Twitter/whatever is fair game (although I'd be curious to learn what a judge would say on the matter). If it's the discrimination itself, however, then I'd expect the same rules (i.e., don't touch it with a ten-foot pole) to apply.
Personally, if I were doing hiring, I'd go out of my way to remain as ignorant as possible of any candidate's personal status, simply as a "covering my ass" tactic. That would (of course) include avoiding the standard verboten interview questions, but I would take it a step further and actively avoid looking them up on Facebook or whatever. If I avoid ever learning whether or not they have kids, I can't be accused of not hiring them on account of of their family obligations.