this post was submitted on 02 Aug 2025
204 points (96.8% liked)

Programming

21924 readers
610 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
all 33 comments
sorted by: hot top controversial new old
[–] Kurious84@lemmings.world 6 points 5 hours ago* (last edited 5 hours ago)

If you give live coding tests you're a moron. Here's why. Not all but many of us coders are autistic or highly functional autistic and our brain shuts down in high stress social situations with someone watching over you. Plus whiteboarding when I never fucking whiteboard anything. But get us alone in a room with a task and we'll whip your ass.

My last boss pulled this on me. I almost didn't get the job. Then I told him to assign me any project as homework. Overnight I produced a program that blew them all away. Got hired.

[–] resipsaloquitur@lemmy.world 10 points 8 hours ago (3 children)

I disagree. I give live coding tests. I very much don’t want the candidate to be stressed. I provide a written and verbal description of the (simple) problem, and provide unit tests. And I talk them through it if they run into problems, but try to give them space to work it out.

I’m not sadistic. I want to see if they can write code.

The few times I skipped the live test because of practical reasons or they were “too senior” I absolutely regretted it.

[–] staircase@programming.dev 2 points 5 hours ago* (last edited 5 hours ago) (1 children)

You seem to be disagreeing with something that isn't the main point of the article.

That you take those steps doesn't mean candidates aren't stressed, despite your intentions.

[–] resipsaloquitur@lemmy.world -1 points 3 hours ago (1 children)

Sorry an interview is stressful to candidates?

[–] toynbee@lemmy.world 2 points 3 hours ago

Fuck yes, and that's just a regular one.

[–] BrianTheeBiscuiteer@lemmy.world 2 points 6 hours ago (1 children)

Interesting. What do you think happened with those you didn't test? You think they were making stuff up or senior at their job is a far cry from senior at your job?

[–] resipsaloquitur@lemmy.world 1 points 6 hours ago* (last edited 6 hours ago)

Not sure. One seemed either incredibly timid or just way in above his head on simple tasks. I assigned him a bug and had already narrowed it down to a particular return code, in a particular call tree. He could have set 20 breakpoints and found the bug in five minutes. Or put unique error codes and found the bug in ten minutes.

But weeks later he was still asking questions and eventually just moved on without solving the bug or even finding the cause.

Maaaybe he would have aced the live coding test, but I doubt it. He just never seemed to "get it" and I think the live test would have reflected it.

But by "senior" i mean decades of experience. No quibbling about job titles.

[–] cole@lemdro.id 5 points 8 hours ago (1 children)

fully agree. we're actually reintroducing live coding interviews into our process because so many candidates made it onsite who then showed that they didn't really know how to code

[–] staircase@programming.dev 5 points 5 hours ago* (last edited 5 hours ago) (1 children)

The article isn't saying don't check, it's saying that live coding interviews are a bad measure.

[–] VoterFrog@lemmy.world 1 points 4 hours ago (1 children)

I'm not sure that offline or alone coding tests are any better. A good coding interview should be about a lot more than just seeing if they produce well structured and optimal code. It's about seeing what kinds of questions they'll ask, what kind of alternatives and trade offs they'll consider, probing some of the decisions they make. All the stuff that goes into being a good SWE, which you can demonstrate even if you're having trouble coming up with the optimal solution to this particular problem.

[–] NotMyOldRedditName@lemmy.world 1 points 2 hours ago* (last edited 2 hours ago)

... that's why you do a follow up interview and review their code, and maybe leave some things a little ambiguous to see if they ask you questions (telling them it's okay to email questions and mostly expected)

Why did you decide to do ABC this way? What do you think about having done it XYZ way instead?

I know you didn't have time to write a full test suite, but what areas of what you wrote would be best to focus on tests and why?

You can ask them so many things about what they wrote.

That's like... how it works in the real world. They ask questions to product as they come up, they get questioned on their work in code reviews

Unless you work somewhere where you pair code 100% of the time anyway...

If you just look at it as a pass or fail and are not doing a detailed review with them after, you're doing it wrong.

[–] Cratermaker@discuss.tchncs.de 13 points 10 hours ago* (last edited 10 hours ago) (2 children)

I can see how this could be unfair, but working as a dev sometimes does require you to be on top of things in a high stress atmosphere. For example, what if you're proposing an excellent technical solution in a meeting but some jaded older engineer is hard to convince? If you can't outline your thinking in that scenario, your solution could be discarded just because someone was louder than you. As someone who used to have performance anxiety, I believe it's generally something you can and should practice for. On the other hand, if there really isn't a need for this type of skill, it totally makes sense to avoid creating interview environments where you are filtering candidates based on it.

[–] martinb@lemmy.sdf.org 3 points 6 hours ago

I did stress test interviews for DevOps positions. I explicitly told them that and gave them a task and a time limit. I would watch what they did and there was nothing out of bounds as long as they were solving problems. For example, I would give them an account in cloud provider and then task them with spinning up a k8s cluster with a few basic services and make it scalable, then watch and heckle as they googled around and brought up services. The objective wasn't to complete the task though, it was too see how they approached problem solving. Good times.

