Why job posts should talk back

Every job post ends the same way: a wall of bullet points, a salary band if you're lucky, and a button that says Apply. That button is doing a lot of work. It's asking someone to commit an evening to your ATS before you've answered a single one of their questions.

The questions that never get asked

Talk to people who almost applied to a role and you hear the same things:

• "I couldn't tell if they'd take someone without a CS degree."
• "It said hybrid but not how many days."
• "I didn't know if the salary range was real or aspirational."
• "I wasn't sure my weird background would count."

None of these are hard questions. All of them are conversation-enders when there's no one to ask.

The best candidates aren't rejected. They self-select out, quietly, before you ever know they existed.

What a page that talks back looks like

When the job page carries an AI twin of the hiring manager, the dynamic flips. The candidate asks about the degree requirement at 11pm and gets a real answer in your voice. The page learns which questions keep coming up. And when someone great shows up, you find out while they're still on the page — not three weeks later in a spreadsheet.

Hiring is a conversation. The job post is just where it should start.