Real Capability vs. Manufactured Polish
When both sides optimize the hiring interface, the signal starts to collapse.
Publication Note
This article is part of the OSI-PIA public article series. It describes an active research and development direction. It does not claim that OSI-PIA is a finished hiring product, validated employment-screening system, legal compliance tool, or production decision system.
Article
In my article “Hiring Does Not Have a Talent Problem. It Has a Translation Problem”, I argued that hiring systems often fail because real capability is poorly translated into standard hiring formats. In “The False Negative Machine”, I argued that bad translations become dangerous when automated systems treat them as truth.
This article looks at the next failure mode: what happens when both sides of hiring optimize for AI-mediated systems, but the system becomes noisier instead of clearer.
Candidates are optimizing for the screen. Employers are optimizing for volume control. Vendors are optimizing for scalable workflows. The tools are supposed to make hiring faster, clearer, and more comprehensive. They are supposed to help employers understand candidates better and help candidates represent themselves more accurately.
But when all sides optimize for the interface, the result may be more volume, more polish, more filtering, more suspicion, and less confidence in what any given signal means.
That is the problem of manufactured polish. It is not only that weak candidates can look stronger. It is that the whole signal environment becomes less trustworthy.
From Translation Failure to Signal Collapse
Article 1 focused on translation failure: real capability may not arrive in the format a hiring system expects. Article 2 focused on false negatives: real capability can be rejected because the representation fails. Article 3 focuses on the mirror-image problem: weak or unverified capability can advance because the representation succeeds.
That does not mean every polished application is dishonest. It means polish is becoming less reliable as evidence.
A resume is not a person. A cover letter is not judgment. A fluent interview answer is not necessarily evidence of experience. A polished application is not proof that the candidate can do the work.
Generative AI did not create that problem. Hiring has always relied on proxies: job titles, credentials, resume bullets, professional language, interview fluency, confidence, and fit signals. But generative AI changes the cost of producing those proxies. It can make a resume sound stronger than the experience behind it, make a cover letter sound tailored without requiring real interest, help prepare structured interview answers without proving judgment, and produce professional language faster than hiring systems can verify what that language means.
The result is signal instability. The hiring system becomes less certain about what its own signals mean.
The Optimization Trap
The problem is not that only one side is using AI. Both sides are adapting.
Employers use AI and automated systems to manage volume, rank applicants, summarize resumes, screen for fit, draft job descriptions, write outreach, evaluate applications, and reduce the burden of review. Candidates use AI to tailor resumes, match keywords, generate cover letters, prepare interview answers, increase application volume, and translate their experience into language the system is more likely to recognize.
Each side is responding rationally to the other. But the combined effect may be irrational at the system level.
More applications do not necessarily mean more qualified candidates. More polished resumes do not necessarily mean more capability. More filters do not necessarily mean better judgment. More automation does not necessarily mean better understanding.
The hiring system becomes busier without becoming clearer.
The Signal Was Already Fragile
The problem is not that candidates suddenly have better tools. The problem is that too much of hiring still treats polished presentation as a proxy for ability. Mark Huang’s analysis of HBR’s warning about AI-polished resumes and remote interview performance makes this point directly: AI did not create the weakness.
A resume can still be useful. An interview can still be useful. A polished answer can still communicate preparation, clarity, and seriousness. But none of those signals should be treated as proof by themselves.
When a hiring system mostly rewards the cleanest resume, the smoothest answer, or the most familiar professional language, it does not necessarily measure capability. It may measure who has learned to perform the hiring ritual.
Generative AI makes that performance easier to produce. That does not make every AI-assisted candidate deceptive. It means the old signals are carrying more noise than they used to carry.
The screening question changes from “Does this look good?” to “What does this prove?”
The Resume Illusion
Robert Half describes a pattern many hiring teams are now encountering: a resume appears to contain the right experience, keywords, and proof of accomplishment, but the candidate struggles when asked to explain the work in a real conversation.1
This is the resume illusion: the document looks like evidence, but the conversation reveals the gap.
That does not mean every AI-assisted resume is dishonest. There is a major difference between using AI to clarify real experience and using AI to manufacture a professional identity the candidate cannot support.
But the distinction matters because hiring systems have long treated resume polish as a useful early signal. When a resume took effort to produce, polish could suggest attention, familiarity with the role, communication ability, and sometimes competence. Generative AI weakens that assumption.
A candidate can now produce a tailored, keyword-aligned, professional-looking resume quickly. The document may pass an automated screen. It may even impress a human reviewer. But if the candidate cannot explain the work, defend the numbers, describe the tradeoffs, or answer follow-up questions, the representation has outrun the evidence.
That is not capability. It is performance.
Polish Is Not Proof
The Interview Guys describe the candidate-side version of the same problem: AI-polished resumes may pass the machine but fail the conversation when the candidate cannot explain the details behind a project, metric, tool, or claim.2
A polished resume can open the door, but it cannot do the work. A polished answer can sound structured, but it does not prove judgment. A list of tools can look impressive, but it does not prove working fluency. A metric can sound persuasive, but it does not prove the candidate measured it, caused it, or understands what changed.
This is where manufactured polish becomes dangerous. It does not merely make weak applications look better. It makes representation less reliable as evidence. The more hiring depends on artifacts that can be cheaply optimized, the less those artifacts can carry trust by themselves.
AI Use Is Not the Same Thing as Deception
Fairness matters here. The problem is not that candidates use AI.
Many candidates use AI responsibly. They use it to clarify language, reduce awkward phrasing, translate experience across domains, prepare for interviews, identify gaps, or make a resume easier for systems and humans to read. For some people, AI may help recover signal that hiring systems would otherwise miss. A candidate with strong capability but weak resume-writing skill may use AI to become more legible. A nontraditional candidate may use AI to translate experience into language employers understand. A person who struggles with professional writing may use AI to communicate more clearly.
That is not the problem.
The problem begins when AI substitutes for evidence: when it invents experience, inflates claims, turns vague exposure into expertise, generates metrics the candidate cannot explain, or produces fluent answers that are not connected to the candidate’s actual judgment.
The ethical line is not “AI or no AI.” The ethical line is whether the representation remains accountable to reality.
AI can help a candidate tell the truth more clearly. It should not help them replace the truth with theater.
Before Anyone Applies
Manufactured polish is not only a candidate-side phenomenon. Generative AI is changing hiring before an application ever arrives.
Forbes, drawing on London Business School research by Isabel Fernandez-Mateo, argues that generative AI is already shaping how jobs are defined, how candidates are attracted, how outreach is personalized, how applicant pools are formed, and how selection systems operate.3
Organizations are using AI to produce job descriptions, identify candidates, write outreach, analyze interviews, and evaluate applications. If these tools learn from historical job descriptions or prior hiring patterns, they may reproduce the same assumptions that already shaped the organization’s definition of talent.
The signal problem starts before the resume. It starts when the organization decides what the role is, what language describes it, which candidates are invited to see it, and which evidence will count as relevant.
This means generative AI can shape both sides of the hiring signal. Candidates can produce more polished representations of themselves. Organizations can produce more standardized representations of work. Both sides may become smoother. Neither side is necessarily becoming more truthful.
When Both Sides Adapt
The hiring process is becoming an arms race around representation.
Candidates learn that the system rewards keywords, tailored language, quantified claims, and polished stories. Employers learn that candidates can generate those signals at scale. Employers respond with more filters, screens, interviews, verification, or suspicion. Candidates respond with more tools, more applications, more tailoring, and more automation.
Neither side has to be malicious for the system to degrade. The candidate is trying to be seen. The employer is trying not to drown. The vendor is trying to make the process manageable. But when everyone optimizes locally, the shared signal environment can get worse.
Generative AI can homogenize candidate signals, lower screening accuracy, and make it harder for employers to distinguish between higher- and lower-quality applicants. It can also increase application volume, which increases the workload on hiring teams and may contribute to more rejection, more candidate frustration, and more process hardening.4
That is why hiring can experience diminishing returns even while the tools become more powerful. The system produces more activity. It does not necessarily produce more understanding.
The Trust Spiral
Employers are responding to the resume illusion by adding friction. Robert Half recommends behavioral interviews, work simulations, reference checks, attention to soft skills, and careful review of whether candidates can substantiate what their resumes claim.1
That reaction is understandable. If resumes become less trustworthy, employers will look for other ways to verify claims. If remote interviews can be scripted or assisted, employers may want more in-person interviews. If application volume rises, employers may add assessments, screens, references, or additional rounds.
But the solution to weak signals can become more gates: more tests, more interviews, more suspicion, more burden on candidates, more process, and more delay.
Candidates did not create this system by themselves. Many job seekers use AI because the labor market has trained them to optimize for machines. They are told to tailor every resume, match keywords, quantify everything, speak the language of the job posting, and submit enough applications to overcome silence.
If the system rewards machine-readable polish, candidates will produce machine-readable polish. If employers use opaque filters, candidates will try to satisfy opaque filters. If rejection feels random, candidates will automate volume.
That does not excuse deception. But it explains the behavior.
The same tools that help an honest candidate clarify real evidence can also help another candidate manufacture evidence they cannot support. That is the unstable middle. The tool is not the whole issue. The relationship between representation and reality is the issue.
The Risk of Replacing One Weak Proxy With Another
When resumes become less trustworthy, organizations may be tempted to replace them with other proxies: assessments, video interviews, personality tests, gamified screens, AI interview analysis, portfolio reviews, reference checks, or work simulations.
Some of these can be useful. Some can be better than resume filtering. Some can also introduce new forms of bias, burden, opacity, or misinterpretation.
The problem is not the existence of proxies. Hiring always requires interpretation under uncertainty. The problem is forgetting that proxies are proxies.
A work sample is not the whole person. An interview is not the whole person. A reference is not the whole person. A resume is not the whole person. A score is not the whole person. Every signal has limits.
The responsible question is not “Which single signal should replace the resume?” The better question is “What combination of evidence gives us a fairer, more accurate, and more accountable understanding of capability?”
What PIA and OSI See
Professional Identity Architecture, or PIA, does not treat polish as proof. It treats polish as presentation.
Presentation can be useful. Clear writing matters. Good structure matters. A person should be able to explain their work in language others can understand. But PIA asks a deeper question: What evidence supports the claim?
If a resume says someone improved a process, what process? Under what conditions? What did they actually do? What changed? Who depended on the result? What did they learn? Could they explain the work without the document in front of them?
Manufactured polish collapses those questions into appearance. PIA tries to reopen them. The goal is not to punish candidates for using AI. The goal is to preserve the relationship between representation and reality.
Organizational Systems Intelligence, or OSI, looks at the system-level effect. When candidates can mass-produce polished applications and employers respond with more automated filtering, the hiring system may become more active without becoming more intelligent.
The organization receives more data, but not necessarily more evidence. It receives more applications, but not necessarily more understanding. It adds more screens, but not necessarily more judgment.
That is signal collapse. The system is producing movement, but not clarity.
OSI asks whether the organization is actually improving its ability to recognize capability, or merely increasing the amount of machinery between the person and the decision.
The Epistemology Problem
At this point in the series, the pattern should be visible. The problem is not only technical. It is epistemological.
Hiring systems are trying to know something difficult: whether a person has the capability, judgment, learning capacity, and contextual fit to do real work in a real organization. But the system rarely sees the person directly. It sees representations: a resume, profile, score, credential, keyword match, work history, interview performance, portfolio, reference, generated summary, or ranking.
Those artifacts may contain evidence. But they are not the same thing as knowledge.
Hiring systems are mistaking representations of capability for knowledge of capability.
OSI-PIA begins from that distinction. Evidence is not interpretation. Interpretation is not proof. A proxy is not the person. A score is not judgment. A polished representation is not capability.
That does not mean hiring systems should abandon structure, technology, or analysis. It means they need a more disciplined way to approach the problem. A better hiring system must be able to move from evidence to interpretation without collapsing uncertainty into false certainty.
PIA approaches that problem at the individual level. It asks how a person’s work, learning, judgment, and demonstrated capability can be represented without reducing the person to a resume pattern or keyword profile.
OSI approaches the same problem at the organizational level. It asks how organizations create, lose, misread, block, retain, or fail to deploy capability through the systems they build.
Together, they point toward a possible response to the failures described in this series: not faster guessing, not more polished theater, not more automated exclusion, but better evidence, clearer provenance, bounded interpretation, and human review.
Better Evidence, Not More Suspicion
The answer is not to ban AI from job searching, trust every polished artifact, or make hiring colder, more adversarial, and more performative. The answer is better evidence.
That means treating resumes as orientation, not proof; designing interviews around actual experience, tradeoffs, and judgment; using bounded work samples where appropriate; asking candidates to explain claims in context; checking whether the process rewards confidence more than competence; allowing AI to clarify evidence without allowing it to replace evidence; giving reviewers enough structure to compare candidates fairly without reducing people to scores; and recognizing that human judgment is still necessary, but human judgment also needs better evidence to work from.
The goal is not to eliminate uncertainty. The goal is to stop confusing polish with proof.
Conclusion
Generative AI did not make hiring signals fragile. It revealed that many of them already were.
A resume can still matter. An interview can still matter. A cover letter, portfolio, reference, work sample, credential, or assessment can still provide useful evidence. But none of them should be mistaken for capability by themselves.
Article 1 argued that hiring has a translation problem. Article 2 argued that bad translations become dangerous when automated systems treat them as truth.
This article argues that polished translations create the opposite danger: representation can look stronger than the evidence beneath it.
That is the problem of manufactured polish.
The technology is supposed to clarify representation. But when candidates, employers, and vendors all optimize for the hiring interface, the system can produce more volume, more polish, and more filtering without producing better understanding.
The future of hiring should not be a contest between candidates using AI and employers detecting AI. It should be a better evidence system: one that helps people explain real capability clearly, helps organizations verify claims fairly, and treats polish as communication, not proof.
The next article in this series, “Hidden Workers and Capability Leakage,” turns from the hiring interface to the larger organizational problem: what happens when real capability exists but remains unseen, blocked, or undeployed.
Sources
https://www.roberthalf.com/us/en/insights/hiring-help/ai-generated-resumes-hiring-challenges
https://blog.theinterviewguys.com/why-ai-resumes-are-backfiring-in-2026/
https://www.forbes.com/sites/lbsbusinessstrategyreview/2026/03/16/generative-ai-is-changing-hiring-its-most-overlooked-impact-may-come-before-anyone-applies/
https://link.springer.com/article/10.1007/s41469-025-00197-1
-
Robert Half, Rob Hosking, “The Resume Illusion: How AI-Generated Applications Are Challenging Traditional Hiring Practices.” ↩ ↩2
-
The Interview Guys, “The Resume Illusion: Why AI Resumes Are Backfiring in 2026.” Secondary candidate-facing commentary on AI-polished resumes and interview verification. ↩
-
London Business School / Forbes, Isabel Fernandez-Mateo, “Generative AI Is Changing Hiring. Its Most Overlooked Impact May Come Before Anyone Applies,” March 16, 2026. ↩
-
Isabel Fernandez-Mateo, “How generative AI is transforming hiring in organizations: key issues and research questions,” Journal of Organization Design, 2026. ↩