|
|
|
|
|
by DethNinja
2104 days ago
|
|
Only thing those questions show is how irrational the software engineering companies have became in the USA. This does not bode well for their futures as well. As an engineer who implemented/architected SaaS applications, I cannot take these questions seriously at all and I genuinely refuse to work for companies that ask leetcode. Do these questions help me to find good/above average Junior Engineers? No.
Do these questions help me to find good/above average Senior Engineers? No.
Do these questions help me to find good/above average Managers? No.
Do these questions help me filter people who cannot memorize algorithms/interview questions or spend enough time on them? Yes. So where is the logical connection between leetcode problems and finding good/above average employees? As far as I can see there is none. There is literally almost no connection between a candidate being capable of solving leetcode and being a good software engineer that is capable of controlling/reducing complexity of the engineered applications and working well with other team members. More rational approach would be asking people architectural questions, even at the Junior level. I expect a good junior engineer would have already implement a small scale system at least as an final year thesis project, so they should be capable of handling questions related to engineering/architectural design. |
|