|
Well in my case I put a massive amount of effort into the technical portion of my interview. I was given a week, as they knew how busy I was. I spent a good 8 hours on it, and went above and beyond. Instead of a simple working SPA, I produced a full working system with full UI, REST API, 100% coverage, rolling data import, containerisation and deployment scripts for all services, pseudo-branding, documentation, GitHub organisation with repo per service, and to top it off, deployed it to a $5 droplet and provided credentials. 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.