Data pipeline orchestration
Reworked a chain of Lambda services across orchestration, application code, and infrastructure definitions.
Fractional CTO · Technical leadership
The business depends on software.
Someone must own the whole technical system.
I work with companies where software has become critical to customers, operations, or growth, but technical complexity has outgrown the current ownership structure.
I take responsibility across architecture, infrastructure, engineering delivery, and production AI while the work continues moving toward customers.
Recognizing the situation
This usually becomes necessary when…
- Important technical decisions keep returning to the founder.
- The team is busy, but delivery remains slow or unpredictable.
- Software has become critical to the business, but nobody owns the whole system.
- An AI initiative, acquisition, funding round, or product transition has raised the cost of getting technical decisions wrong.
20+ years in software engineering12 years of formal leadershipPhD in computer scienceCXO-level responsibilityTeams up to 30 people
What I take responsibility for
One technical system.
Clear ownership.
Architecture, delivery, infrastructure, and people affect one another. I take responsibility across those boundaries.
01
02
03
One technical direction
Architecture, infrastructure, engineering investment, and business priorities stop moving independently.
More predictable delivery
The path from idea to production has clearer ownership, fewer avoidable handoffs, and visible constraints.
Production accountability
Reliability, security, cost, evaluation, observability, and failure handling have named owners, including the risks introduced by production AI.
Examples from the work
Responsibility across
technical boundaries.
Long-running task execution
Led development and DevOps work for a task system, including architecture, standards, initial implementation, and ECS infrastructure.
Selected writing
How I think about
technical ownership.
5 min read
Leadership
What Type of CTO Does Your Startup Really Need?
A CTO is not just a CTO. Early-stage startups need builders, growing startups need architects, and larger companies need executives. Hiring for the wrong stage can cost you hundreds of thousands of dollars and push the company in the wrong direction.
3 min read
Architecture
Your AI System Needs a Deletion Path
Deleting an uploaded file is only one step. Design and verify deletion across extracted text, search indexes, saved answers, logs, caches, and backups.
7 min read
Architecture
AI Cost Starts with Architecture
Model selection, caching, context, batch processing, and bounded workflows shape AI costs. Measure the full cost of a successful resolution.
The person behind the work
I follow the problem
across technical boundaries.
Clients have often brought me in for a narrow implementation problem. My responsibility expanded when the work exposed problems in architecture, infrastructure, delivery, machine learning, or technical ownership.
More about my workSoftware has become too important to operate without clear technical ownership.
Tell me what changed, where the work is getting stuck, and what the company needs to accomplish next.
Discuss your technical situation