5 ms·

Which in fairness, is a reasonable competency to test for in an interview

• jagged-chisel 2y ago
  Indeed. But I need clarity on which skill they want to test in thirty minutes.
  • klyrs 2y ago
    Speaking as an interviewer: nope, you're not being tested on a single skill.
    • jagged-chisel 2y ago
      See, that's what the multi-round, two-hour interview blocks are for. Each interview tests a different set of skills. If you're testing on algorithm implementation and requirements gathering in thirty minutes, you're not testing for the skills you claim to be testing for. There's no way you're getting a good (let alone accurate) picture of the candidate's ability to gather requirements and implement those requirements, especially if your selection tactic is to deny them because they didn't get the PhD answer. You're testing for how good of a minion this candidate will be.
      • klyrs 2y ago
        > especially if your selection tactic is to deny them because they didn't get the PhD answer. > You're testing for how good of a minion this candidate will be. I agreed with much of what you had to say up until this point. Well, and I'm not about 2-hour interviews either; that's too disruption to my work. To me, a coding challenge is a conversation piece. I will see some skills like "can the candidate get a software project in their top-listed language on their cv running in less than an hour," and I do judge questions they ask or don't ask. But then, I don't just pull a leetcode challenge from the shelf. My favorite "coding challenge" isn't actually that challenging (which can send leetcode-grinders spiraling); it's about the journey and not the destination.