Given I reached that milestone myself in September I guess my experience is pretty relevant to your question. Short answer is that there isn't really one clearly defined path, a lot of it comes down to what you want to do in the field and how much effort you put in (and some manufactured luck). And the usual salary affectors like location and the company you work for.
You're unlikely to hit that sort of salary if you only ever want to just be a "normal" developer who writes code 35 hours a week. I know and work with plenty of people like that, they still enjoy their jobs and are still compensated well for their time (inline with their experience), but if you want the bigger money you need to bring more to the table.
More to the table really means one of two paths, in my experience. Either you focus soley on code, work your way up the seniority tree and eventually transition into a architecture role. Here you'll be working on projects from a high level, will decide how many different systems work together and drive the solution. But you won't actually be involved in implementing that solution, save for some early skeleton work.
The other path would be management. Some people try code for a few years and don't like it, so they aim more towards a "development manager" role, whereby you'd be the person that forecasts what work is done when, work out what resource is required and when, and have general line management responsibilites.
Although I've just said that there are two main paths... I took a third
My role is currently somewhere inbetween all of that. I'm employed as a Technical Lead and am responsible for a team of 10 and a team of 5. My job is basically acting as the glue betweem the developers and the rest of the business. I work with product to find out what they really want and distill that into technical requirements. I then take those requirements to my teams and turn them into useable products. Sometimes I'm just there in a mentorship capacity and can just let my team get on with it, sometimes I'm half-baking a solution and letting the team finish it off and sometimes I'm on the front lines churning through bug tickets like any other developer. I also have some line management responsiblity and work with other technical leads in my organisation to shape the near and long term futures of the business and our engineering teams.
For a bit of useful context...
- Graudated university in 2014 and got a BEng in Computer Science from a good uni,
- Started "real" work at an ecommerce company as a developer (building on what I learned there in my uni placement year), [£36k]
- Promoted to senior developer at the same company, took on team lead responsibilities, [£48k]
- Left after 5 years and moved to a consultancy in 2019, [£58k]
- Learned devops, got stuck in with AWS and honed my skills, got promoted to senior consultant and took on commercial and team lead responsibilities, [£75k]
- Left after 3 a half years and moved out of consultancy and into education as a tech lead, responsiblities as mentioned above, [£100k]
I'm 30, all I've ever known is computers and I thoroughly enjoy my job. I live in the north and work for a company that has offices all over the country, but I'm employed as a remote worker.
My degree is useless for my professional life and always has been but without it I'd have struggled to get my foot in the door. I am "lucky" in that I was given decent opportunities and a good foundation by my parents but I've also worked my behind off to get here.
- How quickly can this realistically be achieved (I'm not a dreamer who expects a massive salary from the get go)?
- What sort of starting salary would I be looking at?
- What would be the best / most specialized field to look in to?
- What would be the best steps to take?
- Depends how much effort you want to put in and what your current background is from a software point of view,
- As above, salaries range wildly depending on your experience even for junior roles, but I'd not expect less than mid-30s in the current climate,
- DevOps is a big thing, and rightly so, so I'd spend time and effort getting involved in that,
- First step would be deciding how badly you want the change and whether your life can accept the pay cut that the change would bring.
Post turned into a bit of a waffle, sorry. Will happily answer more specific questions if you have any.