Seriously, been working as a software developer for 9 years now and never passed a single coding test.

The jobs I got were always the ones giving me weekend projects or just no coding test at all.

I have a job opportunity that looks exciting but they sent me this coding test link and I know I’m gonna fail for sure. Any tips aside from the obvious (practicing in advance on leetcode etc)?

    • thesystemisdown@lemmy.world
      link
      fedilink
      English
      arrow-up
      16
      ·
      2 months ago

      I’m trying to wrap my head around the CTO writing code unless it was from long ago when they were a developer. If that is the case, the CTO should understand that a better or more performant solution is likely over time. I’d say that was a bullet dodged. That’s very poor executive behavior.

      • wildbus8979@sh.itjust.works
        link
        fedilink
        arrow-up
        9
        ·
        edit-2
        2 months ago

        People have big egos. I’ve been in similiar situations as OP where the owner/CTO wrote a lot of the legacy code and weren’t particularly receptive to criticism. No acknowledgement either when said criticism turned out to be a client facing vulnerability later on.

        • tealeg@programming.dev
          link
          fedilink
          arrow-up
          2
          ·
          2 months ago

          Yeah. Owning code is about taking responsibility for it being in a satisfactory state, it shouldn’t be overly personal and you also shouldn’t attack people directly when the code has problems. Everyone makes mistakes, learning from them is there important thing.

      • tealeg@programming.dev
        link
        fedilink
        arrow-up
        3
        ·
        2 months ago

        It was a really small startup where the CTO was one of the founders and had written the first version of everything. I don’t mean to belittle what he did, I have a lot of respect for people building thins from the ground up.

        It was just a very odd episode and illustrative that you don’t always fail because you’re bad at coding.