Live data from Hacker News

The latest trend for tech interviews: Days of unpaid homework

work.qz.com

201–210 of 1001 posts

Re: The latest trend for tech interviews: Days of unpaid homework

#201

Despite some of the comments here, I'm actually a fan of the 'homework' format. I'm not always great at hiring, but I know how to gauge the 'homework' interviews, and I've usually been right about the interviewee's abilities afterwards, WAY moreso than whiteboarding or riddles or any of the other alternatives. That being said, I would add some constraints: 1. The 'task' shouldn't take more than 30 min to understand,…

I'm going to disagree with you on a number of reasons. 1. A lot of studies out there show that the most important factor for a hiring success is culture, not skill. 2. Are you even measuring skill with your test? It doesn't matter if it should only take 2h for a candidate to complete your test, if they're nervous or want to impress they're going to spend 12h on it. How can you tell the difference? 3. What about the r…

> . A lot of studies out there show that the most important factor for a hiring success is culture, not skill.

No! Studies show that above an sufficient baseline level, having a baseline of soft skills matters more than marginal differences in tech skills.

Re: The latest trend for tech interviews: Days of unpaid homework

#202
post #171
post #117

Earlier quoted context omitted.

I never see a shortage of people applying. I usually see a great shortage of people I want to hire. Mid-level position, asking for 5 years of related experience? 85% of the resumes have no related experience. Fresh out of school, that is. The virtual pile gets much shorter when minimal criteria are applied.

Have you tried developing your junior talent instead of driving them away so you need to fill a gap at mid-level?

Are there companies where people don't periodically move on? The culture right now is to hop between companies. It's not necessarily a bad thing. People get tired of their work and need novelty.

Re: The latest trend for tech interviews: Days of unpaid homework

#203

Earlier quoted context omitted.

Came here to say almost exactly this. I can't speak to the bias issue. I do know that spending three days doing a little chat app last time around landed me one of the best gigs I've had. The process was painless, I would have spent that time coding and refreshing skills anyway, and the project was actually fun. I also know 100% that if the company I work for encountered a candidate who needed more time to work on th…

>I undertook this project after two 30 minute conversations had convinced both parties that there was a fit, and the project was a next step. In this case, I don't see it as unreasonable, because you didn't have to do the project just to have a shot at someone talking to you in person. I would never do a homework project as the first step in an application process. I would do one as the last step, after I had learned…

> I would never do a homework project as the first step in an application process. I would do one as the last step, after I had learned enough about the job and the company to decide that I really wanted it, and they had narrowed down the field to me and a handful of other candidates.

When I was job hunting last year, the steps typically went like this.

1) 30 min phone call

2) Homework

3) Algorithm Exam

4) Onsite

I typically got rejected at #3 which means the homework meant nothing.

Re: The latest trend for tech interviews: Days of unpaid homework

#204

One big issue that a take home assignment is that it removes the ability for the candidate to ask questions. Interviews are two-way streets. Nowadays, I reject more companies than I interview for based on an initial phone conversation. I have requirements in what I look for in a company and position, and some simple questions help me resolve many of the primary requirements. Given a take home exam, I will have invest…

What questions, if you don't mind my askibg

work environment, fluidity of assignment, career opportunities, acceptance of suggestion, involvement of developers into the design process, key tools and applications, workflow automation expectations...

there are lot little details that one can ask and will give you back a picture of how the working environment is going to be. here's a good starter list, even if I find it too formulaic and question you need to ask heavily depends on what your role will be: https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-s...

also, as an interviewer, if a candidate doesn't ask about the work environment and daily operations I'll take it as a potential sign of the candidate having never reflected on its own craft.

Re: The latest trend for tech interviews: Days of unpaid homework

#205

Earlier quoted context omitted.

I thought of undue grace or generosity because typically the term is used to criticize the unmeritorious for undue position -- is it not? What does it mean if I say you are privileged? When one looks further at the definitions listed for privilege, one sees examples discussing kings and royalty for birthrights. If we're discussing whether people are unworthy, then we are on the same page.

To me, "undue grace" and "generosity" imply some actor who imparts such grace or generosity. But that's not required for privilege. Particularly when people talk about enjoying a privilege in the social-justice way (which I believe to the kind of criticism you're talking about), they're often using it to mean a lack of discrimination as opposed to granting an elevated status. For example, if someone has the expectati…

