3 ms·

Am I the only one who, when being interviewed, doesn't mind whiteboard coding? At interviews where I've later been given an offer, it's usually a relatively sm

by Yen 11y ago

Am I the only one who, when being interviewed, doesn't mind whiteboard coding? At interviews where I've later been given an offer, it's usually a relatively small algorithmic design challenge, where the specifics don't matter, just the pseudocode. In interviews I've given involving whiteboard programming, I've always emphasized that it doesn't have to be valid or even semi-valid code for any language, just a semi-rigorous pseudocode expression of an idea. I think, "if done correctly", whiteboard coding is a good filter for those who can think algorithmically, who can catch the bugs that aren't typos, but incorrect assumptions. That said, that sort of mindset may not be what you need for your role. Need to consider that. --- Tangentially, one of the better technical interview experiences I've had involved chatting for a while, the interviewer describing an actual problem they'd had (relevant to the role and the company's product), and discussing my approach to the problem. (and passing or failing the interview wasn't dependent on using the exact same approach...)

krisdol 11y ago
> Am I the only one who, when being interviewed, doesn't mind whiteboard coding? I'm sure you're not, but my experience is completely opposite of yours. I'm still relatively early on in my career (I've had 3 software jobs, but have grown up coding since I was 12), but every job I scored was one that didn't use a whiteboard/paper problem during an interview. I got a lot better at whiteboards with practice; but early on, every whiteboard problem I received resulted in me blanking on even the most basic concepts. I would have no idea how to solve problems on a whiteboard that I explicitly solved in a codebase the week prior. Then I'd step out of the interview and the solution would just hit me. It's like state-dependent learning, in a way. As I got tested more on whiteboard coding, I figured out that whole problem-solving process better, and I do pretty well on them now. Still, I continue complain about those problems. They feel like a completely foreign, perpendicular challenge compared to having a discussion, answering questions, or writing code to solve the same problem. It's not a skill I've ever used outside of interviews, nor is it a situation that has ever been simulated at any workplace I've been at. There's nothing wrong with evaluating a candidate's whiteboard presentation skills. If the goal is specifically to evaluate technical or algorithmic knowledge, it's worth taking into account that testing for that knowledge on a whiteboard can introduce a side-effect that bottlenecks the candidate's ability to present their answer.
- thisone 11y ago
  Whiteboarding is a skill that the vast majority of people will have to work to obtain. It's not the natural way that we work. Personally, if you know you're going to be interviewing, start practicing for whiteboarding. There are books and online resources available to help you get at least comfortable with it. The resources also help drive home that whiteboarding should be about process, not about perfect solutions. Algorithms have generally taken years to perfect by PhDs, why should you be expected to perfect an algorithm you haven't memorised in 30 minutes?
  - Namrog84 11y ago
    Do that many places ask you to perfect an algorithm or solution? Most places me and my friends have done typically just want any brute force solution with some discussion as potential ways one might improve or discussion on why this might not be ideal without having better ideas. And this is from top places and offers. And were from non top schools.

by Yen 11y ago

krisdol 11y ago

> Am I the only one who, when being interviewed, doesn't mind whiteboard coding? I'm sure you're not, but my experience is completely opposite of yours. I'm still relatively early on in my career (I've had 3 software jobs, but have grown up coding since I was 12), but every job I scored was one that didn't use a whiteboard/paper problem during an interview. I got a lot better at whiteboards with practice; but early on, every whiteboard problem I received resulted in me blanking on even the most basic concepts. I would have no idea how to solve problems on a whiteboard that I explicitly solved in a codebase the week prior. Then I'd step out of the interview and the solution would just hit me. It's like state-dependent learning, in a way. As I got tested more on whiteboard coding, I figured out that whole problem-solving process better, and I do pretty well on them now. Still, I continue complain about those problems. They feel like a completely foreign, perpendicular challenge compared to having a discussion, answering questions, or writing code to solve the same problem. It's not a skill I've ever used outside of interviews, nor is it a situation that has ever been simulated at any workplace I've been at. There's nothing wrong with evaluating a candidate's whiteboard presentation skills. If the goal is specifically to evaluate technical or algorithmic knowledge, it's worth taking into account that testing for that knowledge on a whiteboard can introduce a side-effect that bottlenecks the candidate's ability to present their answer.

thisone 11y ago
Whiteboarding is a skill that the vast majority of people will have to work to obtain. It's not the natural way that we work. Personally, if you know you're going to be interviewing, start practicing for whiteboarding. There are books and online resources available to help you get at least comfortable with it. The resources also help drive home that whiteboarding should be about process, not about perfect solutions. Algorithms have generally taken years to perfect by PhDs, why should you be expected to perfect an algorithm you haven't memorised in 30 minutes?
- Namrog84 11y ago
  Do that many places ask you to perfect an algorithm or solution? Most places me and my friends have done typically just want any brute force solution with some discussion as potential ways one might improve or discussion on why this might not be ideal without having better ideas. And this is from top places and offers. And were from non top schools.