We built Rezon because SES was broken for engineers.
Yuki Tanaka spent years building engineering teams in Tokyo — and watching the same situation repeat. A strong engineer would accept a contract, work for six months, and only later discover the client had been billed nearly double their weekly rate. The difference had passed through two or three broker layers, none of which were disclosed or relevant to the actual work. In 2023, Yuki left to build the platform that would make that arrangement impossible: one where the rate and the brief are on the listing page, not withheld until after you've already said yes.
"Engineers deserve to know what they're worth and what they're building."
Japan's SES sector handles hundreds of thousands of placements each year. The infrastructure works. What doesn't work is the information asymmetry built into it: clients know the full billing rate, brokers know the margin, and engineers are the only party expected to make a decision without seeing the numbers. Rezon is a single, simple correction to that dynamic. The rate is on the listing. The project brief is on the listing. You read both before you decide. We are not building a substitute for the SES market — we are building the version of it that treats engineers as professionals, not placements.
Three people, one problem to solve
Built and managed engineering teams in Tokyo for several years before founding Rezon in 2023. Saw the SES opacity problem from inside hiring organisations and decided to build the platform that fixes it structurally, not case by case.
Spent 8 years as a contract backend engineer across Tokyo and Osaka before joining Rezon. Builds and maintains the matching process — including the brief-quality standards that ensure engineers are never matched to a listing that understates the real scope.
Works directly with hiring teams to turn vague project descriptions into the specific, engineer-readable briefs Rezon requires. Reviews every client submission before it goes live. Better briefs produce better matches — and fewer wasted intro calls on both sides.
How we make decisions
Transparency is not a feature
The rate is disclosed not because it's a selling point — it's disclosed because withholding it from the person doing the work is wrong. We apply the same standard internally: we don't hold information when sharing it would produce a better decision.
Respect the professional's judgment
An engineer who declines a project is making a correct decision for themselves. Rezon is built on the premise that the platform's job is to give them the information to make that decision well — not to push them toward any particular outcome.
Fewer layers, better outcomes
Every intermediary in a contract chain adds latency, communication loss, and undisclosed cost. Rezon's model is to be the only layer between client and engineer — not the first of several. We do not sub-contract matching to third parties.