• Sam
    link
    fedilink
    arrow-up
    85
    arrow-down
    1
    ·
    1 year ago

    When I’m doing coding interviews I always like to start off and say I’m a big fan of very long variable names. “As descriptive as you can be” I say. Then I get to my first for loop. Instead of i I use “iterator” and then when I start a nested loop I use “jiterator” and it always gets a laugh.

    • Dandroid@dandroid.app
      link
      fedilink
      arrow-up
      21
      ·
      1 year ago

      I used to conduct coding interviews at my old job. If someone came in and had some humor like that, it would be big bonus points in my book. Being someone I would like to be on a team with is very important. Plus, I think it shows confidence and being comfortable in situations that make most people nervous.

      • Hazama@lemmy.world
        link
        fedilink
        arrow-up
        16
        ·
        1 year ago

        I’ve been at two start ups and they had me interview people. Honestly this is what I looked for. I’d ask basic questions to prove you had an idea about coding, but I can teach someone to code, I can’t teach someone to be someone I like working with.

        • KairuByte@lemmy.world
          link
          fedilink
          arrow-up
          14
          arrow-down
          1
          ·
          1 year ago

          You can teach them to code if there is an underlying level of logic to build off. I’ve met a few people in life who I know for a fact will never code, no matter how smart they generally are.

      • Sam
        link
        fedilink
        arrow-up
        5
        ·
        1 year ago

        And even if it didn’t help my chances directly like that, even getting a small chuckle would help me be more comfortable and confident.

      • DreamButt@lemmy.world
        link
        fedilink
        arrow-up
        4
        ·
        1 year ago

        Honestly finding someone who can relax and intergrate into your team culture is arguably more important that anything