Sun Dahan

Chapter 12 of 13

The Engine

Proof, Not Opinion

Most of what's come before this chapter wasn't left as opinion. Where I could build something real and check what happened, I did; where I couldn't, I said so plainly instead of dressing up a guess as data. The resume isn't broken, exactly. It does a real job: a condensed, portable way to show professional experience, and it fuels the infrastructure the entire hiring industry runs on. What it was never built to do is carry the rest of a person, and holistically, that's not enough to run hiring on alone. It's a format that shows certain things well and leaves the rest invisible, and depending on how it's used, that can work fine or badly.

I didn't just leave that gap as an opinion. I built 7 Seconds and watched people see their own blind spot for the first time. I didn't just theorize that hiring teams were drowning. I built HireIntel and watched the silence up close. I didn't just guess that people open up in conversation. I built HireIntel's voice agent and listened to it happen, over and over. Reelu is a separate company, one I joined afterward as co-founder and CEO, built specifically to take that finding further than one feature inside one product could.

So when I say the last piece, the uncaptured layer from the previous chapter, needs an engine built to capture it, I'm not going to leave that as a theory either.

One honest note before the specification. The clearest usage signal from Chapter 8 pointed at the resume: the CV-optimizer was what people actually reached for, by a wide margin. That's real, and it's not what Reelu is. The two aren't in conflict, they're measuring different things. Usage data shows what people already know to ask for, the easiest, most familiar option, the one every ATS and every "how to write a resume" article already trained them to want. It doesn't show what would actually change the outcome for them. The fifty real conversations that came after the chat data are what taught me the second thing, and the engine below is built around that, not around what was already popular.

What the Engine Would Have to Do

What that engine would have to do is specific, regardless of who builds it or what it's called. It can't lean on a page. A page throws away exactly the layer this needs to capture. It has to work through real interaction, conversation, something closer to how people actually reveal themselves, not a form asking them to summarize their own life in bullet points. It has to capture the layer from Chapter 11, the values, the range, the way someone thinks under pressure, and hold onto it as something structured, not just a nice conversation that evaporates the moment it ends. And it has to get better the more it's used, because a single good conversation is a data point, and a system that learns across thousands of them is something else entirely. And it has to solve for warmth, not just extraction. AI is good, and cheap, at asking sharp questions and pushing past a rehearsed answer. It's not automatically good at making someone feel like a person listened, not a process, and that's not a detail, it's the difference between someone opening up and someone performing for a machine.

That's the specification. I'm building Reelu to be exactly that.

"What I actually believe is the thesis, not the company."

Where This Stands Today

I'd rather give real numbers than a promise. As of now, Reelu has over 3,000 users, 3 paying customers, and 12 confirmed placements, real people who found a real job through it. That's early, and I'm not going to dress it up as more than it is. But it's the same method as every other proof in this thesis: not a claim about what Reelu will do, a small, real, checkable record of what it's already done.

One Attempt, Not the Only One

It doesn't have to be the only company that ever does this, and it doesn't have to be the last one. What I actually believe is the thesis, not the company: the page is a bad container, the real signal is uncaptured, and someone has to build something that listens for it. Reelu is where I'm testing that belief with real product, real people, and real conversations, the same way 7 Seconds tested whether people could see their own blind spot, and the voice agent tested whether people would actually open up.

A thesis you won't build is just an opinion, and I didn't want this to be one. So I'm building the engine it points to. Whatever happens to any single company I build, that's the part that won't change: something has to exist that finally listens to people the way a resume never could, and I'd rather spend my time building toward that than just writing about it.

What would it actually take to fix how hiring evaluates people?

Something that works through real interaction instead of a static document, captures the uncaptured layer, values, judgment, range, in a structured way, and improves the more it's used instead of starting over with every candidate. That's a requirement, not a pitch for any one company that tries to meet it.

What is Reelu?

Sun Dahan's own attempt at the engine this chapter describes: a product built to capture the layer a resume can't, values, judgment, range, through real conversation, structured and owned by the candidate rather than the employer. As of writing, it has 3,000+ users, 3 paying customers, and 12 confirmed job placements. It's offered as one real attempt at the thesis, not the only possible answer to it.