4 ms·
> find a friend who’s spent time on hiring, and ask them for their favorite battle story. Anyone here have good hiring stories?
by MattGaiser 6y ago
> find a friend who’s spent time on hiring, and ask them for their favorite battle story.
Anyone here have good hiring stories?
- sokoloff 6y agoWe make business cards sold online. ~Half-billion-USD/yr of them. Literal sheets of uncut cards are under glass in the interview rooms. Final round with a candidate who’s “near the bubble”. Me: “Do you have any questions?” Him: “Yeah; have you guys ever thought about selling business cards online?” Me: “Uh, we’ve uh, given it some thought.” To this day, I’m not sure what he thought we did.
- jzwinck 6y agoAt a university recruiting event I asked one candidate if he was willing to move to NYC to work with us. Most people say yes, a few say no thanks and move on. This candidate said "Well my partner is considering a job in Texas." I asked candidate if he preferred Texas to NYC. "Not really, they have scorpions."
- munchbunny 6y agoI don't have good stories (or rather, none that I would want to share), but I do have battle scars. Hiring is hard. It's really complex to get right, and I spent years tuning the process. Having done both, I'd much rather be on the hiring end than the candidate end. But as the hiring manager, I mostly just felt weariness at the process.
- Aeolun 6y agoThe biggest revelation of being on the hiring end is that we generally know whether we want to hire someone a second after the interview ends. The most interesting thing I’ve heard I guess has been the guy who replied ‘Well, they’re all idiots there’ when asked why he wanted to move. Like someone else said, hiring is mostly just tiresome.
- mundo 6y agoA former job of mine forced candidates to fill out a form for one of those abominable HR candidate tracking sites, maybe ICIMS, and I saw the following gem from one applicant: Q: "One of CompanyCo's core values is Openness. How have you demonstrated openness in your career?" A: "I am open about my contempt for bullshit questions like this one."
- Ozzie_osman 6y agoHere are a few, and this is just at the offer stage (at which point you and your team have spent a lot of effort on a candidate): * Candidates reneging after accepting an offer (current company made a bunch of concessions to keep them) * Candidate reneging after accepting offer and my company getting an H1B approved for them (turns out they had interviewed with and accepted offers at multiple companies, to get multiple H1B petitions filed and maximize probability of at least one getting accepted... of course they didn't disclose this) * Candidate accepting offer then simply vanishing
- followben 6y agoYes! I moved internationally in 2012 and, knowing no-one in my new city, promptly volunteered to organise the local chapter of a popular developer meetup. I met dozens of friends and future colleagues at those monthly meets. Almost immediately I got a job with the outgoing organiser, and a couple of years later I recruited the core of a greenfield team from the regular attendees. One of them wasn't even working professionally with the language, but it was clear from talking to them and seeing their code they had potential. Moreover they were a really decent yet introverted person who just needed a break. I loved working with them and was proud to watch them grow into a truly accomplished yet extremely humble engineer. I'd hire them again in a heartbeat. Another: my department was made redundant in March (great timing), but I immediately picked up contract work with a friend I first worked alongside many years ago. I've hired him into multiple roles in the interim with great success... and now I get to help build his business. We trust each other to be candid and know each others strengths and weaknesses (technically and personally) and he pays me on time. It's great. Another: we needed a QA for my last team and one of our senior devs recommended someone from an old workplace. Feels bad saying it now, but with no experience of our toolset or domain we'd never have given their resume a second look. But good QAs are hard to find and we were desperate, so after a promising interview we hired them on a trial. Couldn’t have gone better - obliging, a quick study, and a knack for surfacing esoteric bugs. They went on to lead QA for our company. Referrals and “the network” can work to your advantage. Yet... when growing my last team I’d exhausted that network, so we advertised on StackOverflow. Amongst many applications were from two "developer famous" people I knew by reputation (twitter, conference talks, blog posts, book authorship etc). Our whiteboard-free process was a friendly interview followed by a small take-home code challenge. One came was arrogant and dismissive and said had neither the time nor inclination for take-home projects. While the other was gregarious, gracious and completed the task without fuss. Guess who we hired? They were technical mentor to virtually everyone on the team (myself included) and were instrumental in laying a solid architectural foundation of our product. While I’ve plenty of “war stories”, it really is nice to remember how many gracious, friendly and deeply competent people I’ve worked with over the years.
- 908B64B197 6y agoIt's a story I've been told. Candidate is being interviewed for a senior position, there are three employees conducting the interview: one HR rep, one (non-technical) manager and one senior engineer. The engineer supposed to help with the interview arrived late so the HR rep and manager briefed him, basically telling him the interview was going well and that they were considering hiring him unless he had any objections. Going back, he asked the candidate a simple Fizz Buzz question, something like finding the largest element in an array. All hell broke loose suddenly. He was outraged and started telling them that, back in his country he was a university professor and that this was beneath him. The interview ended with the candidate arguing for 10 minutes that he shouldn't have to do this test. If I recall, at this point the senior engineer just left the room and didn't bother with the remaining 15 minutes of the interview. Needless to say they didn't hire him. HR was shocked as he seemed to be a great hire. Fast forward a few years later, I'm the one interviewing and I systematically get great resumes who can't implement a simple version of word count in 30 minutes.