Technical depth.
Business outcomes.
I lead through technical depth, systems thinking, and the relationships required to turn messy problems into useful, durable outcomes for the business.
How I think
Ambiguity is where I operate best
I do some of my best work when the problem is real but the structure is still forming. Defining missions, recruiting talent, establishing governance, and shipping useful systems usually happen in parallel.
I still write code
I stay hands-on in architecture, tooling, and security decisions. My teams trust my technical judgment because I still do the work required to understand tradeoffs, not because I used to be technical.
Security is a design principle
Not a gate. Not an afterthought. From API security CI tooling adopted across Ford to protecting $12M/day at Dell — security is embedded from day one.
Relationships drive outcomes
The best technical work happens when the right people trust each other enough to solve problems quickly. I invest in cross-functional relationships because they remove drag from delivery.
Organization building
The UEV Platform Tools organization: promoted from within, then asked to define the mission, solve the operating problems, and scale it into a global team of 17 engineers.
What I Built
- 01Defined organizational charter and mission for Platform Tools
- 02Scaled the team from a small group to ~17 engineers globally
- 03Established architecture governance and security strategy
- 04Created tooling strategy spanning engineering, finance, supply chain, DevOps, data, and AI
- 05Enabled development of software change management systems from scratch
- 06Delivered CI/CD infrastructure and release tooling
- 07Led AI enablement integration across the entire SDLC
How I Lead Teams
- 01Lead from the front — I contribute code and stay in the technical details alongside my team
- 02Hire for ownership mindset and technical curiosity
- 03Give teams clear missions with decision-making authority
- 04Earn trust by shipping, not just directing
- 05Build cross-functional relationships to unblock teams
- 06Invest in developer experience as a force multiplier
Technical leadership
I don't just manage engineers. I stay in the architecture, security, platform, and delivery details long enough to help the team make better decisions.
Architecture
- Product Development architecture strategy
- GCMS full platform replatform
- GCP cloud-native architecture
- AWS enterprise architecture (ERP)
Security
- API security CI tooling (Platform-wide)
- Cyber Defense cloud integration
- DevSecOps pipeline design
- Enterprise WAF/DDoS automation
Platforms
- CI/CD infrastructure and release tooling
- Developer ecosystem tooling
- AI enablement across SDLC
- Cross-domain tooling strategy