Work with Andrew
01 / 13
Fractional CTO / technical leadership
Owning the technical direction of a product company, especially healthtech or connected hardware. Software and computer engineer who has run a practice with teams from solo to 27 at peak, scaled infrastructure more than 10× through a demand spike, reported to CEOs, managed $29M+ in project budgets (annual engineering budget to $3.3M), most recently oversaw a client portfolio doing a combined $65M a year in revenue (annualized), and hires specialists while still shipping alongside them.
Credentials
- Ran an AI practice's engineering as Director: teams from solo to 27 at peak, annual engineering budget to $3.3M
- Oversaw a client portfolio doing a combined $65M a year in revenue (2026 annualized)
- 74 named client relationships on the public ledger; 37 spanned multiple calendar years
Why these lanes belong together
The same pattern keeps returning in my work: someone has a system nobody wants to take seriously, and it turns out to be load-bearing. Vacation-home water heaters; a mold inspector's leave-behind sensors; forty federal datasets; surgical training in hospitals with bad connectivity. Every home in a 320-property rental fleet got a digital twin. The mold sensor went through contract manufacturing. The datasets became APIs that AI agents query directly. The surgical platform's prize was $700,000. It runs in Ethiopia. That is the useful part.
Good fit
- Ambiguous zero-to-one systems where the technical direction and the implementation are the same job.
- Data-heavy AI products that must operate reliably in production, under real compliance constraints.
- Problems that cross boundaries: software to hardware, engineering to institutions, prototype to operations.
- Small teams that need a lead who ships alongside them.
Not a fit
- Pure research roles judged on publications. The AI-mechanism work is applied engineering, not an academic track.
- Roles that are exclusively people management with no hands-on technical scope.
- Teams seeking a narrow specialist in a single framework. The value here concentrates where problems cross domains.
- On-site-only roles outside Austin, TX.
A useful first email says what you're building, where it hurts, and what form of help you think you need. Specifics get the fastest reply. hello@andrewfribush.com. The full record is at the engagement ledger, the short version at the résumé. Machine-readable: /career/brief.json · /availability.json.