Contract to perm is the best way by far. In the UK the contract rates are typically significantly higher, so even if the person isn't offered a job at the end they aren't bothered. Everyone wins
We’re Bad at Interviewing Developers – Interview with Kerri Miller
31–40 of 101 posts
Re: We’re Bad at Interviewing Developers – Interview with Kerri Miller
#32Contract to perm is the best way by far. In the UK the contract rates are typically significantly higher, so even if the person isn't offered a job at the end they aren't bothered. Everyone wins
Re: We’re Bad at Interviewing Developers – Interview with Kerri Miller
#33Contract to perm is the best way by far. In the UK the contract rates are typically significantly higher, so even if the person isn't offered a job at the end they aren't bothered. Everyone wins
Re: We’re Bad at Interviewing Developers – Interview with Kerri Miller
#34I love the idea of asking the candidate to "teach me something, preferably something nontechnical." It sounds like a great way to test for communication skills while also learning something about the person's interests. Plus it could make the process a lot more fun for the interviewer. However I expect it would depend as much on the personality of the interviewer as on the interviewee. And at least in the US, it coul…
So this exercise would be artificial and forced. And, yes, for sure, I can put on a show, but it's not me and I'd be doing it because that the game or expectation and further, I think it's rather beside the point.
Re: We’re Bad at Interviewing Developers – Interview with Kerri Miller
#35I'm glad this one has the soundcloud link. Some of the others I've enjoyed don't and it's much easier to just listen.
Re: We’re Bad at Interviewing Developers – Interview with Kerri Miller
#36Contract to perm is the best way by far. In the UK the contract rates are typically significantly higher, so even if the person isn't offered a job at the end they aren't bothered. Everyone wins
Re: We’re Bad at Interviewing Developers – Interview with Kerri Miller
#37Earlier quoted context omitted.
> As a related note, the best predictor of university physics scores is high school English scores. That's pretty counter-intuitive. Can you give a source?
It's been twenty years since I saw that... google doesn't offer anything useful.
> The study by researchers at Harvard University and the University of Virginia (UVA) found the best predictors of success in college science courses to be high school classes that foster mathematical fluency, value depth over breadth, and feature certain types of laboratory work.
The study appears to be https://www.cfa.harvard.edu/smg/ficss/research/articles/Scie... . Table 4, model D, page 14 shows that science grades, followed closely by math grades, are much better than the English grade at predicting "College Science Grade". (It does not specifically pull out physics.)
Re: We’re Bad at Interviewing Developers – Interview with Kerri Miller
#38As a non-CS graduate looking for my first full-time job as a Junior Developer I can only ask one thing of prospective employers. Please give clear feedback that will help give direction to the candidate if you reject them. I have done a number of code challenges and while I don't mind doing the challenges (I look at them as training) and I can always create a working solution there is nothing worse than receiving a s…
Beyond the logistics of communicating to dozens of candidates for a single position, legally speaking, telling people why you rejected them gives you ammunition in court to say the process was discriminatory, and a violation of one of the many civil rights act. Simply saying 'we decided to go with a different candidate' gives you a courteous brush off, without giving you reasonable cause to go fishing with during discovery.
The purpose of an interview is not to get better at interviewing. The place for this is mock interviews. Honest feedback is expected to be given without the risk of employment discrimination lawsuits. I figure to the extent that constructive feedback is owed, mock interviewing is the way to provide it.
Re: We’re Bad at Interviewing Developers – Interview with Kerri Miller
#39Earlier quoted context omitted.
If you "need a developer to port the Java code to Go", you need a contractor. Once the Java code is ported to Go, they're done, and there will be no more Java code to port to Go, so... why would you hire a permanent employee on the basis of their ability to port Java code to Go? The point of a permanent software development teammember is to add to the capabilities of your engineering staff. What is it you want them t…
>If you "need a developer to port the Java code to Go", you need a contractor. Once the Java code is ported to Go, they're done, and there will be no more Java code to port to Go, so... why would you hire a permanent employee on the basis of their ability to port Java code to Go? My examples are being interpreted too literally. They are not tasks that must literally go into the job description. Instead, they are bull…
It's rare that I see a req that interests me, because most are extremely situational and based on very specific tasks. Again, I recognize these sorts of jobs will always exist in established companies, and I thank the writer for making that clear, but a list of 8 technologies (who am I kidding, it is usually 15 with 10 more 'nice to haves') from a start up that will probably be pivoting in 3 months anyway? Doesn't make a lot of sense to me. "Come work for us and absolutely stall your career as you grind out tasks that you mastered 3 years ago" is not an appealing sales pitch, and not one that will bring in the talent you need to respond to new challenges.
I'm not saying you meant any of that in your post (you might of, but I'm not sure), your post was just a convenient one to respond to.
Re: We’re Bad at Interviewing Developers – Interview with Kerri Miller
#40As a non-CS graduate looking for my first full-time job as a Junior Developer I can only ask one thing of prospective employers. Please give clear feedback that will help give direction to the candidate if you reject them. I have done a number of code challenges and while I don't mind doing the challenges (I look at them as training) and I can always create a working solution there is nothing worse than receiving a s…
If you get rejected you were simply not the right fit.