I'm currently a Senior Content Specialist, writing technical documentation for software.
In my past, I've designed and coded content systems that provide knowledge and technical resources to multi-channel/region/language businesses, and write content for them, covering areas like APIs, proprietary application help, media assets, training, project artefacts, compliance documentation, and best practice guides.
My features were highly successful in providing relevant searches and analytics, versatile structure, and enabling SMEs (not just one or two technical writers) to create consistently-formatted, semantic content.
I devised style guides, created standards, and mentored and assisted others with UX and presentation. I edit and review kindly.
This webite is an example wiki-like content system I wrote from scratch. Here's a style book for it.
I was a senior/lead software developer, working on large commercial software projects, Agile, ways of working, engineering, practice, capability, and recruitment. My last focus was ServiceNow.
Example: I created a tool to produce bespoke quotes for manufacturing processes. It figured out how to make things, modelled the end-to-end process, and costed everything, including business models and margins.
It simplified bespoke quotes enough to save hours per estimate, and allowed executives (rather than managers) to create and approve quotes. After becoming established, it was used as a basis for pricing new standard products.
Sometimes, it made better decisions than process experts, and provided hints to assist with those decisions. It was trusted.
Its success depended on: