4 ms·
The article is a follow-up to a previous post which I linked to in the leading sentence. > The author does not mention his experience interviewing or hiring pe
by nsainsbury 7y ago
The article is a follow-up to a previous post which I linked to in the leading sentence.
> The author does not mention his experience interviewing or hiring people
From the previous article: "I've been a software developer now for around 15 years. In that time, I've been a day-to-day developer, run my own successful software business, was co-founder at a VC funded startup, and I've had to hire and manage developers."
> I'd love to hear what OP suggests to replace the coding tests with - a chat about past projects, then make an offer?
From the article: "Why can't you look at a developer's portfolio, education, projects they've built, GitHub repo, talk with past employers, check references...and from that make an informed hiring decision?"
- saagarjha 7y agoI know a lot of really smart people who would score somewhat poorly on those.
- gherkinnn 7y ago> "Why can't you look at a developer's portfolio, education, projects they've built, GitHub repo, talk with past employers, check references...and from that make an informed hiring decision?" I have no Github, portfolio, nor education. My previous companies have a bad engineering culture. So they’ll give me good references, since they don’t know any better. I have trouble writing a fizz buzz and yet that system could have me hired.