3 ms·
As an Interviewer: I think it's helpful, in order for me to understand the person I'm interviewing, to pair program on a problem together. I don't think it mak
by beardedetim 4y ago
As an Interviewer:
I think it's helpful, in order for me to understand the person I'm interviewing, to pair program on a problem together. I don't think it makes sense for them to LeetCode an algorithm in front of me; I think it makes sense for us to build a working API or an Async Worker. I need to know that you _know_ these things or at least know that _you can figure these things out_ and know how to _ask questions when you are stuck_.
As an Interviewee:
I won't do take-homes. I barely like having to do 1hr long interviews, there's no way I'm going to take 1hr+ of my time _outside of work and interviewing_ to do your toy problem _and then talk to you about it_. I would love to hang out, sling code together, and spend time nerding out for 1hr with people as an interview. In fact, I know that if the interview is a "let's code together" one that I'm pretty likely to get the job so I look forward to those types of interviews.
- codingclaws 4y agoI would like to pair for an interview but I don't think I've ever done that across over 100 of them. It might be hard for me though, because I'm a generalist and often apply to jobs where I haven't used the stack recently.