11–20 of 52 posts
All I know is, FAANGs can get away with anything, because the supply of engineers is just that much. There's no shortage of engineers who are preparing months and months on end, solving hundreds or thousands of leetcode problems. There are coaching institutes, and an entire industry devoted to cracking these interviews. The financial reward is worth it for most people.
All I know is, FAANGs can get away with anything, because the supply of engineers is just that much. There's no shortage of engineers who are preparing months and months on end, solving hundreds or thousands of leetcode problems. There are coaching institutes, and an entire industry devoted to cracking these interviews. The financial reward is worth it for most people.
What about all of those who got rejected? Do you think they actually gained any value from it?
I was an engineering hiring manager for several small startups. I never asked for coding on a whiteboard. I asked some work style questions and then concentrated on a collaborative exercise where I laid out a problem and important applicable technology. Then I'd answer any Google-ish questions in realtime. This technique found good collaborators and also which people were good problem solvers. Never made a bad hire f…
A lot of leetcode type interviews also skew towards people who can keep talking out loud while writing code. I can’t remember the last time I was programming and constantly talking out loud. I like to be quiet, focus and then write code. Preparing for interviews felt like I was a code monkey preparing for a special dance.
Who can solve a "medium to hard" problem in 15 minutes, on a whiteboard, under stress, twice in a row? Who are they looking for? Leetcode psychos?
I was an engineering hiring manager for several small startups. I never asked for coding on a whiteboard. I asked some work style questions and then concentrated on a collaborative exercise where I laid out a problem and important applicable technology. Then I'd answer any Google-ish questions in realtime. This technique found good collaborators and also which people were good problem solvers. Never made a bad hire f…
Am I weird for thinking that sounds fun to do?
As a hiring manager, I find talking in detail about work (school or industry) a candidate has done is a lot more illuminating than a coding problem. The trick is that it takes more preparation and focus from the interviewer because they need to know how to ask the right questions, they must know how to guide the conversation in real time, they must understand details about entire project in a few minutes, etc.
As a hiring manager, I find talking in detail about work (school or industry) a candidate has done is a lot more illuminating than a coding problem. The trick is that it takes more preparation and focus from the interviewer because they need to know how to ask the right questions, they must know how to guide the conversation in real time, they must understand details about entire project in a few minutes, etc.
How do you know they personally solved a problem, rather than just studying someone else’s solution?