All I do at work is fix bugs by changing a few lines of code and glue together API's to send data from A to B. I don't regularly search BST's using DFS/BFS algorithms or find the kth shortest string in a merged unsorted linked list or some shit like that. Preparing for these technical interviews is like a part-time job after my full-time job.
Good SWE interview tips. For those interested in product management interviews at Google I wrote some guidance at https://hackernoon.com/acing-your-product-manager-interview-...
Context: I'm on the Google PM Hiring Committee and help craft our hiring rubrics.
These are useful tips, although the example questions are extremely outdated. I found one tip "interesting" though.
> If you already know the answer, don't just blurt it out! They will suspect that you already knew the answer and didn't tell them you've seen the question before. At least pretend to be thinking though the problem before you give the answer!
Most interview questions are taken from sites like Leetcode. So you would have come across some of them if you work through those problems. Is it really that bad if you give the solution quickly? Some problems have specific "techniques" to solve them which you would likely only know if you solved it before. Are you expected to come up with a completely new algorithm to solve a problem?
Can any interviewers at Google or any of these large corporations share about how the interviewing process has changed in the last few years as now Cracking the Coding Interview, HackerRank/CodeWars/LeetCode, Glassdoor, mock interview sites, and even interview-prep bootcamps have become part of the curriculum for potential candidates to prepare for interviews? Do the companies find it as absurd as the candidates do?
I suggest this book the Competitive Programmer's Handbook https://cses.fi/book.html
I taught the class for several years; I'm happy to answer questions.
Or point folks to some notes from an updated version of the class.
This is 9 year old course. Still good for practicing.
"The class is held in room 32-124 from 5:00-6:30 PM on January 12 - 15, 2009"
Given the turn-over at Google is barely 2 years, what's the point? (And it's the largest of most companies too, so, you see what I mean).
I run a (paid) newsletter that sends fun coding interview puzzles every day. If you're interviewing around (or if you just enjoy programming problems), check out Daily Coding Problem: https://dailycodingproblem.com/!
Fun stuff! I especially enjoyed classic question #5 (in Handout 2).