Answers
Screening
Resumes, detectors and keyword screens, and what a document is still evidence of when every one of them is polished.
91 articles
Everything on screening
- An AI Certificate Gets You Read Only If It Names Work You Did An AI certificate proves a course was finished, nothing more. What earns a second look is the project it produced and what you caught going wrong in it.
- Why Formal Writers and ESL Applicants Get Flagged as AI Detector research names your situation: non-native English writing gets misread as AI most often. Here's what the studies measured, and what to do about a flag.
- Humanizers Beat the Detector and Lose the Reader AI humanizer tools do move a detector's score. They also strip out the numbers and specifics a human reviewer was actually looking for. Skip them.
- Every Number on Your Resume Is a Question You Will Be Asked AI builders now invent the metric inside the bullet. Keep a number only if you can trace it, and use scope where you can't.
- The Hours-Saved Number Is the One They Test First A self-estimated AI productivity figure is the least checkable line on a résumé, and the one a specific follow-up question is likeliest to test first.
- Applicants Per Hire Stopped Being a Measure of Demand Applicants per hire moves with your application form and channel mix rather than with interest in the job. Read it as your own trend, and only if the form held still.
- Which Requirements Are Real, and When to Apply Anyway The 100%-qualified rule has no traceable source. Apply when you can evidence the role's core work; only a licence, a legal must, or the job's core makes a gap real.
- An AI Resume Builder Sells Formatting, Not Judgment Worth paying for layout, storage and a grammar pass on your own words, not for a compatibility score or a rewrite. Rankings of the builders are mostly advertising.
- Employers Can't Detect AI in Your Resume. They Can Detect Generic. No employer has a reliable way to prove your resume was AI-drafted. What actually gets an application skipped is reading like everyone else's, and that part you control.
- Seniority Shows Up in Decisions Under Ambiguity, Not in Titles Title inflation makes the usual proxies useless. Ask for three decisions, including one that went wrong, and write what a passing answer contains before the screen.
- Bias-Free, Bias-Tested and Audited Are Three Different Claims Vendor fairness claims come in three sizes: inputs, measured outcomes, and who did the measuring. Sort them, then ask for the artifact behind each one.
- Name-Blind Screening Under-Delivers, and the Field Trials Say Why Redaction removes one signal and leaves the correlated ones. The French randomized trial widened the interview gap, and a gap that opens after the screen is untouched.
- What a Cover Letter Is Still Read For When AI Writes Them All A cover letter earns its place only with a specific reason a resume can't hold. Here's what to write, what to cut, and when to skip it entirely.
- Templates Change Parsing and Scan Order, Not Your Odds A template affects what a parser extracts and what a reader sees first. It cannot improve content it did not write. Here is the difference, sourced.
- Dropping a Degree Requirement Does Nothing Until Something Replaces It Removing the line moved non-degree hiring 3.5 percentage points inside the roles that changed and 0.14 overall. What has to replace it before the posting goes out.
- What to Say When You're Wrongly Accused of Using AI Falsely accused of using AI on an application? Ask what tool and score produced the claim, offer process evidence, and know when an employer won't reopen it.
- The Federal Rule That Can Get You a Copy of Your Hiring Score When a vendor's score about you counts as a consumer report, federal law requires the employer to hand you a copy before rejecting you on it. Here is how to tell.
- Put the Stage With the Best Evidence First, Not the Cheapest The resume screen sits first because it was cheapest to read, not because it knows most. Make a scoped task or a short work conversation the first real gate.
- Twenty Minutes Buys Three Follow-Ups, Not Six Topics Fifteen to thirty minutes is the wrong unit. Size the call in conversational turns: one claim, one opening question, three follow-ups, and a five-minute close.
- Keep the Log Now: It Is the Evidence You Cannot Recreate Specifics about how you used AI decay within weeks. A short log kept at the time is what sources a resume line and survives a follow-up question later.
- Matching Every Keyword Makes You Median, Not Shortlisted Copying every phrase from a posting no longer sets a resume apart. Match the terms that are true, then attach a checkable fact: a number, a system, a result.
- Knockout Questions Are the Only Thing That Can Auto-Reject You A knockout question is a yes/no or select field wired to a rule. It is the one part of a job application that can reject you automatically. Answer it accurately.
- Listing AI Tools on Your Resume Invites One Question A row of AI tool logos on a resume tells a reviewer nothing on its own. List the two you actually rely on, and be ready to describe one real use.
- Models Screening Resumes Show Measured Name Preferences Independent tests have measured name preferences in models used to screen resumes. What they found, and why a vendor's impact ratio is a different kind of evidence.
- How to Prepare for a One-Way Video Interview in an Hour Skip the lighting and background advice. Pull competencies from the posting, build one specific example each, and check the mechanics that actually cost people the round.
- You Can Show AI Skill With No Job That Used It Pick one class project, volunteer task, or personal build, and write it as an accomplishment with the correction included. Two beat a tools list.
- Proxies Survive Deletion Because the Record Rebuilds Them A proxy is any field your screen's decision rides on that carries protected information with no job-related reason. Deletion rarely removes it. Test the load.
- Two Structured Reference Calls Beat Five Courtesy Calls Reference checks are worth running only when they are structured. Two calls on a fixed question set beat five freeform ones, and they belong before the offer.
- You Match Every Requirement and So Does Everyone Else Matching a job posting's requirements now qualifies an application, not distinguishes it. Here is what actually moves you up a crowded queue: scope and evidence.
- Callback Studies Measure the Screen, Not the Hire Name-swap resume experiments prove differential treatment at the screen and nothing past it. What the landmark study says about its own limits, and what to measure.
- Read What the Parser Read Before Blaming Your File Format PDF-versus-Word is stale advice. Extract your resume's plain text in thirty seconds and read it the way a parser does, sourced to two named vendors.
- Write the Screening Criteria Before the First Application Opens Three or four criteria, each naming the evidence that satisfies it and where that evidence comes from, dated and written before anybody opens an application.
- Report the Self-ID Rate Beside Every Ratio or the Ratio Is Unreadable There is no safe response-rate threshold. Bound the result by assigning the unknowns each way, and report the rate per stage beside every number you publish.
- The Seven-Second Resume Study, and What It Does Not Say No published methodology backs the seven-second figure. What is documented is a two-stage read: software narrows the pile first, then a person reads what survives.
- What ChatGPT Should and Should Not Write on Your Resume A model is good at compressing what you supply and bad at supplying it. The honest split between drafting help and generated evidence, sourced.
- Describe the Decision, Not the Data, and NDA Work Still Counts Portfolio advice assumes a shareable artifact. What actually gets scored is the reasoning behind it, and the reasoning is usually the part your agreement never covered.
- Don't Let a Match Percentage Decide Where You Apply A job board computes that percentage from your profile and the posting text. In most cases the employer never sees it or uses it to decide anything.
- Tailoring Is Choosing Your Three Proofs, Not Swapping Keywords One-click rewrites produce a fluent, on-vocabulary resume with nothing specific behind it. The version of tailoring that still works takes about ten minutes.
- Split the Screen Into a Cheap Pass and an Expensive One The 30-second resume rule spreads attention evenly over a pile that is not even. Run a yes-or-no pass on everything, then real minutes on the ties only.
- Most of the Disparity Comes From Settings You Chose, Not Their Model Knockouts, cutoffs, ranking and optional signals are the employer's decisions, and they set selection rates. How to find which one produced a bad ratio.
- A Job Simulation Is a Talking Point, Not a Credential A virtual job simulation is worth doing once if you keep what you produced. Here is why the badge alone convinces nobody, and what to do with the actual work.
- What Job Postings Mean When They Ask for AI Skills AI skills on a posting usually means one of three different things. Learn which one applies to you, then test your own resume line the way employers are told to.
- What an ATS Actually Does to Your Resume File An applicant tracking system parses your resume, stores it, and lets a recruiter search or rank it. It does not grade your writing. Here is what gets you filtered.
- Verification Proves a Record Exists, Not That the Person Did the Work An employment or education verification confirms what an employer or registry filed: dates, title, degree. It cannot establish scope, ownership or contribution.
- The Recruiter Screen Decides One Thing the Application Cannot A recruiter screen has one job: find out whether a named claim on the application survives being asked about twice, and leave a written record of the answer.
- Your Resume Score Comes From the Tool That Sold It to You The company that scores your resume also sells the fix, and the employer systems it claims to predict document no comparable number to check it against.
- Read an Application in Order of What You Can Check The six-second scan was written for the person being read. Order the read by what a third party could confirm: dates and licences, then named specifics, then prose.
- Hidden White Text Lands in the Recruiter's View of Your Resume Hiding keywords in white text reaches the parsed record, and that record is what a recruiter reads with formatting stripped away.
- The Manager Owns the Bar, the Recruiter Owns the Evidence Qualified is two jobs with two owners: the manager defines what the person must be able to do, the recruiter judges whether the evidence meets it. Calibrate on work.
- Software Ranks You. A Person Rejects You. Know Which Happened A rejection has three possible authors: a configured rule, a ranking layer, or a person's read. The timing of your status tells you which one acted, and which is fixable.
- Why AI Resumes All Sound the Same, and What Fixes It AI resumes converge because prompts carry no specifics of your own. The fix is evidence density, not stronger vocabulary or a rewritten tone.
- What an AI Certificate Requirement Actually Filters For A vendor AI certificate is a short multiple-choice exam on one product line. List it as one acceptable form of evidence and keep the requirement on the behavior.
- Are AI Certificates Worth Anything on an Intern's Resume? A Google or Anthropic AI certificate is a self-paced completion; Microsoft's is a proctored exam. Neither proves applied judgment. Four questions settle it.
- An AI Screen Buys Throughput and Costs You the Evidence Automate the parts with no judgment in them: scheduling, transcription, structured notes. Keep the asking and the deciding human, and price what the throughput costs.
- Can You Reject Interns on an AI-Detector Flag? A detector score is a probability, not evidence. Detectors average a 61.3% false-positive rate on non-native English writing; declining on it is unvalidated screening.
- Is It Legal to Reject a Resume on an AI-Detector Result? No federal law bans it. But a detector result used to reject is a selection procedure with no validity evidence, and NYC's Local Law 144 reaches screening.
- Do AI Detectors Work on Interview Transcripts or Written Responses? Detectors flag 61% of non-native English writing as AI, and OpenAI withdrew its own classifier for low accuracy. Read the work instead of the wording.
- An AI-Disclosure Box Is Only Worth Adding If the Answer Changes Something A yes/no attestation collects nothing you can act on. Ask one free-text line about what AI did, and print the rule that disclosure is never a reason to reject.
- What AI Resume Screening Does to Your Pile Before You Open It AI resume screening is a parse layer that loses information and a ranking layer that rewards resemblance to the posting. What each one does, and where to keep the human.
- Rebuilding the Application Form Around What a Model Can't Fill In Length is not the variable. Keep the fields whose answers come from the applicant's own week, drop everything derivable from the posting, and read what is left.
- Your ATS Rejects Only What Your Rules Tell It To Mainstream applicant tracking systems store, parse and filter on rules a person configured. The three that actually reject people, and how to audit each one.
- An AI Screener Buys Throughput, Not Accuracy Buy reading capacity if that is the bottleneck, and configure the tool so it never cuts. What to ask for instead of a bias audit certificate, and how to check you got it.
- Do AI Detectors Work on Resumes and Cover Letters? Detectors misfire on short, formulaic and non-native English writing, so a detector score cuts good candidates. The measured error rates, and what to screen for instead.
- Does GPA Still Predict Anything for Entry-Level Roles? GPA holds where closed-book fundamentals and a licensure exam gate the work, and predicts almost nothing where the first year is judging AI output.
- Your ATS Knockout Questions May Already Be Regulated AI The state definitions turn on what the software does to a candidate, not on what you bought. How to inventory the funnel and classify each screen separately.
- How Do You Know If Your Resume Screen Rejects the Wrong People? A screen that rejects 80% of applicants has outcomes on none of them. Advance a sample from just under the bar, re-run old calls against later work, audit the pass pool.
- False Positives, False Negatives, and Which One You Pay For Every selection process trades a bad hire against a missed one. Name the trade, check it against the role's economics, then buy some visibility into the invisible half.
- An AI Candidate Score Can Be a Consumer Report, Which Changes Your Notices When a third party assembles information about an applicant, the score it returns can be a consumer report, bringing disclosure, authorization and adverse-action duties.
- Should You Hide an Instruction to Trap AI-Written Applications? Don't plant one. It sorts applicants by how carefully they proofread rather than by whether they used AI, and it won't survive syndication. Ask a real question instead.
- Should You Reject a Candidate Who Used AI to Write Their Resume? A field experiment found writing assistance raised hires 8%, with no evidence employers were less satisfied. Reject on claims that fail a check, not the author.
- Your Job Description Is Now the Prompt Every Resume Is Written From Applicants paste the posting into a model, so it stops working as a yardstick. Keep the plain occupational language and move the judging outside the mirror.
- Knockout Questions Are the Only Auto-Reject You Actually Own Knockout questions still reject people, which is why the self-assessed ones are dangerous. Keep the checkable facts, delete the rest, give each one an owner.
- Is the Async Video Round Worth Keeping When Answers Are Scripted? A scripted answer scores higher on content and no different on delivery, so keep the async round for scheduling reach and move the judging into twenty observed minutes.
- Pasting Resumes Into a Chatbot Is a Regulated Employment Decision The risk is not bias or hallucination. It is an evaluation nobody wrote down, applied to some candidates only, in a transcript your company cannot produce.
- Two AI Questions Worth Their Minutes in a Fifteen-Minute Screen Which part of the last job did AI take over, and what did you try that failed. Both need a real job to answer. Then record the claim the next round will test.
- Prompt Engineering Survived as a Skill and Died as a Job Title The skill moved inside ordinary roles and the standalone title mostly went away. Write it into requirements as a behavior and screen it with twenty minutes of real work.
- What Do You Ask a Vendor Who Says They're Bias Tested? Ask which roles the audit ran on, whose data it used, and who signed it. Twelve questions with the answer that should worry you, ready for a vendor review.
- How Do You Reference-Check for AI Judgment When the Reference Says 'They Were Great'? Swap the open question for one incident the reference watched: an AI output that was confidently wrong, and what the candidate did in the next hour.
- What Should You Ask For on the Application Instead of a Cover Letter? Swap the letter for one scored question about a decision the candidate made: the tradeoff, the cost, the outcome. Six role-specific versions and a three-point rubric.
- How to Measure What Your Resume Parser Loses Push thirty resumes from people you already hired through your own apply flow, diff the parsed fields against the documents, and count what the system dropped.
- A Resume Stopped Being a Writing Sample Read a resume for two things only: claims a third party can check, and the order the candidate chose. Grading the prose now grades whichever tool produced it.
- AI Skill Doesn't Survive the Resume Stage A document carries a claim about AI skill, never the behavior. Use the resume stage to mark which claim gets tested, then give everyone the same short task.
- What Is Left to Screen On When Every New-Grad Resume Is AI-Built? A new-grad resume's claims are free to write and impossible to check. Screen the one artifact your role can verify, then move the decision to a first-round act.
- What Do You Screen On When Every Resume Looks Perfect? Screen on records a third party already holds (commits, bylines, licenses, filings), then move judgment to a work sample. What survives AI polish varies by field.
- Skills-Based Hiring Without a Skills Test Is Degree Screening With Extra Steps Removing the degree requirement was half the move. Most firms never built the second half, and the outcome data shows it. What the observation step has to contain.
- Should You Still Ask for a Cover Letter If AI Writes Them All? Keep the letter where prose is the deliverable. Everywhere else, delete the field and require one 100-word answer to a trade-off a generic model answer misses.
- Three Things on an Application You Can Check, and One You Never Will Employment, education and licensure have records behind them. Authorship has none at any price. The claim that matters most needs evidence rather than checking.
- How Do You Verify 'Uses AI Daily' on a Resume in Ten Minutes? Ask for the artifact daily AI use would have left behind (a prompt thread, a diff, an assumption tab), then spend five minutes on one output the candidate refused.
- How Do You Verify 'AI-Proficient' on a Resume? You can't verify it from the resume. Give one short task from the role, allow the AI assistant, and read the working record instead of the deliverable.
- Are Virtual Job Simulations on a Resume Evidence of Anything? A completed job simulation shows self-selection and exposure to one firm's scripted workflow, not performance. Nobody marked it. Weight it like a relevant elective.
- How Do You Tell Who Did the Work on an AI-Built Portfolio? Stop asking whether AI was used. Three questions plus the record the field keeps (commits, version history, source notes) show who made the decisions.
This beat is written by Ella McChesney & Olive.