I used WorkBuddy to turn 'role understanding' into a card that can be picked apart
Where AI recruiting gets stuck is job understanding — the model is actually less critical. And job understanding has to be written down, picked apart by others, and revised before it slowly takes shape. What I've been doing with WorkBuddy these two months is basically this.
The Guangzhou "AI + Human Resources Services" competition — the preliminary round is judged by proposal review plus a live run test, and participating organizations have to prepare their own compute and deployment environment, giving judges an entry point they can actually run. After reading it I wanted to laugh, but couldn't. Because most teams' submissions run smoothly in a demo, but go mute the moment you drop them into a real job. They say AI recruiting penetration hit 47% in 2025 and may pass 65% in 2026, but high penetration doesn't mean accurate screening. That Nowcoder whitepaper surveyed 750 companies — over half use AI for initial screening, and what does screening accuracy depend on? It depends on the job definition you give it.
My environment is web version plus macOS — this setup below may not apply to everyone.
Feed in the JD, let it question me first
Open WorkBuddy, click New Folder in the left sidebar, name it by job, e.g. "2026-11-Structural Engineer." Then drag four things in: the original JD, the voice-to-text of what the hiring manager told me on WeChat, the previous holder's handover doc, and three historical resumes (one passed, two didn't). After uploading, wait for it to parse — a file list appears on the right side of the interface, confirm each one is checked.
Then in the bottom instruction box, type a line: don't summarize this JD, first list what you're still unsure about after reading it, give it to me as questions, no more than eight at a time.
What it spat out was pretty sharp. Does "familiar with structural design" mean able to produce drawings independently or able to review drawings? Is "three years experience" a hard threshold or a preference? Does the supplier liaison mentioned in the handover doc actually count as this job's work? I actually had answers to these in my head, but the answers stayed in my head, never on paper. The value of this step is forcing them out.
Fix it into a card, leave only one column for humans to edit
After I answer one by one, have it generate a job understanding card, with fields fixed to these: hard thresholds, trainable items, veto items, three must-ask interview questions, and which words in a resume mean you can drop it immediately. The key parameter is to have it tag the source after each item — original JD, hiring manager's verbal input, or my call — distinguished by different markers. The first version had no source tags, and later when arguments broke out there was no reconciling the accounts.
Once the card is built, click Export in the top right, choose table format, drop it into the shared sheet. I stepped in a pitfall on permissions. At first I gave everyone edit access, and the hiring manager added a "must know software X" to the veto items, then the business lead turned around and deleted it — back and forth three times. Later I changed it so only this one column is open for the hiring manager to edit, other columns read-only, and I keep the final version. Number of arguments dropped noticeably.
Every Friday afternoon I spend twenty minutes pulling out the resumes I screened out this week that felt off at a glance but I couldn't say why, throw them back in, and ask which item on the card this resume fails. If it can't say, the card has a problem. Last week I found "strong communication skills" was completely unexecutable, pure filler — deleted it.
Another pitfall: don't set up scheduled tasks. I tried having it auto-summarize new resumes daily — the moment the format changed everything went haywire and still needed manual backup, worse than running manually. Now I just manually click once when I get to my desk in the morning, ten-odd minutes.
Physix Frontier