Maxime Himeno
Software engineer, EPITA Paris. M.S.-equivalent degree, graduating Dec 2027.
I build backend and systems software, from how services divide up their state down to the cache line.
- Available
- Internships and full-time from Feb 2027
- Where
- Europe and APAC (Tokyo, Singapore)
- Languages
- French (native), Japanese and English (fluent)
One order through Naoto, against one network round trip
Both slowed down by the same amount. The order's 1.7 µs is the gateway's and the engine's P99 added, measured inside the services; the round trip is drawn at 30 µs, a typical value inside one datacenter.
That's why an order never waits on a reply from another service: a client's balance is fetched once, at login, and kept current from then on.
On two tracks of the same length, slowed down by the same amount, an order through Naoto finishes in 1.7 microseconds (1.1 at the gateway and 600 nanoseconds in the matching engine), while one network round trip to another machine, drawn at 30 microseconds, takes many times longer.
Work
Naoto Exchange
Personal R&D, Jul 2025-present
A trading exchange I built alone: it takes orders, matches buyers with sellers and keeps every balance up to date, pairing an order in under a microsecond.
- to match an order (P99)
- 600 ns
- to match an order (P99)
- to acknowledge it at the gateway (P99)
- 1.1 µs
- to acknowledge it at the gateway (P99)
Orders keep arriving. One that the other side already accepts trades at once, best price first; whatever is left waits in the book at its price. Prices and sizes are illustrative. STP: Vehicle Cost Platform
Team of six at EPITA, Sep-Oct 2026
A platform that tells a carmaker what a car costs and whether it's still profitable, the moment a price, an exchange rate or a design choice changes.
- to serve a 20,000-part car's cost
- 5.8 ms
- to serve a 20,000-part car's cost
- to recompute it after a price change
- 45 ms
- to recompute it after a price change
Parts are shared: the same fasteners go into the body, the chassis and the interior. A price change is pushed up every path it touches; everything else is reused. Parts and prices are illustrative. CNP: Cloud‑Native Platform
Team of six at EPITA, Feb-Dec 2026
A self-service platform where teams ask for the infrastructure they need, like a database, and get it without writing cloud configuration or waiting on another team.
Each claim has its own repo. A change is one commit there, and ArgoCD syncs that resource alone, so the rest of the project never moves. Project names and sizes are illustrative.
Where to start reading
All writingNaoto Exchange
Moving work off the hot path
Before any code, every step an order takes was designed from what the system needs and what the hardware does, to move as much work as possible off the hot path.
8 min readRead
STP
What carmakers already have, and where STP fits
Before designing anything, we looked at how ERPs cost a car and what engineers use instead. Six pain points came out of it, and so did the rule that STP must plug into the systems already there, at a carmaker's scale.
3 min readRead
CNP
Modeling a project's infrastructure as a graph
A flat list of resources can't tell a load-bearing database from one nobody uses anymore. A dependency graph can, by walking it from the project's entry points.
2 min readRead
Get in touch
Open to internships and full-time roles from Feb 2027, in Europe or APAC (Tokyo, Singapore).
maxime.himeno@gmail.com