5 ms·
Someone called this to my attention in terms of making engineering interviews more fair, and there are some overlapping points, particularly with not biasing yo
by thedracle 5y ago
Someone called this to my attention in terms of making engineering interviews more fair, and there are some overlapping points, particularly with not biasing your interviews based on tooling:
https://faircoding.com/interviews/ https://faircoding.com/interviews/
- Richard_Kayala 5y agoWebsite and person look fake AF to me. Let me prove it: "Requiring engineers to dress in any specific way." "I've been writing software for over 20 years. " Old habits die hard. In 1995 you would still be wearing a collar shirt to work. So either he's been amazingly stubborn about the habit or has never worked corporate for a significant amount of time in the old days. "A huge part of software development is seeing how things are done, and then continuing the pattern. " A good senior engineer would have added "and breaking that pattern too." "Success criteria is hidden" Bullshit. Companies standardize their loops and ask their interview group to grade along dimensions and make people justify their decisions to other engineers. "Suppose you have a developer who has written code in 7 different languages spread over 20 years. ( me ) Average length of time coding any specific language then is 3 years. Now suppose you have a developer who has written code in only one language for 5 years. Which developer do you think will impress more at a coding interview? See the problem?" No I really don't. Because if someone says they know Java, they better know the damn in and out of it. I would love to see them talk about how JVM garbage collects as well and other beneficial APIs. You can either know 7 things poorly or 1 thing very well. Any competent engineer would know that persistence and master of 1 thing would mean an insane depth of knowledge: a depth that can't be replicated easily and would make a engineer highly valuable. "The skills required to create effective software that makes the company money are very different from those skills that are used to pass a coding interview. " Again, bullshit. What are you and your 7 languages over 20 years going to do make the company money? How is that Lisp, Haskell, and PHP knowledge working out for you? "Senior engineers who have been writing code for 10+ years may either hate coding interviews or simply be terrible at them because they have focused on delivering business value" No, because there is something called the System Design interview that they would have a better affinity for. In fact, at the Senior Level, its 50/50 (or 30/70 depending where you go) weight between DS&A and SD. This guy is just plain uninformed. "They are a form of random chance" If its truly random, then you should see an equal mix of competent and incompetent engineers hired at all engineering levels. If this was the case, why aren't people being fired en mass all the time? If it was random, then its equally likely that shit engineers would get hired at the same rates as good engineers and you would be forced to believe that Google is full of incompetent morons that magically ship amazing products. I would be stunned to learn that a turd flinging monkey could keep Google Search Engine online. I could keep going but bottom line: this guy is a fucking fake who would suck 2 dicks to get into FAANG in an instant and has no idea what coding interviews really entail.
- whynaut 5y agovery pedantic here. not sure what you mean by fake either, the author has commented quite a bit in this thread
- Richard_Kayala 5y agoThe author of https://faircoding.com/ https://faircoding.com/ is here? You must be in the wrong thread sir.
- disgruntledphd2 5y ago> this guy is a fucking fake who would suck 2 dicks to get into FAANG in an instant and has no idea what coding interviews really entail. The OP is here, is a part of the community and you should at least attempt to be decent to another human being.
- Richard_Kayala 5y agoSure, I'll engage with OP. All he needs to do is reveal his identity on the website. After all, a majority of his points are based on his own personal experience so I certainly hope that his own personal experience isn't made up.
- disgruntledphd2 5y agoBut he (or she) did. They engaged both as coscreen and with their personal account, and called it out clearly.
- thedracle 5y agoI know who the owner is, he isn't fake and reached out to me personally, but I didn't feel comfortable doxing him without his explicit permission. I don't necessarily agree or subscribe to all of these points, just found it interesting there was someone very passionate about the process of software engineering interviews who had made an entire website dedicated to it.