How did it start?
I found Indeed through the UX Designer role. It asks for someone who can make complex flows legible on both sides of the marketplace.
So I went looking for one moment where the employer and the job seeker are looking at the same decision from opposite sides.
The problem
When a recruiter tightens a Required qualification on a live job, they can’t see who it removes —
or that their own job post still promises the opposite.
The job description candidates read and the qualifications that filter them are separate fields in the same Edit Job form. Editing one does nothing to the other.
Indeed is explicit about what a Required rule does: “Applicants who don’t meet a required screener question are automatically moved to your Rejected list.”
Who this is for
Two people on opposite sides of the same sentence, and only one can see the rule.
The hypothesis
If Indeed checks Required qualifications against the live post while a recruiter edits them, more harmful mismatches get resolved before applicants are affected —
without relaxing legitimate must-haves just to clear a warning.
The second half is the guardrail. A screen that goes green because every Required became Preferred has made screening worse.
And the edit moment, not a review dashboard, because a review pile finds the problem after the rule has acted.
What Match Check does
A fictional role, live for 21 days, 128 answers to its Experience question. The recruiter raises the minimum from two years to five.
Match Check answers in place: 41 people you already reviewed will move to Rejected, and here is your own sentence that says otherwise.
It says which kind of difference it found
Flag every difference and it becomes a banner people learn to ignore. So it names three cases, in words rather than colour.
Resolving it never produces a green light
The primary action is small: Make this Preferred instead keeps the signal and keeps the person. The recruiter can also limit the bar to new applicants, or keep it Required and say why.
Keeping it never clears the flag.
And when it has nothing to say, it says only that
Fixed rules over structured qualifications and pre-tagged sentences — not AI, not a fairness audit, and the interface says so.
Its empty state is scoped to what it actually checked.
Prototype in React
Raise the Experience requirement and watch the count change; switch it to Preferred and watch the warning resolve honestly.
The first pass looked branded, not native
My first build put verified Indeed tokens on an invented page structure. I threw it away, rebuilt from public references to the real Edit Job screens, and checked it element by element against live computed styles.
Inside the prototype, Indeed Sans and the product wordmark aren’t licensed to reproduce, so it ships Noto Sans and a typeset wordmark: token-matched, not pixel-identical.
What I would test first
Adversarially reviewed, not yet tested with recruiters. Five recruiters, one task, watching for comprehension rather than preference:
“This job has been live for 21 days. The hiring manager asks you to raise the experience requirement from two to five years. Make that change as you normally would, and save it.”
- Do they notice the mismatch unprompted?
- Do they understand what happens to existing applicants versus new ones?
- Do they keep a real must-have Required rather than relaxing it to clear the warning?
If it shipped: fewer applicants excluded by requirements the post contradicts, fewer restores from Rejected, fewer criteria edits after the first batch arrives.
Evidence and limits
- Public documentation shows no surface that reconciles a post with its rules at the edit moment. That is an observation about documentation, not a claim that Indeed lacks one. The falsifier: if the authenticated Edit Job flow already does this, the concept is redundant.
- Indeed documents what Required and Preferred do to an applicant, not whether editing a qualification leaves the description untouched. I treat them as the separate fields they appear to be.
- The recruiter is a working persona. How often this mismatch happens is unknown.
- A reconciliation aid, not a fairness or job-relatedness audit. All data fictional.
SourcesThe role · Indeed on screener questions · Indeed on screening criteria. Verified 30 August to 2 September 2026.
