4 ms·
Have you tried just having a conversation about pointers and recursion? Does that not work as well (or better)? Kudos for letting candidates know what’s going
by pantaloony 6y ago
Have you tried just having a conversation about pointers and recursion? Does that not work as well (or better)?
Kudos for letting candidates know what’s going to happen, it’s just that when I see problems that are clearly just a stand in for “do you know X?” I always wonder why interviewers don’t cut to the chase and just ask directly. “Are you comfortable with recursion? Can you describe it? When does it tend to be applicable?”
- ajuc 6y agoSome people (myself included) can bullshit through such questions pretty well even when we don't know the answers. It's a skill, a combination of reading body language for clues, being confidently vague in the right places and turning attention away from dangerous questions with charisma. You learn it quickly when teachers do oral exams at university :) Code doesn't lie, so I understand why people like to check candidates that way instead of relying on talk alone. I would just prefer if it wasn't a hit-or-miss test on what algorithms you memorized.