Currently hiring someone JS wise, to work remote. I don't care where you are, I care if you can deliver (i.e. frequent internet outages that mean you can't fork/commit changes = dealbreaker). My team is 99% remote, almost all conversation is via chat, email or PM tools.
So no, it won't necessarily cause you problems – you do need to be able to work and deliver on your connection, and you need to actually be good at what you do. That means you need to have a way to show me that you're good at what you do – for example, a well-kept collection of public github repos of modules, or contributions to major projects (and actual contributions, not "small readme changes to clarify example 3") is what I expect to see, and most certainly not a 'portfolio' of ToDo-style projects to demonstrate how you 'know <x> end-to-end' – that shows me nothing. I'd rather see a well-written Angular module than a ToDoMVC app that looks like it's been generated from a 101 tutorial.
Comments
Currently hiring someone JS wise, to work remote. I don't care where you are, I care if you can deliver (i.e. frequent internet outages that mean you can't fork/commit changes = dealbreaker). My team is 99% remote, almost all conversation is via chat, email or PM tools.
So no, it won't necessarily cause you problems – you do need to be able to work and deliver on your connection, and you need to actually be good at what you do. That means you need to have a way to show me that you're good at what you do – for example, a well-kept collection of public github repos of modules, or contributions to major projects (and actual contributions, not "small readme changes to clarify example 3") is what I expect to see, and most certainly not a 'portfolio' of ToDo-style projects to demonstrate how you 'know <x> end-to-end' – that shows me nothing. I'd rather see a well-written Angular module than a ToDoMVC app that looks like it's been generated from a 101 tutorial.
Hope that helps, and good luck!