3 ms·
Hiring teams that are just "getting their feet wet" with remote workers are going to be more hesitant. When there is an in-company precedent for what remote wor
by mccolin 10y ago
Hiring teams that are just "getting their feet wet" with remote workers are going to be more hesitant. When there is an in-company precedent for what remote work is like, I find them to be more open.
For me, making the transition from on-site to remote work was difficult. Like any job skill, it's something I had to be able to demonstrate proficiency and/or history with before I could land full-time, remote employment exactly where I wanted.
- vonmoltke 10y agoThat creates a chicken-and-egg situation, though, since it is not a skill you can develop on your own. There are a set of skills (remote work, TDD, pair programming, Agile, etc.) that, almost by definition, you need to do professionally to become proficient at. If all the professional gigs expect you to already be proficient, you never get there.
- 8draco8 10y agoI never worked remotely but I don't think it's hard and I want to do it in near future. The way to do that is to find a company that is open for new ideas. Start working on full time office job and after month or two if your job position allows for that, ask for day or two in a week of remote work. This will allow you and the company to test that solution and check it it's working for both of you.
- mccolin 10y agoLots of finding work and vetting skills is actually a chicken or the egg problem. You have to find the places that are willing to offer opportunity with less proven background in order to open the door to bigger opportunities. This is like any job skill.