← Journal
Issue 37 · March 2026 · 3 min read

The Other Side Doesn't Know Either

An outcome is not the same thing as the right outcome.

The last two articles I wrote were for candidates. The people walking into rooms without enough information. What I did not say is that the person on the other side of the table is working with the same amount. Maybe less. The hiring team that interviewed you last month did not know what your profile was worth on the open market. They did not know how many people with your background actually exist. They did not know whether the compensation they offered was competitive or whether the job description they posted reflected the role they actually need filled. They were not withholding information. They did not have it.

Here is how most compensation decisions get made in these sectors. Someone asks what the last person was paid. Someone else asks a recruiter. A third person looks at a job posting from a different market and adjusts by feel. And from those three inputs, a number is created. Not benchmarked. Created. There is no comp study to reference. No percentile data broken down by sector, geography, and experience level. No way to know if the number is P25 or P75 or completely off the map. So the offer goes out and everyone holds their breath. If the candidate accepts, the number must have been fine. If they negotiate, maybe it was low. If they walk, it was definitely low. But nobody knows by how much because there was never a reference point to begin with.

Nobody writes a job description from data. They write it from memory. What the last person did. What went wrong. What they wish they had asked for the first time. And then they add a few things that sound important and post it. The problem is not that the descriptions are poorly written. Some of them are detailed and thoughtful. The problem is they are built on assumptions that have never been tested. Is five years of experience actually the threshold, or did the best person you ever hired have three? Is a degree in hospitality management a real requirement, or is it a proxy for something else entirely? Does the candidate need to have managed a team of eight, or do they need to have built a team from zero, which is a completely different skill? These are not edge cases. These are the core questions that determine who applies, who gets screened out, and who ends up in the chair. And in most searches, nobody asks them until something goes wrong.

This is where it compounds. The employer undervalues the role because they have no benchmark. They set compensation below market without knowing it. They write a description that filters out the people they actually need and attracts the ones who match on paper but not in practice. The candidate pool looks thin, so they lower their standards or rush the process. The person they hire is not a bad hire. But they are not the hire they would have made with better information. And the candidate on the other side accepts a number that undervalues their profile, joins a role that was not clearly defined, and spends the first year figuring out what the job actually is. Nobody got what they needed. Both sides thought the process worked because it produced an outcome. But an outcome is not the same thing as the right outcome.

A bad hire in these sectors does not show up on a spreadsheet. It shows up in the room. The household that has to explain to the principal why the new person did not work out. The family office that operated without a key role for four months while they searched again. The security detail that lost cohesion because someone was brought in who checked every box on paper and missed the ones that actually mattered. And every one of those situations started the same way. A search built on assumptions. A compensation package built on a guess. A job description that did not reflect the real need. The cost of the bad hire is obvious. The cost of the process that produced it is the part nobody calculates.

This is not a candidate problem. It is not an employer problem. It is a market problem. The information that would make every hire in these sectors more precise, more fair, and more durable has never been organized into something both sides could use. That is what rouka is. Not a recruiting platform. Not a job board. Intelligence infrastructure for the hires that matter most. Over 1,000 roles across 10 sectors in 95 markets. For candidates, it answers the question: how rare am I? For hiring teams, it answers the question: what does this search actually require? Both answers are at rouka.co.

← Back to Journal