I'm definitely interested in working remotely. One of things I get a lot of mixed reactions about is the idea that you need to work in-office with a software team before even being considered for a job on a remote team.
I've got a decent amount of portfolio work, have worked for a company as their main "Web Dev" guy, but never on a team of people working on a product together.
Do you think this specific hole in my experience is preventing me from getting a Remote job?
Did you do the traditional office life before remote work?
Thanks for commenting Jack. To answer your questions:
I don't think that you have a "hole" in your experience. If you've been successful in on-site roles, then you're ready to be successful in remote roles. And that's regardless of whether or not you've been part of a large team. I've worked remote roles where I've been "on an island" and roles where I've been a part of large teams. If you're ready, you're ready. Good remote developers are adaptable.
I did personally start with an on-site roles; two of them to be exact. Once I moved to remote work I reflected on my time with both of the roles I had which were on-site and it blew my mind how much time was wasted on both. Commuting, lunch times, and meaningless meetings eat into one's day. Since my first remote role I've been far more productive.
It sounds like you've got about as much experience as I had before my first remote role, and I would encourage you to pursue one.
Founder of Microverse, a school for remote software developers that is free until you get a job. Former co-founder of TouristEye (acquired by Lonely Planet).
We train software engineers in 65 countries and prepare them for remote jobs, and 70% of the entry level developers we have trained are now working in remote positions as their first job. So no, experience working with a co-located team is not necessary, but it could definitely help since the mentorship is usually better (unless it's a remote first organization that knows how to build a strong remote culture).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm definitely interested in working remotely. One of things I get a lot of mixed reactions about is the idea that you need to work in-office with a software team before even being considered for a job on a remote team.
I've got a decent amount of portfolio work, have worked for a company as their main "Web Dev" guy, but never on a team of people working on a product together.
Thanks for commenting Jack. To answer your questions:
I don't think that you have a "hole" in your experience. If you've been successful in on-site roles, then you're ready to be successful in remote roles. And that's regardless of whether or not you've been part of a large team. I've worked remote roles where I've been "on an island" and roles where I've been a part of large teams. If you're ready, you're ready. Good remote developers are adaptable.
I did personally start with an on-site roles; two of them to be exact. Once I moved to remote work I reflected on my time with both of the roles I had which were on-site and it blew my mind how much time was wasted on both. Commuting, lunch times, and meaningless meetings eat into one's day. Since my first remote role I've been far more productive.
It sounds like you've got about as much experience as I had before my first remote role, and I would encourage you to pursue one.
We train software engineers in 65 countries and prepare them for remote jobs, and 70% of the entry level developers we have trained are now working in remote positions as their first job. So no, experience working with a co-located team is not necessary, but it could definitely help since the mentorship is usually better (unless it's a remote first organization that knows how to build a strong remote culture).