01Company · Team
Four disciplines, one uncomfortable amount of field experience
Most of what the product knows about failure came from people who have stood at a charger in July trying to work out why a contactor will not close. That is not incidental — it is why the software is shaped the way it is.
How the team is organised
Who does what
Platform engineering
The OCPP gateway, the event pipeline, the billing engine and the multi-tenant data layer. The people who care that a consumer is idempotent because a driver being billed twice is not an abstraction.
Field operations
Commissioning, triage and the unglamorous knowledge of which contactor sticks in humidity. Most of what the product knows about failure came from this team.
Commercial & finance
Tariff design, settlement mechanics, GST treatment and payment operations — the parts of charging that decide whether a network is a business.
Customer success
Onboarding operators, migrating their history, and answering the question behind the question when a support ticket arrives.
How we work
Small team, long horizon, unglamorous priorities
We are deliberately small, which forces a particular discipline: nobody gets to own a feature nobody uses. Engineers talk to operators directly, field operations file requirements as specific reproductions rather than complaints, and the people who write the billing engine are the people who get asked why a session refunded.
The decisions we take slowly are the ones that are expensive to change — the data model, the tenancy boundary, the event architecture. Everything on top of those we move quickly on, because we can afford to be wrong there.
Most of our best product decisions started as a support ticket somebody refused to close with a workaround.
Careers
We are hiring for a few of these
Talk to the people who built it
Walkthroughs are run by the team, not by a sales engineer reading from a script.