I know this is a very generalized question, as it depends on the company, product, position, etc. But in general, what sets someone apart as ready for a senior position over an intermediate or junior position? Experience I would think would be a big one, but say you have a candidate that shows problem solving abilities to solve code problems, but is newer to the tech field vs someone who’s been in the field x years, does the first guy have a shot without really knowing the ins and outs of working as a software engineer, hoping to pick it up quick?

  • remotedevOP
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I was asking about interviewing as a newcomer to the software dev world. I’ve been going through an online school to learn the fundamentals, and about to start their program that when you finish allowe you to target higher positions when job hunting. I don’t question the skills part of the program, I’ve just been wondering how they would be able to prepare us to go right to more senior positions out of the gate and get other companies to accept us at that level.

    I feel like imposter syndrome is bad enough without feeling like any tiny mistake you’d make would have your whole team thinking you’re in way over your head.

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

      I feel like imposter syndrome is bad enough without feeling like any tiny mistake you’d make would have your whole team thinking you’re in way over your head.

      Impostor syndrome sucks, but someone who just joined a new organization, is statistically, absolutely in way over their head.

      The hard part to come to grips with is: that doesn’t make them an impostor, it makes them a developer who just joined a new organization.

      Now don’t get me started on teams that make people feel bad for that. They suck and they deserve the revolving door of non-help talent that they end up invariably hiring over and over, because they can’t retain talent.