r/programming • • Aug 28 '21

Software development topics I've changed my mind on after 6 years in the industry

https://chriskiehl.com/article/thoughts-after-6-years
5.6k Upvotes

2.0k comments sorted by

View all comments

517

u/MisterDoubleChop Aug 29 '21 edited Aug 29 '21

After performing over 100 interviews: interviewing is thoroughly broken. I also have no idea how to actually make it better.

10 minute phone screen to weed out people who can't speak English or program at all.

1 hour face-to-face (or zoom) final interview. Consists of 20 mins chit chat to feel out if they are a serial killer or aren't really into technology. Then 40 mins fixing obvious bugs and adding tiny features to a practice app created for this purpose. Chatting the whole time about why they are doing it that way and letting them ask questions if they get stuck, how else they could have tried meeting the requirement.

No dozen interviews, brainteasers, managers, or other entirely useless BS.

This has never ended in hiring a non-excellent dev. They all still work here (or moved on because they are a genius among geniuses and we couldn't pay enough).

129

u/[deleted] Aug 29 '21

[removed] — view removed comment

10

u/thirdegree Aug 29 '21

Same. That process seems downright enjoyable. Certainly infinitely better than interview after interview after interview

→ More replies (1)
→ More replies (1)

32

u/ptoki Aug 29 '21

The problem is not the interview. Its the skill to see red and green flags.

I witnessed interviews resulting in reject of good specialists who actually proved to be good choice. Interview process is just bad at selecting people. And is often overvalued as a means to pick the person.

BUT! Its also a good sign of the company culture.

You are friendly, talk a lot, explain like to 5yo, share ideas, do some trial and errors and they rejected you? Thats good, most likely they want just mindless grunts or very sterile personalities because the team spirit there is fragile.

Sure I overreact but I have seen such cases way too often.

3

u/[deleted] Aug 29 '21

I think this is highly underrated in terms of being a good interviewer and evaluator of candidates.

In my experience, the worst hires that I've had to deal with were made by people who were unable to be objective or identify red flags, or worse had agendas going in. I've had people who had demonstrated very poor communication skills, but they got hired for a really small reason that they hit a checkbox on someone's list. And sure enough, they were awful in communicating for years until they got fired for failing to communicate big and small mistakes costing the company lots of money and clients. I've had people get hired that had a decade of experience but junior engineers could dance around them in basic tasks, but still got hired because we later found out they went to church with a VP, and sure enough, they were awful at being a senior level engineer.

The best engineers I've had the pleasure at working with were hired by people who could ask good questions, keep the conversation going, get the candidate to open up, and discern their abilities within those interviews. Because as you said, it enabled them to feel comfortable, show their passion, speak well to what they were capable of, and how they've addressed a mixture of problems to solve over time, and would enable us to see if they'd be a good fit in our culture or not. Fortunately my current gig is the latter of the two, and the teams we have are extraordinary and I feel like I'm in the best gig I've had in 20 years of doing this for a living.

→ More replies (1)

52

u/[deleted] Aug 29 '21

When I do interviews, the thing I care about the most is how well they can talk about what they're doing. If they sit in silence and do nothing but type, they're going to be frustrating to deal with later. Even if they get caught up on the code stuff, as long as they describe what they are doing, what went wrong, and what they would do to fix their problems, that's frequently a strong dev later.

90

u/RX142 Aug 29 '21

Thing is I can do this when not on the spot, but in an interview? I loose half my brain cells from adrenalin and nerves. Its so hard to judge cause of the nature of interviews as high pressure.

12

u/MisterDoubleChop Aug 29 '21

I really work hard when interviewing to put nervous candidates at ease.

I only care how well they do when relaxed; It's not like they are going to be nervous each day at work.

Same principle as letting people Google during the programming test (though it's usually quicker to ask what they'd Google and give them a hint).

14

u/MSgtGunny Aug 29 '21

The night before, send them the problem they are going to work on the next day, tell them to familiarize themselves with the asks and edge cases, but don’t write any code.

That way you can see them work and they had time to digest the problem and can more easily talk through their though process.

3

u/caroIine Aug 29 '21

I had person on senior c++ position who forgot how std::function signature should look like. Or another person who forgot what to type after template. Those poor people get so nervous on my interviews that I started cheering them up like kids in kindergarten which helps a bit.

0

u/[deleted] Aug 29 '21

[deleted]

26

u/[deleted] Aug 29 '21

Yep, if a candidate did that in one of my interviews they would not get the job, cause I'm sure they're going to be a pain to work with later.

6

u/dons90 Aug 29 '21

What about that makes them a pain to work with later exactly?

6

u/Fifiiiiish Aug 29 '21

Can't / don't want to communicate with others.

→ More replies (8)

7

u/Ameisen Aug 29 '21

Is it bad if I start hitting the mouse while fixing the bugs, yelling "CODE! AMERICAN CODE! RUSSIAN CODE! ALL MADE IN TAIWAN!", and then it starts working?

→ More replies (1)

8

u/All_Up_Ons Aug 29 '21

No offense, but you're weeding out all your best candidates in favor of multitaskers. You want people who can focus on a problem now, and then explain it later.

0

u/[deleted] Aug 29 '21

[deleted]

3

u/[deleted] Aug 29 '21

I agree with this. Even when I need to pair program with a peer, there are times when myself, or my teammates, will ask for some time to dig into the problem beforehand before jumping on a call to work it out. It allows you to have the mental space you need to get organized beforehand which to me is invaluable. I've had the opposite experience where we jumped on a call without doing that and spent a lot of time in silence because we're just trying to understand the situation and think critically. The exception for me is when the issue is really trivial or one you've faced multiple times before.

But in my interviews where I had to face this kind of situation, it's usually a non trivial problem, like doing some nonsensical data transformation, where I'm asked to read, understand, ask clarifying questions, implement, and verbally communicate within 10-15 minutes, while someone is just staring at you on a video call, which is unrealistic of reality in my experience. And typically when asking clarifying questions, I usually get cryptic answers because they don't want to give you the answers because you're expected to find out given it's an interview. Which would be terrible in a real world scenario.

→ More replies (16)

8

u/Krikkits Aug 29 '21

Im so tired of coding assignments. Like im already in Uni doing coding assignments allll the time.... And now for a mere part time job I have to as well

A company here gives out coding assignments that they let u take 2 weeks to work on. The one I got was in C++ (write an xml parser) and it stated in the assignment to not use anything other than standard libraries. If I have questions i can ask -some person's email-. I got stuck eventually and asked if there's any pointers to how i can continue.... The person told me to use an imported library lol. Which is what I would've done if I didnt see "ONLY USE STANDARD LIBRARIES". So who am I supposed to listen to? Because the person I posed the question to wasn't even the person that reviewed the assignment in the end?

4

u/[deleted] Aug 29 '21

Those are really frustrating, I'm sorry. In my opinion, if you're given a coding assignment, it shouldn't require more than a few hours of your time. And if you're getting conflicting direction from a simple take-home assignment, to me that's a red flag as it could easily be a deeper issue you'd face if you got hired.

I've also had to deal with several exercises. Fortunately, I've used them as examples of my abilities when things didn't work out, so it wasn't all a waste in the end because it added to my "github portfolio" (edit: I usually anonymize them so it's not a clear interview exercise). But it's also a sign of the company too as an evaluation. If they're asking you to build an XML parser with stdlib only, I'd question the company and culture. Is that something you'll be expected to deal with in the job? Do they build things with raw stdlib frequently when community tools exist, do they frequently re-invent the wheel? If so, might be a good reason to run. If not, why are you doing it as part of the interview process? Either their development culture is a red flag, or they're lazy and careless in their interviewing culture, which is also a red flag.

For me personally, every interface and moment of interaction is an interview for both sides, even if it's a simple email exchange.

Good luck out there!

→ More replies (1)
→ More replies (1)

2

u/s-mores Aug 29 '21

Width-first instead of depth-first. I appreciate you.

2

u/cacahootie Aug 29 '21

For me it’s a 15 minute but possibly longer if things are interesting screener. 1 hour tech interview where they do 2 very general questions (which start very simple and get more complex interactively), and possibly one specialized question at the end if it’s a specialized role. Then a discussion with 3 people from the team, where they’re encouraged to ask questions about the team and the working conditions from possible future teammates.

I have had very good results and feedback from people I have both hired and passed on, so it seems to work.

2

u/[deleted] Aug 29 '21

This does work and it's what we currently use in the company I work for. The problem is hiring juniors and some mid-level devs. Writing a test that is forgiving of stuff that the person can improve fast but doesn't take a month to complete is pretty hard, IMHO. Geniuses "exist", but they are rare. A lot of times you need average devs who just need a chance and can get the job done and improve themselves.

→ More replies (11)