About
Building the systems that let teams move faster.
I spent years leading technical operations — owning the seams between engineering, support, analytics, and infrastructure where most work quietly succeeds or fails. The lesson that stuck: the systems around the work matter more than any single feature. The export nobody owns, the field two teams define differently, the manual step done every Friday — close those and a team gets faster everywhere at once.
That same instinct is what pulled me into building products. I am most useful at the point where a real, repeated problem meets a system that can remove it for good. So I started a studio: a handful of products, each born from a problem I kept running into, built through the same disciplined loop. The job is no longer running someone else's operation — it is designing the operation, and the products, from the ground up.
Career
Where I've done the work
Cross-functional technical operations — engineering, business systems, analytics, and cloud.
Project Lead — Technical Operations
International Education Evaluations
Recent
Orange County, CA
- Led cross-functional initiatives spanning software engineering, operations, customer support, and analytics.
- Drove system modernization — replacing manual, error-prone workflows with automated, auditable ones.
- Administered the business-systems stack (Zendesk, HubSpot, Talkdesk) and improved data quality across them.
- Built Power BI reporting and executive dashboards that turned scattered data into decisions.
- Owned AWS infrastructure and operational reliability for core internal tooling.
- Delivered technical projects end-to-end — scoping, sequencing, and shipping with cross-team buy-in.
Skills
What I bring
The disciplines behind the operations work and the products.
Operations & Delivery
- Technical Operations
- Technical Program Management
- Process Optimization
- Cross-Functional Leadership
- Revenue Operations
AI & Automation
- Workflow Automation
- AI Integration
- Systems Integration
Business Systems
- Zendesk Administration
- HubSpot Administration
- Talkdesk Administration
Data & Cloud
- Power BI
- Analytics & Reporting
- AWS Infrastructure
- Data Quality
Philosophy
How I think about the work
Systems over heroics
A team that depends on its best person being awake is one bad week from failure. I build the system so the right thing happens by default — not because someone remembered to.
Measure before you build
If you cannot say how often something happens and what it costs, you cannot say whether fixing it is worth it. I find the real bottleneck before spending effort on it.
Consistency compounds
Showing up beats intensity. The same disciplined loop run every time turns shipping one thing into being able to ship many — reliably, without drama.
What I'm building
A studio of products
Each one solving a real problem I kept running into — built through the same loop.
Future goals
Where this is going
The goal is a studio that can ship many products reliably — not one good launch, but a repeatable way of turning real problems into things people use. I want the operating system around the building to get strong enough that the products almost take care of themselves, so the work stays where it matters: finding the next problem worth solving.