10 Years. Technical Leadership. Real Results.

The Problem

Company needed new solution with a tight deadline. Led a small team to deliver. Had to sync internal team with external partners.

Key Decisions & Actions

• — Led technical delivery—coordinated 4-person internal team + external partners under tight deadline
• — Made architecture decision: Build a new system of reusable components that can be used by any future project—faster iteration, better fit for tight deadline and future-proofing
• — Managed cross-functional dependencies between product, design, and engineering to ship on time

The Problem

Junior team drowning in technical debt. CMS was blocking development. Azure deployments duplicated across environments, costing a fortune. Deployments took hours.

Key Decisions & Actions

• — Identified infrastructure duplication as primary cost driver—made the call to consolidate vs patch. Investment: 2 weeks. ROI: permanent 90% reduction
• — Rebuilt CMS to unblock development velocity—junior team was losing days to broken tooling
• — Coached team on architecture patterns to reduce future technical debt

The Problem

Years of valuable data locked in an old C++ Windows application. Only one department could access it. Other teams needed the data but couldn't get to it. Business wanted web access.

Key Decisions & Actions

• — Chose incremental migration over big-bang rewrite—kept old app running while building new. Zero downtime, phased rollout
• — Led frontend development and acted as Scrum Master—organized tasks, prioritized business value, kept us on schedule
• — Migrated legacy C++ workflows to modern web stack without breaking existing processes