Engineering leadership · Platform · Developer experience
I'm Matt Willhite, a Tech Lead Manager on the Platform team at FloQast. I take ambiguous, cross-team technical problems and turn them into repeatable systems that raise delivery speed, reliability, and what the organization is capable of.
Four kinds of problems I keep getting handed, and what happens when I take them.
A team I joined went from slow, contentious reviews to four times the velocity per developer in four months. The mechanism was not heroics. It was contribution guidelines, pairing, swarming on stuck work, and making cross-team dependencies visible. I plan quarters around both delivery metrics and individual growth, assigning work by experience and appetite.
Selected for a small task force to lay a platform foundation meant to last five to ten years, I led the team with the largest repository migration scope and finished in the first week of a two-week window. In the next phase I ranked serverless workloads by cost and latency, moved the worst offenders to containers, and cut monthly operating cost by roughly 60%.
A release-pipeline configuration was silently masking QE test failures across more than 50 applications, a quality problem with compliance consequences. I mapped every owner, opened a ticket per instance, and tracked closure with Product until it was done. Nobody asked me to. That is usually how the important ones go.
I run recurring enablement sessions on production debugging, Git and review collaboration, architecture patterns, and lead-time analysis. I pioneered TypeScript adoption for a business unit and its patterns spread to neighboring products. When a new platform team inherited an audit-ingestion prototype in unfamiliar technology, we rebuilt it for resilience and learned the stack together.
Seventeen years of shipping, the last several spent making other engineers faster.
Case studies from the work above, with names abstracted and only validated numbers.