|
|
|
|
|
by notus
2426 days ago
|
|
I was not a fan of Zapier's interview process. You're actually timed on your project and you have exactly 2 hours to do it. I was ultimately turned down after doing it because they said there were linting errors and they said I was using hooks incorrectly. My usage of react hooks was straight from the documentation and I showed my solution to several other people in the industry and they saw no issue with it. I was under the impression the purpose of those coding assignments is to deliver something imperfect but functioning and talk about how to improve it. The main problem I see with a lot of remote companies is that they seem to be overloaded with applications to the point they are making strange decisions about how to filter applicants. They also almost always require you to do some type of project which is a big commitment if you're applying to a lot of places. My best application experience apart from the one that hired me was Duck Duck Go. They pay you to do the project and I feel that is a far better approach. That way they don't have to feel bad about turning you down because hey you get paid, and you don't feel so bad about not getting it because hey you got paid. I ultimately got a much better position at a fully remote company than I would have gotten at Zapier so it wasn't a matter of me overestimating my worth either. I also found that a lot of the well known fully remote companies take forever to respond to you, gitlab, zapier, and DDG were the most responsive and communicative during the process, but I have some that I applied to 2 months ago that are just now emailing me to set up video screens. Startup companies tend to be the most responsive, I would get video screen invites sometimes within minutes after sending an email out. |
|