It depends. What sort of tool do you use to monitor your client stack? Are they on the cloud? or on-premises?

It depends too. What kind of software are you using? Datadog? Nagios? Sensu? Do you proactively monitoring the server stacks? are they critical systems? If your job consist of 60% in talking your way out to get the service up again, and this is something you would like to do, then you are on the right track. If the 60% includes restarting the service, manual server reboot etc, you should get out.

In the next 5 years, 90% of the support and monitoring job will be paired with scripting to proactively resolve an issue automagically. Back in the old days, the industry used to run a Turing Complete machine to get the job done, therefore the drawbacks of it were required a consistent monitoring and maintenance.  Nowadays, the trend of microservices and immutable architecture with containers are rising rapidly, monitoring is still needed but in an automated fashion.

I've been working in the UK straight out of the university as a developer then now solutions architect (cloud and analytics), so above is based on my experience in the UK. My another 2 cent is that a lot of good company don't even have any presence in this forum, so I reckon the first step is to attend devgroups and build some network I guess.

hope this helps.