Live data from Hacker News

A hiring test I'd like to run

shkspr.mobi

71–80 of 203 posts

Re: A hiring test I'd like to run

#71
> I'd tell them that at the start, obviously. This isn't The Secret Rules For Getting Hired.

> "I know you've never used Blender," I'd say, "And this job doesn't require it. But we want to see how quickly and accurately you can learn to use something unfamiliar while under pressure."

> Or whatever.

The main problem is that the level of pressure that people feel under interview conditions will vary dramatically. Personally, I would find this a very bad test as I get horrendously stressed at interviews yet somehow manage to portrait a facade of calmness (to be fair I've been told once that I looked remarkably calm).

To the usual refrain of:

If you can't handle the pressure of an interview then maybe you are not a good fit for our company

I normally reply:

If day to day working at your company generates interview like levels of stress, then please do not offer me a job

Re: A hiring test I'd like to run

#72
post #36

Earlier quoted context omitted.

> In reality I was given only a single coding interview my whole onsite, and it was to build a JavaScript SPA, including routing/linking, without the use of any framework, just vanilla JS. > I was allowed to Google whatever but 50 minutes is still a crazy time crunch to figure out a lot of the stuff that needed to be figured out. This actually might not be so nuts if it were clearly a way to evaluate how you handle u…

I don't know. I'm very comfortable in JS, valilla, jquery, react and vue. And apparently my customers think I do a decent freelancer work since they keep hiring me back. And yet, an entire SPA in vanilla JS in 50 minutes seems a lot to me. I guess it depends of the size of the SPA, but user input + rendering + routing + whatever logic they ask you for the app is a lot of work. I guess it depends a lot of the requirem…

I've done a similar test. I didn't finish it in the time allotted, but a few other candidates did and they hired one of them. The fact companies can do these kinds of demanding frontend tests and still hire people is what makes me think there's a glut of web developers and not a shortage like people keep saying.

Re: A hiring test I'd like to run

#73
post #53

Earlier quoted context omitted.

I don't do much hiring, but when I do I make an active effort to avoid reading candidates resumes. I've found it's not possible for me to enter an interview with an unbiased mind having read a resume.

This feels weird to me. If you have advertised a job and I've given you my resume, it is to give you some information you can use to avoid wasting your time and my time. Just like I would hope your advertisement is accurate and useful enough to let me decide if it is a good use of time for me to send you a resume (e.g., saw an ad for "react developer" -- got to the interview and they were looking for a "server side j…

It is rude. People put lots of effort into resumes. But it's ruder to reject a candidate based on age, gender, martial status, education or lack thereof or doing non sw jobs in the past.

I always talk on the phone before and that's where we both make sure the interview is of relevance.

Re: A hiring test I'd like to run

#74
I was pretty happy with the interviews I went through for my current position, although that might be selection bias because I passed them. They all shared some important attributes:

1: Fairly open-ended, there was no "bzzt-wrong" moment like the Office 97 case in TFA, so I didn't feel a lot of pressure. It was definitely enough rope to hang oneself, so the interviewers could form an actionable and objective judgment, but as a candidate, I didn't feel that I was on trial, more just chilling and talking tech with some other nerds.

2: The underlying skills (understanding one's audience, breaking a large problem into pieces, making reasonable assumptions) were obviously directly applicable to the position. I never felt that I was doing senseless work, even when the questions were clearly contrived, because the connections were self-evident.

3: Despite the above, the actual questions didn't require a lot of domain-specific knowledge. Even the one that sorta did, could be answered by assuming that it was similar to a more common system, and that's how I approached it.

4: In every case, there were "plan B" options and accommodations for having a gap in one's knowledge. "I don't know this off the top of my head, but here's where I'd go to find out and here's the guess I'm going to use in the meantime" was a valid answer. Perhaps the best answer in some cases.

The result is that I work with a team of people who are super adaptable, can think on their feet, but have a keen interest in pushing towards correctness as soon as real information is available. Whenever I think about possibly going elsewhere, I remember that most HR departments don't select for any of those attributes, often quite the opposite. (And those places tend to be the clients whose problems we get called in to help solve, as a result.)

Re: A hiring test I'd like to run

#75
post #46
post #36

Earlier quoted context omitted.

> In reality I was given only a single coding interview my whole onsite, and it was to build a JavaScript SPA, including routing/linking, without the use of any framework, just vanilla JS. > I was allowed to Google whatever but 50 minutes is still a crazy time crunch to figure out a lot of the stuff that needed to be figured out. This actually might not be so nuts if it were clearly a way to evaluate how you handle u…

> "to evaluate how you handle unfamiliar problems" The only problem here is figuring out why would anyone work for a company with these practices. Unless I am missing something and it is common practice to build a product without any thinking, research and design.

[deleted]

Re: A hiring test I'd like to run

#76
post #53
post #25

I interviewed at Twilio. My resume and phone chats made it abundantly clear that my professional experience was 95% backend in languages like Java and Go. I looked at their Glassdoor where people wrote they were heavily biased to the algorithm type questions, for better or worse. In reality I was given only a single coding interview my whole onsite, and it was to build a JavaScript SPA, including routing/linking, wit…

I don't do much hiring, but when I do I make an active effort to avoid reading candidates resumes. I've found it's not possible for me to enter an interview with an unbiased mind having read a resume.

What? Unbiased mind after reading a resume? I'm expecting you to read my resume when I apply for a job. I hate it when recruiters call and ask how many years I've done X. It's right there on the resume. If you don't read it, you're wasting my time, as well as your own, if you're doing hiring.

Re: A hiring test I'd like to run

#77
post #65
post #36

Earlier quoted context omitted.

> In reality I was given only a single coding interview my whole onsite, and it was to build a JavaScript SPA, including routing/linking, without the use of any framework, just vanilla JS. > I was allowed to Google whatever but 50 minutes is still a crazy time crunch to figure out a lot of the stuff that needed to be figured out. This actually might not be so nuts if it were clearly a way to evaluate how you handle u…

> This actually might not be so nuts if it were clearly a way to evaluate how you handle unfamiliar problems and they made it clear they didn't really expect you to finish the whole thing in 50 minutes, I guess. This happened to me. I once interviewed at a place where they presented me with a language I had never seen. Very different concepts than your typical C/Algol flavored languages. They went over the basic conc…

Was it a company that is in the healthcare technology space, because that sounds like something you'd find there. That or aerospace.

Re: A hiring test I'd like to run

#78
post #77
post #65

Earlier quoted context omitted.

> This actually might not be so nuts if it were clearly a way to evaluate how you handle unfamiliar problems and they made it clear they didn't really expect you to finish the whole thing in 50 minutes, I guess. This happened to me. I once interviewed at a place where they presented me with a language I had never seen. Very different concepts than your typical C/Algol flavored languages. They went over the basic conc…

Was it a company that is in the healthcare technology space, because that sounds like something you'd find there. That or aerospace.

MUMPS?

Re: A hiring test I'd like to run

#79
post #73

Earlier quoted context omitted.

This feels weird to me. If you have advertised a job and I've given you my resume, it is to give you some information you can use to avoid wasting your time and my time. Just like I would hope your advertisement is accurate and useful enough to let me decide if it is a good use of time for me to send you a resume (e.g., saw an ad for "react developer" -- got to the interview and they were looking for a "server side j…

It is rude. People put lots of effort into resumes. But it's ruder to reject a candidate based on age, gender, martial status, education or lack thereof or doing non sw jobs in the past. I always talk on the phone before and that's where we both make sure the interview is of relevance.

If you can't read someone's resume without rejecting them based on age, gender, marital status, education or lack thereof, or for their non-sw work history, then it sounds like you're not a very good person to be interviewing candidates. The concept of "unconscious bias" might be true in an academic sense, but in a very real way you should be treating people with respect regardless of their characteristics, especially during an interview process. Not reading someone's resume isn't just rude, it's supremely disrespectful.

I take a completely different approach, because I have been on the receiving end of disrespectful interviews and I won't stand for it and I don't expect the candidates I interview to accept it either. I carefully read the resume and research the candidate far in advance to the interview. I only ask questions during the interview which are open-ended, not trivia questions, and are directly related to either the content of the candidate's resume or things we're actually doing day-to-day on my team.

The dog and pony show interview style is intensely disrespectful and so is the idea that you won't even read a candidate's resume. I've walked out of interviews where both have happened, and I hope everyone on HN gets the personal confidence to do the same. I'm a professional, I expect to be treated like a professional, and I return that by treating those I interview like professionals. End of story.

Re: A hiring test I'd like to run

#80
post #4

First test of any software dev: Do you know how to look for answers on stackoverflow? Second test of any software dev: Do you know how to ask a good question on SO?

When I'm stuck I look for answers on SO, however, if I don't find answers I open a book or read documentation. I actually never had to actually ask a question on SO.
Post reply on HN