• thanks_shakey_snake@lemmy.ca
    link
    fedilink
    arrow-up
    9
    ·
    10 months ago

    That sounds like a good plan in many situations… But how do you handle candidates who say something like “look, there’s heaps of code that I’m proud of and would love to walk you through, but it’s all work I’ve done for past companies and don’t have access (or the legal right) to show you?”

    You might just say “well the ideal candidate has meaningful projects outside of work,” and just eliminate the others… But it seems like you’d lose out on many otherwise great candidates that way.

    • Beej Jorgensen@lemmy.sdf.org
      link
      fedilink
      arrow-up
      1
      ·
      10 months ago

      But how do you handle candidates who say something like “look, there’s heaps of code that I’m proud of and would love to walk you through, but it’s all work I’ve done for past companies and don’t have access (or the legal right) to show you?”

      It never once happened. They always knew in advance, so they could code something up if they felt like it.

      • thanks_shakey_snake@lemmy.ca
        link
        fedilink
        arrow-up
        1
        ·
        10 months ago

        Interesting, thanks. Do you give them any ideas or guidance as to what they should whip up? Or just leave it totally open-ended for them to figure out?

        • Beej Jorgensen@lemmy.sdf.org
          link
          fedilink
          arrow-up
          2
          ·
          9 months ago

          I always left it open-ended and that seemed to work. Part of the interview was seeing what they’d come up with. I’m pretty sure people always brought things they’d already written.