3 ms·
Heyo. From time to time I do interviews at my employer which involve having someone hack on our code base, pair-programming style, for around an hour-ish. But
by fennecfoxen 13y ago
Heyo. From time to time I do interviews at my employer which involve having someone hack on our code base, pair-programming style, for around an hour-ish.
But the work isn't free. Sure, the company isn't paying you, but the company is paying me, and you can bet that we're not getting as much done as we would get done on an interview-free day. I don't think anyone's ever been under the delusion that we're just trying to get cheap labor to build our codebase for us.
- RyanZAG 13y agoThere's a big difference between talking through an interview for an hour with some questions on how they'll handle a code base with maybe a function or two here and there to demonstrate, and the following: > LD: "Well, I thought we could work on our application, we've got some features I want to implement and push live by the end of the day" Key difference being that the interviewee is going to be adding new features that will be pushed live without any further work by other employees.
- abraininavat 13y agoThe interviewee isn't going to be able to do it (correctly) without the guidance of the interviewer. Not if the project is of more than trivial complexity.
- judk 13y agoThe actual red flag here is that the LD has no sense of software schedules or QA, or is feeling so pressured that he can't make time to prepare a well structured interview session.