About
Systems Thinker, Resilient Leader
I turn ambitious ideas into products people want, and serve the teams capable of delivering them.
Systems Thinker, Resilient Leader
I turn ambitious ideas into products people want, and serve the teams capable of delivering them.
Career
Everyone Deserves Better
Everyone is carrying something—a challenge at home, a mental battle, or an internal struggle—and none of us leaves it at the door. Acknowledging the whole person creates the safety and support people need to be well, contribute fully, and do their best work.

Dealflow Platform
An applied-AI land-underwriting workflow designed around typed data contracts, provenance, cross-source validation, uncertainty handling, and human approval gates, shown with synthetic demo data.
01 / About

I turn ambitious ideas into products people want, and serve the teams capable of delivering them. I'm a systems thinker. Technology enthusiast, failed founder, and hands-on leader. I help make emerging technology practical, dependable, and valuable. My leadership is grounded in the example I set, the respect I show, the empathy I give, and the constant pursuit to challenge myself and my team.
Value maxing on Codex. Weaving a tree net. One-wheeling with my Rhodesian Ridgeback. Camping in my truck with my two kids and growing in love for my beautiful wife.
02 / Experience
With no formal authority, created a shared path from recurring delivery friction to deployable operating changes: surfaced pain points with engineering, QA, product, and Scrum leads; framed options through demos, documentation, and presentations; iterated to unanimous support; and personally implemented four approved mechanisms spanning release operations, governance, prioritization, and DevOps-quality automation.
Integrated delivery telemetry into a diagnostic release view and helped turn the findings into recurring reporting, ticket-quality review, formal bug prioritization, a live RACI, and a monthly release cadence that remained in team use through his January 2026 end date.
Converted an unstable mobile product and an open replace-versus-remediate decision into a time-boxed diagnosis and prioritized roadmap across code, architecture, defects, testing, deployment, and delivery process.
Completed the six-week assessment on time. Collaborator alignment and recommendation adoption are not established.
Created direction for a fragmented 74-market mobile portfolio by researching comparable transformations, framing the architecture implications of content and experimentation requirements, and producing a reviewed server-driven UI recommendation and high-level platform architecture. Made the unresolved decision-right gap explicit rather than overstating adoption.
When reassigned to a separate client need, reset the architecture direction for an iOS customer-support migration, worked in conjunction with client engineering and Capgemini product leads, implemented the solution, and drove it through shipment and acceptance; stakeholders qualitatively reported shorter support time.
Designed and built a complete visionOS 3D asset-rendering framework for a consumer marketplace.
The framework shipped and remains part of the live product.
Served as the functional iOS engineering lead for a financial-news iPad engagement through an agency.
All personally assigned work shipped.
Turned an unscoped GLP-1 initiative with a fixed timeline into an approved architecture and delivery plan: set the server-driven UI direction, made engineering and design choices concrete, secured the appropriate technical, design, and release approvals, and personally built and tested the reusable three-screen system.
Oversaw an on-time, incident-free release; co-architected five thread-safe data managers reused across the product; and led 50+ engineering learning sessions over approximately one year.
Carried an iOS product from concept to public launch, recruited a cross-functional founding team, and translated a low-friction invitation concept into shipped onboarding, custom chat, and App Clip flows.
The product reached the public App Store in May 2022; no adoption, funding, retention, or business-success metric is claimed.
Set major iOS architecture direction and partnered with product leadership, founders, and the CTO to turn complex insurance requirements into shipped onboarding, navigation, deep-linking, localization, transition, and application experiences.
Also helped build the early engineering organization through recruiting, interviewing, hiring, and an internship program; no unsupported counts or savings are claimed.
Technical Program Manager
Solution Architect
Solutions Architect
Software Engineer - visionOS
Functional iOS Engineering Lead
Lead Engineer
Co-Founder & CEO
Lead iOS Engineer
03 / Thoughts
I strive to serve the people I work with by demonstrating excellence, empathy, respect, and gratitude, allowing me to push myself and push others from this cultural foundation.
Everyone is carrying something—a challenge at home, a mental battle, or an internal struggle—and none of us leaves it at the door. Acknowledging the whole person creates the safety and support people need to be well, contribute fully, and do their best work.
Clear expectations are a form of care. Ambiguity, avoidance, and inconsistent leadership make work feel unsafe and unpredictable; honest direction gives people the stability and trust to do their best work.
Conflict is not something to avoid; practiced with respect, humility, and empathy for different perspectives, it surfaces stronger ideas and better outcomes. Healthy disagreement helps us align and move forward as a team rather than fragment into individuals.
I would rather work with someone who is teachable, asks thoughtful questions, and celebrates other people’s success with gratitude than someone who needs to be the hero. The strongest teams are built by people who stay curious, share credit, and keep learning.
Leadership is most effective when it stays close to the problems it is trying to solve. Consistent proximity—to the people, details, and real work—creates the context to make better decisions, remove barriers, and lead toward outcomes that matter.
Whatever I inherit—a product, process, relationship, team, or space—I look for ways to leave it stronger, clearer, and more useful than I found it. Small improvements compound, and stewardship means the next person should have a better starting point than I did.
Give me clear outcomes, constraints, and ownership, then remove the barriers and let me operate. I do my best work with ambiguity, end-to-end responsibility, and room to decide how to reach the goal—not under micromanagement.
The strongest products do a few things exceptionally well. Simplicity is not less ambition; it is focus made visible.
Band-aid fixes treat symptoms. I look for the incentive shaping the behavior, then change it so the right outcome becomes the easiest and most natural one. When incentives align, the problem can be solved at its source.
Look beyond the task requirements and step into the user’s context. Ask: “If I were using this, what would I expect to happen?”
Iterate on the feedback from your end user as fast as humanly possible and you will inevitably build something that people want and a valuable enterprise.
Data tells you what happened, not what to do next. Use it to inform judgment, not replace it; letting the past dictate the future will always leave you one step behind. Market leadership requires an innovative visionary who can use the evidence to imagine what should exist next.
Whether in code, documentation, or a team lead, having one place to go to know what to do is critical in building highly functional systems.
A good idea can still be wrong to pursue when it is delivered with the wrong intent, in the wrong way, or at the wrong time. Being right is not enough; the idea must be communicated with care, context, and timing that allow it to be heard and acted on.
04 / Outcomes
Outcome highlights rotate automatically. Hovering over or focusing the controls pauses rotation.
Evidence-bound highlights
Independent Consulting Engagement
Jul 2025–Jan 2026
≈3–6 mo → monthly≈3–6mo → monthly
Helped move an engineering team from releases roughly every three to six months to a monthly cadence in January 2026.
