| I'd love to serve some bay area companies, but I'd really prefer to not live there. None of the companies I've spoken to so far have any interest in remote help. One west coast company has interviewed me. The company recruiter sent me like 14 "how to prep for tech screens" links and recommended I check them out days before the actual tech screen. I'm on a job right now so I don't have time to be doing that sort of thing so I didn't prep. It made me expect I was going to have to implement a BSP decompiler with a hand tied behind my back. The guy who called me allotted 50 minutes to solve 1 problem "two if I finished the first early" on collabedit. I finished both in 6 minutes. I'm a good, experienced developer but I'm no genius. Their tech screen was so ludicrously easy it made me wonder what the current standard is for developers. After I finished the guy said "huh I normally don't have to end these early. Great I guess." I pressed him a little and he went on to say his questions had done a great job invalidating candidates. Most people couldn't do it. It's pretty beguiling since my midwest salary demands would be peanuts compared to my west coast equivalent. There'd have to be >60% remote-related productivity penalty for it not to be a no brainer to hire people like me. The last few years has taught me that job seekers and dev seekers both have a hard time connecting. |