3 ms·
I have done the takehome style interview before. I spent about a day on it, then said "here's a day's work, there is an API and a backend with tests, writing t
by jrockway 8y ago
I have done the takehome style interview before. I spent about a day on it, then said "here's a day's work, there is an API and a backend with tests, writing the frontend would be straightforward" and they said "go away unless you do it all". I went away. They had enough of a programming sample to make a hiring decision.
As a hiring manager, the takehome is very tempting. Candidates put their Github profile on their application. You go and look and there's nothing there except some make-react-app template. Their work experience on their resume is bullet points like "enabled solutions for the business through synergy", which they've been doing for five years. But they write you a cover letter about how much they like your company, so you want to give them a chance. You read on HN about how whiteboard interviews are unfair. So with no data, you reach for the takehome. If they can do some assigned work, then they'll probably do well in the role that they've applied for, and that's a good hiring decision. And they said right there in the cover letter that they'll do anything to get this job. It just seems natural.
For that reason, it's something I keep in my back pocket. (So far I've used it 0 times, though.) You can definitely have a Github repository that is more valuable than any takehome would be. You could actually talk in detail about the sort of engineering problems you've solved on your resume, and the takehome wouldn't show me anything new. But the reality is that the vast majority of candidates do neither. They work all day, so the last thing they want to do when they go home is write some open-source software. I get that. They have no idea what a resume should look like, since they've never been in that resume screening or interviewing role, so they write whatever some professor in college told them to do. ("It must fit one one page," is what I was told. I have learned that the opposite is true, if you want a job anyway.) So having some way to determine "can this person program at all" is valuable. But it's very time-consuming for the candidate, so is not ideal. A smart candidate will say "nope". A naive candidate will spend 50 hours on a 2 hour task and be mad. So it's probably not ideal.
(As an aside, what is the deal with these boot camps? Every single applicant has the same exact react app in their Github, and an entry for building it on their resume as though it was work experience. I sifted through 100 such resumes recently and almost have a script to determine which bootcamp they went to based on which files are in their Github. Is anyone getting jobs this way!? I am beginning to think that it is some social experiment involving bots.)
- xvector 8y ago> They work all day, so the last thing they want to do when they go home is write some open-source software. Or they are not allowed. A lot of companies like Apple don't let devs contribute to open-source. (Still not an excuse for a take-home, as you note.)