[deleted]

Re: The latest trend for tech interviews: Days of unpaid homework

#206
post #57

Despite some of the comments here, I'm actually a fan of the 'homework' format. I'm not always great at hiring, but I know how to gauge the 'homework' interviews, and I've usually been right about the interviewee's abilities afterwards, WAY moreso than whiteboarding or riddles or any of the other alternatives. That being said, I would add some constraints: 1. The 'task' shouldn't take more than 30 min to understand,…

Well when done this way with all the constraints you specified, then yes the homework interview works very well. Unfortunately, the vast majority of hiring managers do not come anywhere close to any of the points you mentioned. Just last week, I was interviewing for an opportunity as a VP of Engineering for a post-early-stage startup. The CTO gave me a take home assignment involving building not one but three complet…

Senior roles should have more demanding technical interviews than junior roles. The company had a bullshit-preventing immune system. It's not a culture fit for you. Win-win.

Re: The latest trend for tech interviews: Days of unpaid homework

#207

If the software development industry was the home building industry... I'm a general contractor (Unicorn Homes Inc.) and I'm currently building a number of spec homes. We're going to need electrical work done in all the homes and I'm in the process of sub-contracting out that work. What I need from you, Joe Electrician, is for you to go wire the kitchen of one of these homes. Once you're done I will inspect your work…

You are welcome to go work in an industry where all the projects are essentially identical so once you've done it once you can do it for anyone anywhere. Enjoy your pay cut and ease of getting hired, unless there is an oversupply .

Re: The latest trend for tech interviews: Days of unpaid homework

#208

Earlier quoted context omitted.

>I undertook this project after two 30 minute conversations had convinced both parties that there was a fit, and the project was a next step. In this case, I don't see it as unreasonable, because you didn't have to do the project just to have a shot at someone talking to you in person. I would never do a homework project as the first step in an application process. I would do one as the last step, after I had learned…

> I would never do a homework project as the first step in an application process. I would do one as the last step, after I had learned enough about the job and the company to decide that I really wanted it, and they had narrowed down the field to me and a handful of other candidates. When I was job hunting last year, the steps typically went like this. 1) 30 min phone call 2) Homework 3) Algorithm Exam 4) Onsite I t…

Maybe to your experience, but it likely is a filter for others.

Re: The latest trend for tech interviews: Days of unpaid homework

#209

I don't want to name names but one YC company I interviewed at left me with the distinct impression that they talked a big game, just to get me to work on one of their (apparently) "strictly-hiring-related toy projects" as homework. Homework, "sure", except it: 1) integrated with a real system, 2) mirrored something they actually did, and 3) they would only agree to proceed if I signed an IP/work contract and accepte…

I don't want to pass judgement on your coding exercise, and it certainly seems fishy with the contract, however... I would point out that on the hiring side, evaluating a submitted project in a way that can differentiate between good and great candidates, and that the reviewers can understand well enough to get the signal they need, is very difficult. Because of this, I know several times we have asked candidates to…

this, just have them do a small subset of something you already do. It tells you so much. I also tell the candidate that if they complete it and it works they are guaranteed to be hired at some level. At the end of the day if you can't show me your work on a open source project, or demo me something you made, there is no way for me to know you can actually build something until you do! Especially true for junior level positions!

Re: The latest trend for tech interviews: Days of unpaid homework

#210

Earlier quoted context omitted.

I've never seen a take home coding challenge that had even the possibility of being used as production code. For me it's always been a standardized, self-contained example problem. Maybe there're scummy companies that try to push job applicants' work to production, but I'd be shocked if that was anywhere close to the modal case. So it's more like "What I need from you, Joe Electrician, is for you to go wire up this d…

I've definitely seen some prompts that looked suspiciously production-ready. It's usually not "build out our new feature", because spinup time is a thing, but some companies do seem to throw around "build our new one-off microservice". Stuff like "given this incoming data, set up intake, a storage layer, and a backend layer that applies formula X". If the data and the formula look business-relevant, it's at least eno…

Wow the pendulum has swung from "employers don't ask any relevant questions" to "I mistrust employers who ask relevant questions".
Post reply on HN