Earlier quoted context omitted.
What would you do instead? Everybody knows interviews don't work that well but nobody has any better ideas.
1) give a 3 day coding challenge to gauge the candidate real potential, and 2) hire fast, fire fast.
Fixing impostor syndrome in coding interviews
71–80 of 84 posts
Re: Fixing impostor syndrome in coding interviews
#72Earlier quoted context omitted.
What would you do instead? Everybody knows interviews don't work that well but nobody has any better ideas.
1) give a 3 day coding challenge to gauge the candidate real potential, and 2) hire fast, fire fast.
And I’m a good test taker and interviewer.
Re: Fixing impostor syndrome in coding interviews
#73Why do people study for interviews? I feel like if I have to study for an interview, then I’m clearly not good enough for the position. Is this common in other fields of study?
Interviewing is a different skillset than most development positions ever use; you can be a good developer but a terrible interviewer. You'd be great at the job, but you get rejected in favor of someone else that put some more practice into skills that are applicable to interviewing (i.e. whiteboard programming, working without reference material, etc). You go into the interview, having not studied. Your twin studied…
Re: Fixing impostor syndrome in coding interviews
#74Earlier quoted context omitted.
It wasn't really 'trivia'. It was several hours of difficult problem solving without reference material, given access only to a whiteboard and a judge. The studying that would have led to a success: * Memorizing a significant amount of the interview's programming language. Since there is no reference material, you really need to know it. No standard library reference to help you out. * Solving enough algorithms and d…
> It wasn't really 'trivia'. It was several hours of difficult problem solving without reference material, given access only to a whiteboard and a judge Even more irrelevant with today's access to Google, StackOverflow and alike. I've done my share of learning by heart pages of demonstration for some obscure quantum physic model, puking it the day of the test, and then forgetting about it. It the company is looking f…
Re: Fixing impostor syndrome in coding interviews
#75Earlier quoted context omitted.
I'd say that if you're in a technical interview with a non-technical manager, you may've chosen the wrong company to interview with. And if it's a non-technical portion of the interview and you have trouble making yourself understood (to a manager), you're back to the "it's not a good fit" conclusion.
It was definitively the "technical interview with a non-technical manager", and yes, I do agree with you, but it's difficult to judge companies beforehand.
Re: Fixing impostor syndrome in coding interviews
#76Why do people study for interviews? I feel like if I have to study for an interview, then I’m clearly not good enough for the position. Is this common in other fields of study?
There are some things I do in programming that are such habits that I have hard time explaining it.
If someone gave you an English test (assuming you are a native English speaker), and gave you a sentence to correct:
I love that antique green big wonderful car that is always parked at the end of the street.
It probably would sound wrong to you but could you explain why? (http://www.gingersoftware.com/content/grammar-rules/adjectiv...)
Re: Fixing impostor syndrome in coding interviews
#77Earlier quoted context omitted.
1) give a 3 day coding challenge to gauge the candidate real potential, and 2) hire fast, fire fast.
I’m barely willing to take an online coding test for one job when I know historically for me, if I get submitted for 10 jobs by a recruiter, I’m likely to get three offers, take myself out of the running for 6, and only have one company that’s not interested. Why would I ever spend three days on a coding challenge. And I’m a good test taker and interviewer.
Re: Fixing impostor syndrome in coding interviews
#78Earlier quoted context omitted.
1) give a 3 day coding challenge to gauge the candidate real potential, and 2) hire fast, fire fast.
Who's going to consent to doing three _days_ of work?
Re: Fixing impostor syndrome in coding interviews
#79Earlier quoted context omitted.
1) give a 3 day coding challenge to gauge the candidate real potential, and 2) hire fast, fire fast.
I’m barely willing to take an online coding test for one job when I know historically for me, if I get submitted for 10 jobs by a recruiter, I’m likely to get three offers, take myself out of the running for 6, and only have one company that’s not interested. Why would I ever spend three days on a coding challenge. And I’m a good test taker and interviewer.
Re: Fixing impostor syndrome in coding interviews
#80Earlier quoted context omitted.
Who's going to consent to doing three _days_ of work?
Most of the candidate of my past job who passed the initial non-technical interview with my former manager, over 2 years, that was probably a dozen people, leading to 3 hires.