|
|
|
|
|
|
by hitsurume
1100 days ago
|
|
|
I don't think your lack of success is because of the remote aspect. An interview is meant to see if your skill set can match with what the company is looking for and values. I don't know the React market and whether companies are getting flooded with candidates and can just swipe away people like tinder, but to me, your lack of success is either you are competiting against too many people, or they don't value your React knowledge / experience enough or don't think they can train you to get up to speed on how their tech stack works. |
|
|
Otoh I’m pretty confident I would have a job by now if I were open to non remote work.
Of course, I don’t do react work, but equally droll .NET work. I’ve had some interviews, usually with a few companies at a time with large dry spell in between, but a vast majority have been from recruiters reaching out with on-site or hybrid roles which would require a tedious and expensive move I don’t need right now. When I scroll through something like LinkedIn’s job board adding the remote filter significantly cuts out results, leaving a lot of low effort spam listings (i.e. recruiting firm posting the same remote job for every goddamn city the hiring manager could think of). I’ve had one interview for a remote role this go around and it was earlier this week, but I doubt it will go anywhere. I’ve been out of work a little bit longer than OP with A roughly similar YoE.
The other thing I’ve noticed is a lot more “specialist” roles than I’ve ever seen before and a lot less “generalist” ones.