| I believe his point is you're part of the issue with interviewing as well. People design arbitrary trivia for people to answer and won't hire unless their workflow overlaps yours. For example, someone is hiring a chef for their restaurant: Q: "What is the difference between X local priduce supplier and Y local produce supplier?" A:"Where I work we had an exclusive relationship with X supplier so we never used Y supplier." Q: "Hmm ok, tell me the last fancy meal you cooked at home." A:"I spend all day cooking for my job. At home my spouse does the cooking because they really enjoy it." Q:"Ok thanks no hire." A:"In an executive chef with great credentials and experience. Do you want to ask me about and evaluate me on my actual job?" Q:" No thanks. I want someone who has the exact same experiences as I do. And I once spent a long time evaluating suppliers and found a better one. And I'm single so do all the cooking at home." And overall I don't mean to isolate you, but every time I see someone say they don't have extreme coding questions, they instead fall back to using the most non-representative arbitrary signals for decision making. |