MCSE is Back!
This week Microsoft announced some major changes in our certification program. Why? Well with the Cloud taking off, it’s time for an update.
MCSE is now Microsoft Certified Solution Expert. If you remember 20 years ago, here in Texas we had problems using MCSE, because then “e” was Engineer. In Texas to call you self and Engineer, this is a special licensing process, that just doesn’t work in IT. So we had to use MCSE, not the work Engineer. I like the use of Solution Expert.
Here is what the PRESS Release said:
Because cloud computing talent is in short supply, Microsoft has reinvented its flagship credential, Microsoft Certified Systems Engineer, for the cloud. The new Microsoft Certified Solutions Expert (MCSE) shows employers and peers that those certified have the skills to do the job in an expanding market. Forecasts show that public and private IT cloud services will generate nearly 14 million jobs worldwide between now and 2015.1The MCSE is the flagship credential for those who want to lead their company to the cloud and is the target credential for established IT professionals and developers who have expertise working with Microsoft technology solutions.
“The new Microsoft certifications are raising the bar across the industry and reflect industry shifts that require a broader knowledge base and deeper skills across solutions that cloud computing requires,” said Don Field, Microsoft’s senior director of Product Management. “The Microsoft certifications reflect the experience and skills needed to build, manage and evolve solutions in a cloud-based environment, ensuring validation of real-world skills for individuals and helping hiring managers identify the best-qualified job candidates.”
The new framework will help IT professionals and developers navigate their own path, while also making it clearer for hiring managers to identify credentials that offer the greatest value to their organization’s needs.
Here is a short video talking about what has changed.
Remember you can download the Microsoft Private Cloud today at https://aka.ms/syscntr
Here is the behind the scenes why we made the changes: