6 ms·
Reasoning behind the questions: 1-7 - basic HTML/CSS/JS proficiency (and ability to effectively Google for help if they didn't know about CSS' nth-child or wha
by yeldarb 8y ago
Reasoning behind the questions:
1-7 - basic HTML/CSS/JS proficiency (and ability to effectively Google for help if they didn't know about CSS' nth-child or whatnot)
8 - get them familiar with the jQuery animate function (which I wanted to use later as a visual proxy for any async function) -- I was more than happy to link them to the jQuery docs or explain the parameters here if they weren't familiar with it.
9 - testing understanding of async functions and how to use callbacks. Ideally they used recursion but I would have accepted a calculated timing-based solution using setTimeouts as well.
10 - wanted to see how they'd go about learning something new given the documentation -- async.js' docs don't have great examples included so I was hoping to see them search for them on Stack Overflow if they didn't quite understand the callback formats.
11 - algorithm design and recursion. But mostly I thought people would get stuck here and I wanted to see how they dealt with that and what they did to get themselves un-stuck.
- spyckie2 8y agoNo your questions aren't bad they're actually quite good for what you're testing. Good reasoning to back them up too. Your funnel also looks pretty normal. I wouldn't be surprised if all 8 fail the test for front-end, welcome to hiring in the real world.
- fitpolar 8y agoYou shouldn’t be hiring if you’re completely oblivious as to why all 8 would fail.
- zerr 8y agoTake home would make more sense for these... Researching/Googling/SO-ing under 1h limit and when someone watches you, breathing behind the neck, should be uneasy.
- dyeje 8y agoThis. The timeline is a bit tight for a live interview. They have about 5 mins per task. I think you're probably filtering too hard on people with previous experience using jQuery and don't have interview jitters. My suggestion would be offload some of those basic questions to an automated at home code test. It'll filter out candidates who can't FizzBuzz, so you're left with a more reasonable 1 hour technical interview with less pointless candidates.
- fitpolar 8y agoThe questions you asked and the reasoning behind asking them was quite good, and I would’ve liked this interview. The timing though was a little ridiculous. You could, and perhaps SHOULD, easily spend an hour on 10 and an hour on 11. IME, this is the biggest problem with the current state of the interview process - what I call Hollywood hacker testing. Unrealistic timing expectations based on what’s seen in Hollywood movies. The take home test is worse for this! At least this wasn’t part of your process...you don’t want have a hiring process where the only person who can put in 60 hours wins. Be realistic, if you really care about improving the hiring process and not being another dumping ground on Glassdoor for interviewees you’ve angered.