Found this article interesting and useful:
https://blog.pragmaticengineer.com/data-structures-and-algorithms-i-actually-used-day-to-day/
Reminding myself to also read through this book on algorithms which seems cool.
Showing posts with label coding interviews. Show all posts
Showing posts with label coding interviews. Show all posts
Tuesday, July 21, 2020
Friday, July 19, 2019
Review: Google's Byteboard (A New Way to Interview Tech Talent)
Many developers, technical hiring managers, and even recruiters have heard of "Cracking the Coding Interview" by Gayle Laakmann McDowell. From my experience of interviewing for coding and testing jobs, I've learned that the recruiting process will change as the demands for talent also change. Naturally, it's time to see this process change with the landscape of new talent (even if big businesses continue to lag behind). With many new start-ups and small businesses looking to take their share of the market, the next generation of talent should consider their opportunities and no longer feel intimidated by recruiters or the recruiting process. In my opinion, the interviewing process has always been talked about mutual benefits but in reality have mostly, if not always, benefited the interviewer. But, how would talented interviewees shift more of the benefits to their side of the scale in an interview process?
Taking quizzes on HackerRank is cool. Throwing up all over a Whiteboard to showing code matching algorithms for problem solving is classic. Flexing a GitHub of finished projects is nice. However, none of these show a developer's team chemistry on a new feature which is now essential. And, many technical interviews are now happening online (rather than in-person). Teams don't automatically increase productivity due to talent alone. So, could Byteboard be the answer that talented teams and developers are looking for? Time shall tell.
Taking quizzes on HackerRank is cool. Throwing up all over a Whiteboard to showing code matching algorithms for problem solving is classic. Flexing a GitHub of finished projects is nice. However, none of these show a developer's team chemistry on a new feature which is now essential. And, many technical interviews are now happening online (rather than in-person). Teams don't automatically increase productivity due to talent alone. So, could Byteboard be the answer that talented teams and developers are looking for? Time shall tell.
Read Article
https://www.blog.google/technology/area-120/byteboard-interview-measures-for-essential-engineering-skills/A Comedy Skit on Job Interviews - Enjoy!
References
- https://youtu.be/d_MZgNSv2Fk (Purpose of Job Interview by Derick)
- https://youtu.be/BN0B4mOtwX0 (Tips to Coding Interviews by Gayle)
- https://youtu.be/zhUgaKb0s5A (How We Hire @Google)
Labels:
byteboard,
coding interviews,
google,
interview
Wednesday, January 2, 2019
Review: Microsoft changed the way they Interview
This is great to finally hear! Not because I can't pass such technical difficult interviews, but because such in-depth technical interviews do not reflect how people actually work in tech environments. There's a lot more to developing a key product pushing the industry's tech edge than a random research conclusion or unrealistic (useless) technical solution.
The "Alternative Interview Framework"
https://blog.usejournal.com/rethinking-how-we-interview-in-microsofts-developer-division-8f404cfd075a
P.S. French is a very useful language in the tech world, as I'm starting to see.
References
- https://www.businessinsider.fr/us/microsoft-new-developer-interview-process-2018-12
- https://www.businessinsider.com/how-google-hires-2013-6
Subscribe to:
Posts (Atom)

