If you have worked in Japan's IT staffing market for any length of time, you already know the routine. An SES agency contacts you about an opening. They describe the project in broad strokes — enterprise Java, somewhere in central Tokyo, three to six months. You ask about the rate. They give you a number. What they do not tell you is what the client is actually paying, or how many layers of margin sit between that client budget and the figure landing in your account.
This opacity is not accidental. It is structural. And it has consequences that shape the careers of tens of thousands of engineers working in Japan today.
The anatomy of a traditional SES chain
Japan's System Engineering Service model was designed around a specific era — a time when client companies lacked the HR infrastructure to find and qualify engineers themselves, and when the information asymmetry between talent and employer was simply assumed to be the cost of doing business. An SES agency sits in between, takes a margin, and dispatches engineers under a gyomu itaku or haken contract.
The problem is that this structure rarely stops at one intermediary. It is common for a client's budget to pass through two or even three agencies before reaching the engineer — each taking a cut, each adding a communications layer, and none of them required to disclose the original figure. A project budgeted at ¥250,000 per week by the client might reach an engineer as ¥170,000 or less, with no explanation of the difference.
Consider a plausible scenario from the mid-2024 Tokyo market: a backend engineer with five years of Java and Oracle experience accepts a dispatch role at a financial services firm in Otemachi. His agency quotes him ¥185,000 per week. Eighteen months into the engagement, he learns through casual conversation with a direct-hire colleague at the same firm that the client is billing his services at approximately ¥240,000 per week. The gap — roughly ¥55,000 weekly — has been invisible to him for the entire duration of the engagement. That is not a rounding error. That is meaningful income that went somewhere he had no visibility into.
What transparency actually means in practice
When we talk about rate transparency at Rezon, we are not saying brokers should not earn a fee. Matching services, contract administration, and the risk management that agencies provide have genuine value. We are saying that the engineer should see the full picture — the gross figure the client is paying — before they accept any engagement.
This distinction matters. Transparency does not require zero intermediation. It requires that the intermediation be visible. If an engineer knows the client is paying ¥220,000 per week and the platform fee is disclosed at ¥20,000, the engineer receives ¥200,000 with complete understanding of the arrangement. They can evaluate whether that arrangement is fair. They can compare it against market alternatives. They can negotiate from a position of actual information rather than inference.
The opaque model denies engineers all of this. They are asked to make career decisions — accepting or declining projects, setting their own rate expectations, evaluating whether a renewal is worth taking — without the information those decisions require.
Why brokers have resisted change
It would be unfair to characterise the traditional SES industry as simply exploitative. The opacity has been self-reinforcing rather than purely deliberate. Agency relationships with client companies are often long-term and sensitive. Disclosing billing rates risks disrupting those commercial relationships. Engineers who know the gross figure might push for renegotiation or defect to direct-hire arrangements. The incentive to maintain the information asymmetry is real.
There is also a structural habit at play. Many of Japan's established SES agencies grew during a period when neither engineers nor clients had the tools to connect directly. The brokerage layer was genuinely necessary. The question now is whether it still serves its original function, or whether it has become a friction cost sustained by inertia and information control.
We are not saying all traditional SES agencies are acting in bad faith. We are saying the structure they operate in makes opacity the path of least resistance, and that engineers bear the cost of that path.
What engineers can do now
Even before working with a platform that discloses rates openly, engineers can improve their information position. The first move is to simply ask — directly, in writing — what the billing rate to the client is. A reputable agency should be able to answer. If they cannot, or will not, that tells you something.
Second, calibrate your rate expectations against market benchmarks rather than agency-provided numbers. For mid-level engineers with four to seven years of experience in mainstream stacks — TypeScript, React, AWS, Java Spring — the Tokyo contract market in 2024–2025 has generally supported weekly rates in the ¥160,000–¥230,000 range depending on seniority, specialism, and remote flexibility. For infrastructure and cloud-heavy roles, or engineers with SAP or mainframe backgrounds, the ceiling is meaningfully higher. These are realistic ranges based on what we observe in the current market, not guarantees.
Third, pay attention to how a project is described to you. Does the brief tell you what you will actually build? Does it describe the client organisation with enough detail to assess whether the work is meaningful? Or is it vague in ways that make it hard to compare against alternatives? The quality of information in the initial brief is itself a signal about how the engagement will feel from the inside.
The information gap is the market distortion
Labour markets work best when both sides of a transaction have access to the information they need to make good decisions. In most professional employment markets, salary ranges are increasingly disclosed, benchmarked, and discussed openly. Japan's SES sector has lagged well behind this broader movement, partly due to cultural conventions around discussing compensation, partly due to structural inertia in the agency layer.
The consequence is not just that individual engineers are underpaid relative to their market value. It is that the market itself misallocates talent. Engineers who do not know their real value accept projects below their floor. Clients who do not compete on disclosed rates never have to sharpen their offers. The whole market operates less efficiently than it should, and engineers disproportionately bear the friction cost.
Fixing that starts with a simple commitment: every engineer who works through Rezon sees the gross rate on every project before they make any decision. Not a range that obscures the real number. Not a net figure stripped of context. The actual amount. Paired with a disclosed, fixed service fee on the client side. That is what we mean when we say the SES model needs to change — and it is where we have chosen to start.
