4 ms·
I'm so glad to work in a field with technical interviews. I can't imagine having to deal with coming up with a clever new spin on "tell me about your work histo
by philwelch 14y ago
I'm so glad to work in a field with technical interviews. I can't imagine having to deal with coming up with a clever new spin on "tell me about your work history" or "what's your greatest weakness" to stand out from the crowd--though I've resolved never to take the latter question seriously.
- Nursie 14y agoI find honesty has worked on that latter one in the past - "I don't always ask colleagues for help if I'm stuck" Which is true, I have a tendency to (occasionally) get bogged down and spend a day or two on solving a technical problem myself that may well be resolved with five minutes of chat around the coffee machine. I've never not been offered a job after an interview with that line in it, though I think it's only come up twice.
- slurgfest 14y agoThat's a thing, it's technically true in itself, and it's bad enough to sound plausible. I think you are a smart person and it's a good self-preserving tactic. We all have to eat. But this answer is unlikely to be the worst thing about you. You probably do have character flaws which affect your work. It's just that digging into them won't do anything except give the advantage to someone else who kept his mouth shut. I submit that what this question really does is test fit to a certain corporate culture. There's a tacit understanding that you are supposed to come up with some token flaw to use. People oblivious of this will either overshare or obviously deflect the question, and people who are stubbornly honest will also not give the expected answer. This kind of obliviousness or stubborn honesty can be a political liability. E.g.: if you are asked about your boss's or team's or company's worst weakness, you should also offer some bullshit token flaw which isn't really meaningful, because this determines their futures too. If a culture isn't specifically built to put honesty ahead of politics, politics will quickly take the lead and honesty will be a casualty.
- philwelch 14y agoAnd this is why these bullshit questions give me a headache and I'd rather talk about suffix trees or something.
- lrobb 14y agoThose are actually good questions. The work history serves as a nice interview warmup and is a good gauge of a candidate's ability to communicate. A bad answer is to mumble out what's on paper in front of you. A good answer will reframe the question in terms of what the job ad described. The weakness question tells me how introspective you are. Someone aiming at self mastery that has a big picture view is going to give a vastly different answer than someone fresh out of school that's read an advice column and thinks they're a rock star.
- rdl 14y agoWork history is essential. After an initial screening (minimal technical competence, etc.), and a review of work samples already prepared, I think a walkthrough of "what have you done, and why", starting as early as possible, makes sense. It's not just passive "I worked at X, Y, Z", but trying to actually understand the candidate and his motivations. It's interesting to explore what someone didn't do as much as what they did do. The point of being comprehensive is that it's much more difficult to come up with a bonus story with that level of detail while keeping it consistent, and the most interesting stuff is not the overt things ("I worked on guidance systems") but all the details and motivations. This could easily take 2-3h even for a 30 year old. Doing it without 1) being a dick 2) psychologically taxing 3) being confrontational is the hard part. I'd personally rather have a 2-3h interview/talk with a manager or founder, and a half-day of technical stuff, than sit through 8 interviews with people I won't be working with doing a combination of technical and non-technical. Then, work-product sample, as close to the actual work as possible.
- slurgfest 14y agoIf you want to gauge ability to communicate then you should probably find some way to get relevant work samples, like explaining the kind of thing which will have to explained in the job (e.g.: docs or brief presentation on something), rather than relying on the totally unreliable assumption that asking someone bad things about themselves in a high-pressure situation is a close analogue to what they will be doing on a daily basis. This is like the ancient Chinese exams which assessed applicants' suitability by their knowledge of classical poetry. Of course people who are very well prepared or smart will do better in aggregate and with certain biases, but this doesn't mean you are measuring what you claim to measure.