Model Card for jonathanberi/jonathan-beri
A product and platform leader pre-trained on two decades of connecting hardware to the internet, and fine-tuned for getting developers from unboxing to "it works" as fast as possible. Currently spending weekends on robots.
TL;DR: I think robotics is close to its Arduino / Raspberry Pi moment: cheap, open, hackable robots that get developers from unboxing to "it moves" in minutes. I've spent my career on that kind of transition for connected hardware. Lately I've been building for Reachy Mini, starting with Mini Fleet, a dashboard for a room full of robots.
Model Details
- Developed by: USC (B.S. Computer Science & Business Administration), then a long run of hardware platforms
- Model type: Founder-PM hybrid. Product strategy, developer programs, open source, partnerships, P&L.
- Current deployment: Head of Product, IoT at Canonical
- Contact: jmberi@gmail.com · LinkedIn · GitHub
Training Data
| Dataset | Years | What it taught |
|---|---|---|
| Golioth (Founder & CEO) | 2020–2026 | Building a device-to-cloud developer platform from zero. Raised $8M+, grew a distributed team to 23 across five countries, ran the P&L, built DevRel from scratch, structured semiconductor partnerships, and led the company through acquisition by Canonical. |
| Particle (Senior PM) | 2017–2019 | Owned the embedded device platform. Shipped Particle Mesh, Particle Workbench, Device OS 1.0, and the mobile apps. |
| Google / Nest (PM) | 2011–2017 | Led product for Thread and OpenThread, Nest's first open-source initiative. Alphabet's alternate board member at Thread Group. Earlier: Google Play SDK / Firebase SDK. |
| WeWork, Magento, MySpace | Earlier | Core platform work, developer platforms, and early OpenID Connect / OAuth 2. |
| Zephyr Project | Nearly the beginning–present | Involved since nearly the beginning, in various roles at various companies. |
Supplemented with a contributed chapter to Make: JavaScript Robotics and an active workbench.
Intended Uses
Direct use: Product and platform leadership for developer hardware: dev kits, robots, and the ecosystems around them.
Specifically good at:
- Turning a beloved dev kit into a platform: SDKs, onboarding, app ecosystems, docs, community
- Scaling from thousands to millions of units: manufacturing partners, silicon vendors, distribution, education channels
- Open source as strategy, not just licensing
- Connectivity, OTA, fleet, and telemetry, the unglamorous parts that decide whether a robot survives contact with a classroom of 30
Out-of-scope use: Being the person who says "we'll fix the developer experience after launch."
Evaluation
| Metric | Result |
|---|---|
| Companies founded / exited | 1 / 1 |
| Venture capital raised | $8M+ |
| Distributed team built | 23 people, 5 countries |
| Open-source platforms launched at a big company | OpenThread (Nest's first) |
| Reachy Mini apps shipped (in simulation; no robot yet) | 1 (Mini Fleet) |
Bias, Risks, and Limitations
- Strong prior that the first five minutes of the developer experience matter more than the next five features
- Will ask why the update path isn't one command
- Prone to building tools on weekends (see: Mini Fleet)
How to Get Started with the Model
from humans import Jonathan
jonathan = Jonathan.from_pretrained("jonathanberi/jonathan-beri")
jonathan.ask("What would it take to get a robot from unboxing to moving in under a minute?")
Or, less formally: jmberi@gmail.com. Coffee or a call any time.
Citation
@misc{beri2026,
title = {Connecting sand to the internet, then giving it a face},
author = {Beri, Jonathan},
year = {2026},
url = {https://huggingface.co/jonathanberi/jonathan-beri}
}