I have been working at a large bank for a few years. Although some coding is needed, the bulk majority of time is spent on server config changes, releasing code to production, asking other people for approvals, auth roles, and of course tons of meetings with the end user to find out what they need.

I guess when I was a junior engineer, I would spend more time looking at code, though I used to work for small companies. So it is hard for me to judge if the extra time spent coding, was because of me being a junior or because it was a small company.

The kicker, is when we interview devs, most of the interview is just about coding. Very little of it is about the stuff I listed…

  • burningmatches@feddit.uk
    link
    fedilink
    English
    arrow-up
    14
    ·
    1 year ago

    This kind of thing is common in many jobs — as you become more experienced, you take on more management responsibilities. It’s inevitable but not always ideal.

    The alternative is that you get managed by people with no first-hand experience of actually doing the job, but it can also mean that people get promoted into management roles without necessarily having management qualities (which can be the worst of both worlds — you lose a good coder and gain a bad manager).