How I Work
Engagements start with a working session, not a sales call.
My preference is to start with a session where we walk through frameworks and case studies from autonomous driving and ML development, then review your team's specific challenges together. From there, we determine what continued engagement looks like: hands-on development, advisory, or embedded ownership.
Engagement formats
Project-based
A defined deliverable with a fixed scope and timeline. Best when the goal is clear and the question is execution: hardening a pipeline, building a validation framework, getting a model into production.
Advisory
A focused engagement that goes deeper into speed through structure and shipping with confidence. Best when a team wants to level up engineering practices without committing to a longer engagement: iteration cadence, validation discipline, ML release process. Duration set case by case depending on what the team needs.
Fractional Founding Engineer
Embedded ownership of a technical area, the way a founding engineer would hold it. Engagements usually start at high intensity to hit the first milestones, then settle to a lower ongoing cadence once context is established. After that, continuity is the value. I know the tradeoffs already, so decisions get faster and cheaper.