What are your worst interviews you’ve done? I’m currently going through them myself and want to hear what others are like. Dijkstras algorithm on the whiteboard? Binary Search? My personal favorite “I don’t see anything wrong with your architecture, but I’m not a fan of X language/framework so I have to call that out”

Let me hear them!

(Non programmers too please jump in with your horrid interviews, I’m just very fed up with tech screens)

  • Mercuri@lemmy.world
    link
    fedilink
    arrow-up
    48
    ·
    28 days ago

    As the interviewee?

    I show up at their office for a round of interviews. IIRC it was 4 interviews of about an hour each. Every single interviewer comes in 5-10 minutes late. They all look completely exhausted. Unprompted, they all commented that “yeah, this is a start-up so we’re expected to work 80 hour weeks. That’s just how it is.” I did not take that job.

    Another place wanted to do a coding “pre-screening” thing. You know, where you go to a website and there’s a coding question and you code it and submit your answer. THIS place wanted you to install an extension that took full control of your browser, your webcam, your mic, etc. So it could record you doing the coding challenge. No, thank you.

    As the interviewer? omg, the stories I can tell.

    We had a guy come in for an hour interview. We start asking him the normal interview questions. Literally everything he says is straight up wrong or he says, “I don’t know” and then just gives up and doesn’t try to work out a solution or anything. But we have a whole hour with this guy and as interviewers we’ve been instructed to use the full hour otherwise candidates complain that they weren’t given a fair chance even when it’s TOTALLY obvious it’s going to be a “no-hire.” So we start asking this guy easier and easier questions… just giving him basic softball questions… and HE STILL GETS THEM ALL WRONG. We ask him what type of variable would you use to store a number? He says, “String.” WHAT?! I’m totally flabbergasted at this point. So finally I get a brilliant idea: I’ll ask him an OPINION question! There’s no way he can get that wrong, right? Looking at his resume, it has something like “Java Expert” on there. So I say to him, “It says on your resume you’re a Java Expert. What’s your favorite thing about Java?” His response? “Oh, I actually don’t know anything about Java. I just put that on my resume because I know they used that at a previous company.” So now on top of this guy getting every question wrong, we’ve established he has also lied on his resume, so basically just red flags EVERYWHERE. Finally, after a grueling 45 minutes we decide to give up asking questions and just end with the whole, “So we like to reserve the last bit of time so you can ask us questions. Do you have anything you’d like to ask?” Without missing a beat, this guy goes, “When do I start? I feel like I NAILED that interview!”

    At another company I worked at, we would do online interviews that took only an hour. The coding portion of the interview had a single question: “Given a list of strings, print the contents of the list to the screen.” That was it. Sure, we could make the coding question harder if they totally aced it, but the basic question was nothing more complicated than that. The candidate could even choose which programming language they wanted to use for the task. That single question eliminated half the candidates who applied for the job. Some straight up said they couldn’t do it. One person hung up on me and then when I tried to call back they said the fire alarm went off at their place and they would reschedule. They never did. Many people forgot that I could see their screens reflected in their glasses and I could see them frantically Googling. There was one candidate that did so insanely poorly during the interview that we believe it must have been a completely different person that had gone through the initial phone screen, so basically they were trying to bait-and-switch.

    I have a bunch of other stories but this post is already getting quite long.

    • conciselyverbose@sh.itjust.works
      link
      fedilink
      arrow-up
      23
      ·
      28 days ago

      Unprompted, they all commented that “yeah, this is a start-up so we’re expected to work 80 hour weeks. That’s just how it is.”

      lol I’m walking out the minute they say that.

        • conciselyverbose@sh.itjust.works
          link
          fedilink
          arrow-up
          6
          ·
          28 days ago

          I’m genuinely terrible at not falling for sunk costs and have a bad habit of just letting inertia take me.

          But unless you’re offering me 100k a week (in which case I’ll work for maybe a month before burning out), I’m not working a fucking 80 hour week.

        • Mercuri@lemmy.world
          link
          fedilink
          arrow-up
          5
          ·
          28 days ago

          At the time it was like watching a train wreck. This was much earlier in my career and I was like, “there’s just no way, right?”

          I did get lunch out of it.

    • Scrubbles@poptalk.scrubbles.techOP
      link
      fedilink
      English
      arrow-up
      16
      ·
      28 days ago

      I resonate with so many of these. I hate the tech prescreen, but morons, cheaters, and liars make it necessary. The prescreen is purely there to weed out a good, like you said well over 50% of candidates right there.

      And I’ll throw a thorn at you, I do store numbers as strings… When I’m dealing with currency lol. I’m 100% sure that’s what he meant of course, because he was thinking about float precision and how you wouldn’t want to risk currency imprecision during serialization or anything! Should have given them the job! /s