|
|
|
|
|
by b20000
1527 days ago
|
|
fizzbuzz is the least of your concern if you do these type of interviews. the problem is that you will be asked a question which required several hours to produce an optimal solution, yet you are supposed to deliver this solution in under 5-10 minutes, and the only way to do that, is to repeatedly grind the solution and memorize it and then quickly reproduce it in the interview. as such, the style of interviewing is broken, and optimizes for candidates willing to endlessly grind LC or HR, and memorize the solutions. in the end, everyone loses. coding interviews are there to exhaust the candidate so when the offer stage finally arrives, they take any offer. all it does it put everyone in a bad position. and you are mistaken that it's up to the company to decide what happens. as an industry of professionals, it is our decision. |
|
As a professional software engineer, you are expected to be proficient at those skills to an extent in which you can demonstrate them in practice.
The burden of verifying you acquired the skills associated with your education falls on the employer.
Fizzbuzz is trivial and should not be a problem for any developer at any level. Writing a binary search function should not be a problem either.
But I agree that the industry's obsession with competitive programming has gone too far in some cases, especially in cases where the skills being tested are not relevant for the job.