4 ms·

> I've been to plenty of interviews where my CV hasn't been given more than a glance. I do technical interviews and I never look at CVs before doing the inter

by pradn 6y ago

> I've been to plenty of interviews where my CV hasn't been given more than a glance. I do technical interviews and I never look at CVs before doing the interview. I do this to avoid bias. I want to treat them the same no matter if they went to Stanford or were not working for 10 years or if this is their first job. Also, people are adaptable, and soft skills matter a lot. So the error bars for recruiting even based on hard skills on a resume are really large.

tasty_freeze 6y ago
> I want to treat them the same no matter if they went to Stanford or were not working for 10 years or if this is their first job. I don't agree. If I'm interviewing someone straight out of college there are things I wouldn't expect them to really know and focus on whether they are focused and motivated enough to learn those things on the job. If the person at 15 years experience and doesn't know things which are a normal part of the kind of job I do, it would be a deal breaker.
- pradn 6y ago
  Where I work, the interview is based on the level we're hiring for, not their background. If someone's expected to perform as a mid-level engineer, it doesn't matter to me how long they've worked as long as they can solve the technical problem as expected for someone of that level. It's a different philosophy, and has it's pros and cons.
- mdpye 6y ago
  I try to let the expectations for the interview be set by the expectations they will find when they start. It's useful to know what you're looking for when you go out in to the market...
bhandziuk 6y ago
What if there is something interesting on their CV worth exploring?
- pradn 6y ago
  I start off by asking them about an interesting technical problem they worked on recently, so I get to talk to them about that stuff. Unfortunately, many candidates mention the company they work for off the bat, which may introduce unconscious bias or whatnot.

by pradn 6y ago

tasty_freeze 6y ago

> I want to treat them the same no matter if they went to Stanford or were not working for 10 years or if this is their first job. I don't agree. If I'm interviewing someone straight out of college there are things I wouldn't expect them to really know and focus on whether they are focused and motivated enough to learn those things on the job. If the person at 15 years experience and doesn't know things which are a normal part of the kind of job I do, it would be a deal breaker.

pradn 6y ago
Where I work, the interview is based on the level we're hiring for, not their background. If someone's expected to perform as a mid-level engineer, it doesn't matter to me how long they've worked as long as they can solve the technical problem as expected for someone of that level. It's a different philosophy, and has it's pros and cons.
mdpye 6y ago
I try to let the expectations for the interview be set by the expectations they will find when they start. It's useful to know what you're looking for when you go out in to the market...

bhandziuk 6y ago

What if there is something interesting on their CV worth exploring?

pradn 6y ago
I start off by asking them about an interesting technical problem they worked on recently, so I get to talk to them about that stuff. Unfortunately, many candidates mention the company they work for off the bat, which may introduce unconscious bias or whatnot.