Senior Software Architect
CurrentTrimble, like many large companies, participates in acquisitions. Each acquisition comes with a product and a team. During this process, acquired teams offer a mountain of potential that too often goes untapped. Our team's goal is to change that.Also, the MEP division at Trimble wants to adopt large scale inner source development. This means that on shared code bases, various teams must find it simple to switch contexts. The technology being used, patterns, code styles, cadence, and communication methods should all be as aligned as possible without smothering creativity and autonomy.My team is a platform architecture team that consists of a relative few full stack architects that must exhibit a few traits. We cannot be dogmatic about our preferred technology, patterns, or styles. We must always be open to new ideas and to explore newer technology before others. It is important to be both approachable and resolute at the same time, due to a prioritization of outcomes. And we must be familiar with the technology, patterns, and contexts that we advise the rest of the division on. We are currently most reliant on Microsoft Azure for serverless, .NET for rest services, the dotnet new commands for project templates that we provide, Angular for our front ends, and integration with Docker for local testing and builds.As of today, this has led to the following achievements. I've refactored an entire internal NuGet infrastructure to be modern, optimized, and documented. We've piloted a large Azure Function based serverless ecosystem, as well as Azure App Configuration reliance for shared cloud settings, and several Angular portals that interact with these ecosystems. And we maintain many project templates, deployed through an internal dashboard, that allow new projects to avoid the ceremony of getting aligned to the platform standards.