never_snapped
mgridley is right in that the vast majority of business applications require almost no math, and those that do are usually so specialized that an advisor figures out those equations first as they require a specialized domain knowledge.
Want to build tools that developers build upon? You may need the math, but you can usually already find the algorithms in research papers.
The only exception to this rule (that I can think of) are very specialized niches of development, which ultimately become commoditized and consumed by developers without the math anyways.
It was exhausting as the people on call didn't have the power to actually fix the system. Instead, they would have to walk someone else through the steps over the phone. If it took a code change to fix the system, too bad that was at least two weeks of red tape, and every single time the error occurred they had to page the person on call to walk the person through over the phone to verify it was the same error and nothing could be done.
Think "big business," "division of responsibilities," "accountability," inept management who never had to suffer under the policies they demanded, and a toxic culture which was proud to "give everything they have for the product."
Luckily, I don't work for those shitty companies anymore.
Whereas the certifications you described enabled a person to write reports, recommend products of a particular vendor, and maintain software/hardware configurations -- a job which is still being automated and taken over by developers without certification, particularly in smaller companies (devops).
Only time will tell though.
One of the biggest flaws of the CMS space is assuming or requiring that they are completely in control of the application. When in reality, all I need is a CMS for is a subset of pages. At most it can be in control of a subset of domains -- but never all of them.
For example, a common requirement is a faq-like page, a blog section and easily being able to edit other public pages (about, team, contact, index, etc.). Then the real bread and butter of the application is behind some sort of login wall or is all internal and requires custom code and logic. I shouldn't have to stand up two applications to achieve this (increasing application maintenance by an order of magnitude in the process), fight the cms, or roll my own every time.
Ideally I should be able to tell a CMS a single page it can control (or subset of domains), and it takes the existing content and allows editing and saving of it.
Start with that idea, then add premium features like easy a/b testing.
edit... Also, in my experience CMS is a race to the bottom when it comes to client quality. You end up making very little money per project as the person looking for a wordpress/cms solution is either pinching pennies or just plain cheap. The real money clients come from those looking for real solutions (which are almost always custom solutions) to enhance their business' bottom line, not give it a crappy web presence that wont change for the next 10 years.
..edit, found out they hard coded the string as constant in the app, smh.