3 ms·
Point 3 is pretty important. I have seen so many small companies, that did not need really the very best engineer on the world to do their C# API suddenly ask G
by Arkhaine_kupo 4y ago
Point 3 is pretty important. I have seen so many small companies, that did not need really the very best engineer on the world to do their C# API suddenly ask Google questions straight from the "Cracking the coding interview".
Asking a 21 year old about a recursive O(nlogn) algorithm solution or how many ping pong balls fit on an airbus because you heard Google asks it when all you need is someone who can write a good integration test suite, use springboot, and create documentation for the clients to make the API useable and scalable is such a weird way to go about it.
And it seems entirely based on "if FAANG does it, it must be right".
- shagmin 4y agoThe hardest interview in my life was a long time ago when I tried getting a part time/side job updating content on a mostly static PHP website (no database or backend). Thought this would be a nice way to get some extra beer money or something. The interviewer was the person who was currently maintaining the site and had just graduated from Yale and wanted to move on. Not a single question about PHP, javascript, HTML, instead question after question about implementing various algorithms in pseudo code. I figure he was asking me questions from a textbook or something. I didn't get the job. Been a while since I've been in an interview but everything has been cake since.