[–] silasmariner@programming.dev 3 points 9 hours ago (2 children)

Good enough example, although I would've picked dealing with a live incident

[–] BrianTheeBiscuiteer@lemmy.world 1 points 6 hours ago

That sounds fair. I hate "tests" that involve things you'd never do on the job.

[–] Cratermaker@discuss.tchncs.de 2 points 9 hours ago* (last edited 9 hours ago)

Yeah, that too! When you have some non technical manager breathing down your neck, you might have a hard time not fumbling around even if you normally could resolve the issue in no time.

[–] FizzyOrange@programming.dev 11 points 12 hours ago (1 children)

IMO this is not a helpful way to put it. They measure skill under stress. Stress may have a large effect on skill level for some people but highly unlikely that it's so large that performance is completely random.

[–] tyler@programming.dev 2 points 11 hours ago (1 children)

Nah, they measure memorization under stress. Can you recall that tidbit of information to solve the problem the interviewer has given you? If you never have needed to solve a problem like that then you’re shit out of luck, even though solving that problem for the first time (by whomever) definitely didn’t do it under stress in a job interview.

[–] FizzyOrange@programming.dev 5 points 11 hours ago

Some bad interview questions are like that, sure. But they're supposed to be things you are very unlikely to have done before and can reasonably figure out. It's not too hard to come up with simple questions like that. (Though I will grant many people don't seem to bother.)

[–] frezik@lemmy.blahaj.zone 25 points 14 hours ago (2 children)

Our industry has no idea how to hire people. Our interview processes are almost designed to filter out obviously bad candidates while accepting that some good candidates will fail, too. Getting a specifically good candidate is almost luck.

Remember this if you're bummed about a string of rejections.

[–] blarghly@lemmy.world 11 points 13 hours ago (2 children)

I mean, this is essentially all hiring processes.

The way to get actually good employees is to be the sort of place that actual good employees want to work for. Good pay, good work-life balance, good managers and company culture, work that is enjoyable and meaningful. Then, you hire through social networks. The founders start off as people who meet through informal social networks. They hire their friends. And then they ask their friends for further recommendations. The best way to know if someone is a good hire is if you have actually worked with them before. And at this point, the interview is really just hanging out, shaking hands, and having lunch before you sign some paperwork.

[–] Iteria@sh.itjust.works 5 points 12 hours ago (2 children)

The problem with only hiring people you have met personally is that you miss out on a whole world of people who would be great to work with but had no chance of ever meeting you or your network. I agree that network recruiting is the safest route, but having diversity in your employees is great. If you only hire through your networks you'll see quickly quickly how you only get one kind of person.

I have seem this happen a lot in smaller companies. It's also the story of how I'm typically the sole woman in the department. I by happenstance happen to seed my professional network from college with a lot of men (because I accidentally picked a college that like 80% men). I'm a unicorn because many men's networks include so few women since in IT they tend to be non-traditional and/or generally excluded from younger men's social groups.

I get tapped via my network all the time. But if the company basically only does referral based hiring me and perhaps one other woman is there for the whole engineering department. It's way more balanced at 20%-30% of the department at companies that don't do this. There is some value in shotgun hiring even if it has a higher fail rate than referral hiring. Different kinds of people can bring fresh perspectives and considerations.

[–] lagoon8622@sh.itjust.works 1 points 10 hours ago

Great points. Thanks for sharing your perspective

[–] bitcrafter@programming.dev 4 points 12 hours ago (1 children)

So in other words, focus on hiring extroverts who are great at forming social networks.

[–] blarghly@lemmy.world 2 points 11 hours ago (1 children)

I mean, kind of. I wouldnt say extroverts, so much as "people with good/decent social skills". Introversion/extroversion is a sliding scale, not a dichotomy, and it refers more to your propensity to gain or lose energy from social interactions - not your ability to socialize.

While many more introverted people find socializing more difficult in general, there is no reason why they can't develop the skill.

[–] bitcrafter@programming.dev 3 points 9 hours ago

Sure, but if someone is more introverted, then, even if they have amazing social skills, they will have a much harder time forming social networks with a lot of reach because it takes more energy for them to do so, whereas it is a lot easier for a more extroverted person to do this.

[–] FizzyOrange@programming.dev 3 points 12 hours ago (2 children)

You don't know how good you've got it. The hiring process in other industries is much worse.

[–] bitcrafter@programming.dev 2 points 5 hours ago

Story time?

[–] staircase@programming.dev 1 points 4 hours ago

for those who this affects, this lands badly

[–] oshu@lemmy.world 4 points 15 hours ago

my current company does live code design challenges instead of straigt codong exercises. seems to work well

[–] Venat0r@lemmy.world -1 points 14 hours ago

is the point of a question like that not to measure how you perform under stress? the guy who posted it in the screenshot doesn't seem to realise that either though...