Andrew Fribush

Work with Andrew

Email Andrew →

12 / 13

Electronics design & manufacturing

Getting a device from working prototype to production units: sourcing, component specs, and production communication with manufacturers, at the managing/interfacing level of Chinese manufacturing across the startup device era (Bevi, Pavlok, WOO, ROCKI), and MMD's custom leave-behind sensors taken through contract manufacturing to a mass-production build. The bench-to-production patterns stay current through the 2024–2026 custom builds.

Credentials

  1. MMD's leave-behind sensors: a custom design taken through contract manufacturing to a mass-production build
  2. Manufacturing responsibility at the managing/interfacing level: sourcing, component specs, and production communication with Chinese manufacturers
  3. Pavlok's post-launch hardware revisions: hands-on across most of the module's components

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.

Work with Andrew | Andrew Fribush