I worked as engineer for 15 years and then management for the last 2 years. The urge to go back to engineering never stop. What keeps me in management is seeing how I can create the environment where engineers are able to do their work.

If I go back to being an engineer, I won't be able to make sure product requirements are clear, priorities are correct, team members will have a chance to practice skills they don't get to do at work. At the minimum, protecting my engineers from stupid back to office policies that were enforced just because the CEO felt lonely one day. Would someone who has not worked as an engineer understand the feeling of stairing at the screen for 8 hours not able to start anything due to burnout is the worst feeling ever? Will they hear the grinding wheels when soneone used the wrong term during meetings?

There are just so many things that I can do for MY engineers, exactly what I wanted when I was still an engineer. I don't trust others to provide that so I take it on myself to do it. Granted, I need support from upper level for this to happen so it's an important aspect for me when I apply for jobs.

Moving is possible but difficult.

I tried doing that few years ago but you literally start from step 1. I went against a lot of recruits, that were single, and fresh to the job scene. They are more than ready to slave away the hours to impress their managers.

I on the other hand wasn't single, not ready to over work, and the salary offered for starters was not impressive after all these years.

Suffice to say, I feel much better now knowing how much I make for the hours I put in.

Yay, something I can talk to.

I'm a middle manager in tech delivery. Started in a different industry, moved into the saas world at the right time, became a dev, became a contractor, made lots of money, had a family, needed more regular hours so went the management route, less money, more stress. About a year ago I took on a new role which has me across approx 10 directs each who have their own squads of 6 to 10 people.

I don't hate it but it is hard work. And yes it is objectively harder and more stressful than being a developer, simply because of the level of accountability that I personally take.

In terms of expertise. I know a deep amount about one platform, a moderate amount about three others and I have no fucking clue about the rest. Integration, for instance. Yet I'm accountable for delivery and eye watering budgets. I'm sure the devs have a similar opinion of me as to what's posted elsewhere in the thread, that I don't understand the specific technology hence shouldn't be directing the work stream, but the thing is - thats not the role.

The role is to manage money and people. The array of brilliant technologists who i've seen step into leadership roles then slowly drown and fail is distressing. So when I'm looking for leads to bring into positions, a lot of the time I'm looking for people who naturally want to step forward and want to lead. Most of the time they do well even without the full depth of tech.

I think this is the link back to your question. Like, can you go back to being a dev? If your promotion to management was as a result of being the most experienced dev, then yes absolutely, you should fit back in fine. If you were promoted because you were the voice in the team that said why or how or what if or let's do this, then I'm sorry. Leadership will seek you out once again.

Do you really need the IT bit in there?

Management sucks. Full stop.

I'm an IT worker bee and I agree, management sucks

90% of management in any job are useless because most of the them have never done or have not done the job(s) of those they manage for so long they have little to no idea how to do it . And once you get into executive positions the uselessness is even greater. Just soulless vomit spewing moronic yes-men.