The Team

Six people. One product. We are small on purpose, and every person below owns a hard problem from the whiteboard to the customer who unboxes the puck.

Priya

Real-time firmware lead · ex-QuantumScape

Priya owns the deterministic path on the Cortex-M7: the 1 kHz control tick, the FreeRTOS task priorities, and the brutal little routines that decide what happens when the world goes wrong — the watchdog, the brown-out detector, the safe-state fallback. She came from battery-management firmware at QuantumScape, where "the timing is a suggestion" was never an acceptable answer, and she brought that intolerance with her. She measures jitter in microseconds and has strong opinions about interrupt latency that she will share whether or not you asked. If the puck ever misses a deadline, she treats it as a bug, not a tuning parameter.

CURRENTLY filing the FCC Part 15B report

Marcus

RF / antenna engineer · ex-Skyworks

Marcus owns the part of the WB-1 that most people pretend is magic: three radios — BLE, Wi-Fi, and LoRa — sharing a footprint the size of a hockey puck without stepping on each other. He designs the front end, lays out the antennas, and negotiates the coexistence schedule that keeps a chirping LoRa transmitter from deafening a Bluetooth receiver eight millimeters away. He spent years at Skyworks on power amplifiers and RF front-end modules, which means he thinks in S-parameters and speaks fluently to a vector network analyzer. He is the reason the puck holds a link across a noisy gym floor, and the reason there is exactly one plastic window in the aluminum enclosure.

CURRENTLY debugging LoRa module 4 antenna isolation

Dana

Web / UX engineer · ex-HTTPie

Dana owns the web control plane — everything you see when you point a browser at the puck. That is the REST endpoints, the WebSocket stream that pushes live telemetry, and the dashboard that has to render a room full of orchestrated devices without ever feeling laggy. She came from HTTPie, where making network requests legible to humans was the entire job, and she carries that same conviction into the WB-1: a control surface should tell the truth about what the hardware is doing, instantly and without lying to make itself look faster. She profiles first paint the way Priya profiles interrupt latency, and she will not ship a view that stalls.

CURRENTLY cutting the dashboard's first-paint under 200 ms

Sam

EE / firmware generalist · ex-Plex

Sam is the person who makes a bare board come alive. He owns bring-up — the ritual of powering a fresh PCB for the first time and finding out which corners of the schematic were optimistic — plus the power tree, the 18650 discharge-curve characterization, and the test fixtures that stamp every unit before it ships. He came from Plex with the profile of a true generalist: he can debug a boot loop in the morning and reflow a stubborn QFN by hand in the afternoon. He believes the discharge curve is a moral document, because it decides how honest the battery indicator is allowed to be, and he refuses to round it in the product's favor.

CURRENTLY revising the power tree for rev C

Leah

Industrial + brand designer · ex-Teenage Engineering

Leah is responsible for how the WB-1 looks, feels in the hand, and communicates its state — and for how this website looks while you read about it. She owns the machined aluminum enclosure down to the draft angles, the status-LED language that lets a single light say a dozen precise things, and the design system, palette, and type that hold the whole product together. She came from Teenage Engineering, where restraint is a discipline and every chamfer earns its place, and she treats that ethos as non-negotiable here. She argues that a product's honesty is visible in its details, and she will move a bezel by half a millimeter to prove it.

CURRENTLY tuning the die-cast draft angles

Tom

Operations · ex-Tesla energy operations

Tom owns everything between "the board passes test" and "a customer is using it happily" — supply chain, incoming inspection, serialization, fulfillment, and the personal relationship with each of the first fifty customers. He ran energy operations at Tesla, where a shipment that slips is a substation that stays dark, so he thinks in lead times, buffer stock, and traceability by serial number. He knows which of our components has a fourteen-week lead time and has already placed the order. For a company this small, he is the difference between a promising prototype and a product people can actually buy, and he treats every one of those first fifty relationships as the reference the next thousand will be built on.

CURRENTLY onboarding customer 31

How we work

There is no layer of management between the person who signs off on a decision and the person who has to live with it — they are usually the same person. We carry each subsystem through the schematic, the code, the test fixture, and the field result. If something on the WB-1 is broken, exactly one of the faces above is responsible for it, and they know it.

How we hire

We hire slowly and we hire deep. A generalist who can carry a subsystem from first principles to a passing test fixture is worth more to us than three specialists who each need a spec handed to them. The result is a team where the firmware lead can read a schematic, the RF engineer can push a web commit, and the operations lead can run the serialization script without asking anyone.

Want to build the WB-1 with us?

We are six, and we grow only when a problem clearly needs a seventh person who owns it completely. If that sounds like you, our careers page has the current openings — but read this first: the fastest way in is to send us something you made, not a résumé. A schematic, a repo, a machined part, a teardown, a bug you chased down to the silicon. Show us a hard problem you took end to end, and we will know exactly what to do next.