
A hands-on ServiceNow architect, technical lead, designer, developer and support engineer, 10 years on the platform and 6 on BMC Remedy before it. Every engagement was my own hands on the platform, not a team's, and the support packages are run the same way.
Telecoms, defence, government, utilities, finance, retail, aviation, media, gaming and hospitality do not run the same service desk, and they did not build their platforms the same way either. Some were built on the base and have upgraded quietly for years. Some were built around it and every release is a negotiation.
Having seen both, from the inside, is the point. A design decision on your platform is made by somebody who has watched that decision play out ten times elsewhere - which customisations cost their owners most, which integrations survive a replatforming, what a four-hundred-domain MSP instance does to a migration, and what a first instance needs so it is still tidy in year three.
Before architecture: second-line broadband support, a service desk seat, then administering the tool. Knowing what it is like to be on the receiving end of a badly built process is why I build platforms to be supported, not just delivered.
The engagements are on the home page; the full history, with dates, is on LinkedIn.
An architecture question, a platform in trouble, or a support package: support@alchemist-it.uk.