AddressThis wont be easy.
There are a lot of Engineers, they have strong opinions and they don't currently have much Architectural oversight. Each group is kind of doing their own thing. They need you to help and guide them with technology decisions. Allowing them to talk, listening, guiding the conversation and getting some kind of commitment.
This company are dynamic, have initiative, they don't stop, they work fast, plenty of amazing talent, lots of innovation, cutting edge stuff, they are daring and they have a go.
You've probably worked out their Architecture maturity is pretty low for the size of company they are. Its a bit wild. They've created a number of new roles to act as the Lead Architect across each domain. This role is focussed on Cloud, Platforms and Infrastructure
You'll take ownership of the Cloud Platform Strategy in terms of working with headless vs non headless, GCP vs Azure & Kubernetes. Looking at Cyber related stuff within Cloud, Key Management. There is some migration work. They are about to build a developer portal - do they build a solution vs purchase one. Outside the platforms they look after API's, assessments from a Cyber perspective, they own some of the assets but not all of them.
The role has a mix of Enterprise Architecture & Technology Architecture - what does it look like currently? what's the domain capability? blueprints? target state? where are we today? maturity level?
They are using frameworks like Urgency, Feasibility & Opportunity- using data spores from architecture to guide business and technology teams. Working with the other Lead Architects to see which is common or unique across each domain, can it be sharable. Do we build it or if its being built, how is progressing?
We are looking for an architect who can design systems from application data strategy. Not an orchestrator.
This team is all about Cloud - but it doesn't matter if you are Azure, AWS or GCP.
If you have any questions, feel free to email or call me - *******@theonset.com.au / 0438984***
