Hiring fast is actually really important. It sets a really good tone with candidates and forces you to have a hiring process with good decision points and processes. At Voxy we had a 1 week turn around goal from receiving a resume to having on offer on the table. Didn't always work out like that because of candidates, and vacations and what not, but that was the goal. The day of last interviews we either said no than…
Anec-data to your point: The two best companies I've worked for made their offers at the end of the interview day.
Hiring Processes Are Also Engineering Processes
11–20 of 71 posts
Re: Hiring Processes Are Also Engineering Processes
#12Earlier quoted context omitted.
Anec-data to your point: The two best companies I've worked for made their offers at the end of the interview day.
How did they go about doing that? It seems like it would be very difficult to avoid pressuring someone to decide on the spot. When that's not the intent (i.e. when the company respects a person's right to think about the offer), it seems like that risks becoming an uncomfortable situation.
Re: Hiring Processes Are Also Engineering Processes
#13Resume writer and ~20 year tech recruiter here. Just a comment to readers about the author's estimate that your resume is being reviewed for 5 minutes. It's not, so be sure not to write your resume as if it is going to get that much attention. Don't save the good stuff for the ending, thinking "the reader will get to that." Interview or delete decisions are often made in under thirty seconds, at least for things like…
Re: Hiring Processes Are Also Engineering Processes
#14Re: Hiring Processes Are Also Engineering Processes
#15Earlier quoted context omitted.
How did they go about doing that? It seems like it would be very difficult to avoid pressuring someone to decide on the spot. When that's not the intent (i.e. when the company respects a person's right to think about the offer), it seems like that risks becoming an uncomfortable situation.
The offer was made: they didn't require an immediate response. They had refined their decision process, they didn't constrain my decision process beyond what's customary.
Re: Hiring Processes Are Also Engineering Processes
#16Earlier quoted context omitted.
The offer was made: they didn't require an immediate response. They had refined their decision process, they didn't constrain my decision process beyond what's customary.
Cool. So they just said, "Hey, we would like to offer you the job. Here are the details. Please take your time and let us know when you've made a decision"?
Re: Hiring Processes Are Also Engineering Processes
#17Resume writer and ~20 year tech recruiter here. Just a comment to readers about the author's estimate that your resume is being reviewed for 5 minutes. It's not, so be sure not to write your resume as if it is going to get that much attention. Don't save the good stuff for the ending, thinking "the reader will get to that." Interview or delete decisions are often made in under thirty seconds, at least for things like…
I'll definitely include this when I write more for an audience of applicants. Resumes are soooooo boring, so anything to stick out is a big deal.
Re: Hiring Processes Are Also Engineering Processes
#18Earlier quoted context omitted.
The offer was made: they didn't require an immediate response. They had refined their decision process, they didn't constrain my decision process beyond what's customary.
Cool. So they just said, "Hey, we would like to offer you the job. Here are the details. Please take your time and let us know when you've made a decision"?
Re: Hiring Processes Are Also Engineering Processes
#19I especially liked this part: > If you need someone who can hit the ground running right away, test them with the exact tools they’ll be using on the job. If you need someone flexible who can learn anything, test them on something new and unique. If you need someone with a level head, try to frustrate your candidates and ditch the ones with short tempers. Edit: Except for deliberately frustrating candidates.
> If you need someone with a level head, try to frustrate your candidates and ditch the ones with short tempers. Interviews are a two-way street. If as a candidate I'm given an unrealistic expectation that's intended to frustrate me, I'll get the impression that's how the company normally operates and choose to look elsewhere.
When I talk about intentionally frustrating candidates, it's mostly based on a technical interview we would do that a lot of people would struggle with. It hit the critical thinking itch, I think, and some people can't handle that. Y'all have me thinking that this section could use a little revision, though.
Re: Hiring Processes Are Also Engineering Processes
#20I especially liked this part: > If you need someone who can hit the ground running right away, test them with the exact tools they’ll be using on the job. If you need someone flexible who can learn anything, test them on something new and unique. If you need someone with a level head, try to frustrate your candidates and ditch the ones with short tempers. Edit: Except for deliberately frustrating candidates.
The candidates who ended up frustrated weren't feeling that way because we were jerks to them (I don't think). Maybe what I'm getting at is don't be afraid to push people to the limit a little bit in a task, because their reactions to it say as much as their approach.