The conversation

Lessons learnedExperience excerpt · English

In 2006 when I got my first dev job, I sat down with the lead developer for about half an hour and …

In 2006 when I got my first dev job, I sat down with the lead developer for about half an hour and we largely just had a very friendly and informal conversation talking about how I would hypothetically build things, what software I enjoy using, etc. I very vividly remember talking about how great I thought it was you could do basic math in the Firefox search bar at the time. He left to talk to the owner, came back with a (in hindsight very small) number on piece of paper, and I started that week. When I started at my current gig over a decade ago I had a three-day ordeal of interviews. In person, telephone, full day of in person again. Spoke with at least six different sets of people. Jobs I've applied for in the interim have been even worse. As someone who has been in a hiring position myself, I think that first informal interview tells you way more than a checklist. If you need the checklist items answered, put them on the application. Interviews should be for getting to know the person. …

Original discussionAsk HN: Why is hiring so dehumanized, and what can be done?159 source comments · at import
2

What was this responding to?

Parent context · original excerpt

EL

As technology permeates the world more and more, the hiring process is becoming more dehumanized, IMHO. What can we do as an industry, to make hiring more efficient for everyone? Some of the pain points I observe are: 1. Applicants must wade through large volumes of job postings, which are often poorly written, and frequently lacking key information which is important to the applicant. 2. Employers are overwhelmed with large numbers of applicants, most of whom don't meet the requested minimum requirements. 3. Employers are then too overwhelmed to reply to all the applicants. 4. Applicants are then annoyed with the lack of replies. 5. By the time an employer finds a potential match, the applicant may be difficult to reach, or is no longer interested. 6. By the time an applicant hears back from an employer, they are disappointed in the quality of the response, and already have a bad impres…

Full original

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 2

Direct replies available in this import. Original-language excerpts.

NE

> When I started at my current gig over a decade ago I had a three-day ordeal of interviews. In person, telephone, full day of in person again. Spoke with at least six different sets of people. These kinds of processes just feel designed to dilute the blame.

Full original
MC

My interviews still tend to be one or two friendly conversations. Of course I'm freelancing (for big projects) rather than employed, so maybe that changes things. And the actual hiring process can still be long because I do a lot of work for banks and other organisations with a serious screening process, but at its core is still the basic interview that's basically a friendly chat. When I was responsible for hiring at my previous project, that's also what I did: I want to get to know the person. Is this someone I can work with? I was much more interested in what their most interesting project was, than in which checkboxes they checked. If there was one checkbox I had, it was: "can they admit they don't know something?" because some people just started spewing nonsense if they didn't know the answer to a question.

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.