I won't be the only one on the call so I can't just give him an impossible interview. we're planning the interview together today. how do I make sure we can't hire him?

luckily his background doesn't line up with what our team does, at least from his resume -- god it's the worst to read from the formatting alone. so maybe I can just lean into that? my team is part of a software infrastructure group and we're tasked with making the rest of the org stop sucking ass at software development -- secrets don't go in git repos type of stuff. so people skills and writing little bits of code that ensure the culture changes over time. his background is in operations and maybe a little software dev.

I need suggestions for questions that will make him a no go. I can't take someone who worked for Palantir, for nearly a decade no less, seriously.

  • ElHexo [comrade/them]
    ·
    7 months ago

    Assuming that you're in America, is it common to not be able to veto any applicant without giving reasons?

    • silent_water [she/her]
      hexagon
      ·
      edit-2
      7 months ago

      the team makes a decision together so they'll ask for reasons. so no, I can't just veto, just sandbag. candidate is also in the UK, so idk what HR is legally required to disclose to them.