binarytox1n
Joined 9 years ago
Joined 9 years ago
-I should speak to someone at the company before having to write code
-Interviews go both ways
-Coding problems should be appropriately sized, encapsulated, and reproducible
-Coding problems should not be real work
LeetCode is just what you get when you ask Software Engineers to solve the interview problem - they like showing off their chops so that's what you get. It doesn't need to be that complicated though. I know with about 80% certainty whether someone will work out based on how they solve that "SimpleProblem". The other 20% - just fire them if they don't work out. It doesn't need to be that hard. You don't need 100% certainty for a hire, you'll never get there. Just fire the ones that don't work out. You don't even need to feel bad for them - in this market they'll find another job by the end of the month.
Signed, someone who works at a company with a culture of sending blank meeting invites
It's easy do dehumanize a voice on the phone. Many people don't want to even use cameras for video calls. How much empathy do you have for a voice on the phone versus a human being you interact with in person on a daily basis?
I think the benefits of remote work far outweigh the work that needs to be done to maintain culture remotely, but it is a new challenge that doesn't have a lot of good understanding around how to make it work.
Rest assured their goal is full return to office despite the current "hybrid" model they are pushing, and you are not important enough to them to keep your job while being civilly disobedient.