# ResumeCommand > The full text of every ResumeCommand guide, in one file, for language models and other machine readers. This file concatenates every published article on resumecommand.com in full. Each entry carries its title, canonical URL, publication date, and complete body. For the link-only index, read /llms.txt. ## Guides and articles --- # Two-column resumes and ATS parsing: what actually breaks Source: https://www.resumecommand.com/resources/resume-tips/two-column-resume-ats Published: 2026-09-09 Ask whether two-column resumes are ATS-safe and you will get two confident, opposite answers. Both camps are right, because the answer does not depend on your resume. It depends on which text extractor sits behind the application form, and there are three common ones that disagree with each other by design. ## A PDF has no reading order This is the part almost every guide skips, and it explains everything else. A PDF does not store paragraphs, columns, or a sequence. It stores instructions to draw glyphs at coordinates. When software needs the text back, it has to reconstruct an order that was never recorded. Apache PDFBox, the library underneath a great deal of enterprise document processing, states the problem plainly in its own documentation: "The order of the text tokens in a PDF file may not be in the same as they appear visually on the screen. For example, a PDF writer may write out all text by font, so all bold or larger text, then make a second pass and write out the normal text." The W3C describes the same failure in its accessibility guidance, and its example is exactly a resume sidebar: "some documents use multiple columns, and the reading order is clear visually to sighted users as flowing from the top to the bottom of the first column, then to the top of the next column. But if the document is not properly tagged, a screen reader may read the document from top to bottom, across both columns, interpreting them as one column." Swap "screen reader" for "resume parser" and you have the entire two-column problem. Your layout is not ambiguous to a person. It is ambiguous to software, because the file format never recorded which block comes first. ## Three strategies, three different answers Every extractor picks a strategy for rebuilding that missing order. The three you are most likely to meet behave differently on the identical file. **Content stream order** returns text in the sequence the PDF draws it, which for a document exported from a web page or a word processor is usually the underlying document order. Apache PDFBox does this by default: its documentation notes that "by default PDFBox does not sort the text tokens before processing them due to performance reasons." A sidebar authored before the main column comes out as one clean block, followed by the main column. **Position sorting** rebuilds the order from coordinates, top to bottom and left to right. Anything sharing a horizontal line merges into that line. The Python library pdfplumber works this way, and describes its alternative mode as using "the PDF's underlying flow of characters as a guide for ordering and segmenting the words, rather than presorting the characters by x/y position." Presorting is the default. This is the strategy that shreds a sidebar. **Column detection** tries to identify the columns and undo them. Poppler's `pdftotext`, the command-line tool behind many pipelines, takes this route: its manual says the default is to "'undo' physical layout (columns, hyphenation, etc.) and output the text in reading order." When the detection works, a two-column resume reads correctly. When it misfires, you get a hybrid of the other two outcomes. So the honest answer to "is a two-column resume ATS-safe" is that it is safe under the first and third strategies and unsafe under the second, and you never find out which one you drew. ## What this looks like on a real resume We ran our own template library through a position-sorting extractor, the pessimistic case, to see how each layout survives. The results were not subtle. Our full-height sidebar templates, the ones with a coloured column running the height of the page, came apart. Here is the top of one of them as the parser read it: ``` Experience Senior Machine Learning Mar — Present Engineer (LLM & Retrieval Lead) Dalad Nosson ``` The candidate's name lands in the middle of a job title. Every word is present and nothing is missing, which is precisely why this failure is so easy to miss: a human proofreading the PDF sees a clean document. A recruiter searching that database for a job title finds a fragment. The same file, read by the same library with content-stream ordering switched on, comes out perfectly ordered: name, headline, contact details, summary, then the main column. The file was never broken. The reader was. Do not trust a visual check alone. Open your PDF, select all, and paste into a plain text editor. That shows you one extraction strategy, not all three, but it catches the worst cases in about ten seconds. ## How common is this, really An October 2025 paper from a team studying large-scale resume extraction puts a number on the exposure: "approximately 20% of resumes employ non-linear, multi-column layouts that break the standard top-to-bottom, left-to-right reading flow." Reconstructing reading order from those layouts is treated as a distinct engineering problem, separate from reading the text itself. That is a useful frame. Roughly one resume in five is carrying a risk its author cannot see, and the systems on the other side are actively building machinery to compensate for it. Some of that machinery works. You have no way to know whether the employer you are applying to has it. ## The rule that gets you columns anyway The useful distinction is not one column versus two. It is whether anything sits beside your work history. A full-height sidebar shares a horizontal line with every entry in your main column, so position sorting interleaves the whole document. That is the arrangement that fails. A **band** is different. A band is a section that owns its full width and happens to lay its own items out in columns, with nothing beside it. Your skills list in two or three columns is a band. So are languages and interests. A position-sorting parser merges the items within one row of that band, and nothing else, because there is no other content at that height to merge with. When we rebuilt a template on that principle, it scored full marks on the same check that our sidebar layouts failed. Three details did the work: 1. **Bands hold short, single-line items only.** We first tried a two-column education section and watched the next section's heading fall into the gap between two entries of unequal height. Multi-line entries belong at full width. 2. **Use a grid that flows across rows, not newspaper columns.** CSS multi-column flows down column one, then down column two, so a visual row is items 1, 13, and 25. A grid flows left to right, so a visual row is items 1, 2, and 3, and reading across it reads them in order. 3. **Put a visible separator between the cells.** This one mattered more than we expected. Without it, a merged row reads as `Prompt engineering Cross-functional collaboration`, two phrases run together. With a middot in each cell, the same row reads as `Prompt engineering · Inference optimization · Retrieval systems ·`, which is a correctly delimited list. That single change moved our banded template from a passing score to a perfect one. You keep the density and the visual structure of a two-column resume. You give up only the full-height sidebar, which is the one element that cannot be made safe. ## One more trap worth knowing While testing, we found a font setting that silently deleted every year from a resume's text layer. The dates rendered correctly on screen and in print, but the extracted text read `Mar Present`. The cause was a typographic feature that swaps in alternate digit glyphs, which the PDF export then wrote without a mapping back to real characters. There was no visual symptom at all. The only way to catch it was to extract the text and look. The general lesson matters more than the specific bug: what a PDF displays and what a PDF yields as text are two different things, produced by two different mechanisms. Styling choices can quietly break the second without touching the first. This is also why the copy-and-paste test is worth doing on every resume you build, whoever built it. ## What to do If you are deciding on a layout right now: - **Default to a single column for the parts that carry your history.** Work experience, education, and projects should never have anything beside them. - **Use bands for short lists.** Skills, languages, tools, and interests can sit in two or three columns safely, with a visible separator between items. - **Keep dates on the same line as the role they belong to.** A right-aligned date column is a second column, and it extracts as a detached block of bare years. - **Use standard section headings.** This is the cheapest reliability you can buy, and it is covered further in our guide to [ATS optimisation](/resources/resume-tips/ats-optimization-2026). - **Test by extracting, not by looking.** Select all, paste into plain text, and read what comes out. A two-column resume is not disqualifying, and anyone who tells you it is has skipped the part where three different parsers give three different answers. But a sidebar is a bet on which library the employer runs, placed without knowing the odds. Bands give you most of the design for none of the wager. --- ResumeCommand's templates are built and checked against this failure mode, and you can run the same readability analysis on any template before you download it, so you see what a parser sees rather than guessing. Try it free → [ResumeCommand](https://www.resumecommand.com) ## Sources - Apache PDFBox, *PDFTextStripper API documentation* (text token ordering and the `setSortByPosition` default): [pdfbox.apache.org](https://pdfbox.apache.org/docs/2.0.0/javadocs/org/apache/pdfbox/text/PDFTextStripper.html) - pdfplumber, *extract_text and the use_text_flow parameter*: [github.com/jsvine/pdfplumber](https://github.com/jsvine/pdfplumber) - Poppler, *pdftotext manual* (default reading order, `-layout` and `-raw`): [mankier.com](https://www.mankier.com/1/pdftotext) - W3C, *Technique PDF3: Ensuring correct tab and reading order in PDF documents*, Techniques for WCAG 2.0: [w3.org](https://www.w3.org/TR/WCAG20-TECHS/PDF3.html) - Zhu et al., *Layout-Aware Parsing Meets Efficient LLMs: A Unified, Scalable Framework for Resume Information Extraction and Evaluation* (October 2025): [arxiv.org](https://arxiv.org/html/2510.09722v1) --- # How to prepare for AI-led and one-way video interviews Source: https://www.resumecommand.com/resources/interview/ai-video-interviews Published: 2026-07-26 You get the invite, open the link, and there is no interviewer. Just a question on screen, a countdown, and a record button. One-way video interviews, often with an AI layer that transcribes or scores your answers, feel impersonal and a little unnerving. But the format is predictable, and predictable means preparable. Here is what is really going on and how to walk in ready. ## What these interviews actually are A one-way, or asynchronous, video interview asks you to record answers to preset questions on your own, for a recruiter or a system to review later. Sometimes a human watches the recordings; sometimes an AI tool transcribes your answers and scores them against the role before a person ever sees them. The format is now common, especially for early-stage screening and high-volume roles. In SHRM's 2025 Talent Trends survey of more than 2,000 HR professionals, 51% of organizations said they use AI to support recruiting, with resume screening and candidate communication among the top uses. The trade is speed for connection. You lose the back-and-forth of a live conversation, and you gain the ability to do it on your own schedule. Treat it as a real interview that happens to be recorded, not as a casual video message. ## What they do not measure, and the myth to drop The most common fear is that an algorithm is reading your face, scoring your smile, your eye contact, your micro-expressions. At reputable vendors, that era is over. In January 2021, HireVue, one of the largest video interview providers, announced it had removed facial-expression analysis from its product, after concluding that visual analysis no longer added meaningful predictive value and that the public concern was not worth it. In other words, the face-scoring approach was dropped in part because it did not work well. Do not perform for the camera. The substance of your answers, the words you actually say, is what a modern system transcribes and evaluates, not whether you smiled at the right moment. Prepare what you say, not a facial routine. There are fringe tools that still claim to read personality from a face or voice. Treat that as a reason to know your rights, not a reason to rehearse expressions. ## Know your rights before you record Depending on where you or the employer are based, you may be legally entitled to notice and to an alternative. This is worth knowing, because you can ask. - **New York City** requires employers using an automated employment decision tool to notify candidates at least 10 business days beforehand, and to let them request an alternative selection process or a reasonable accommodation. The tool must also pass an independent bias audit whose summary is published. - **Illinois** requires employers to tell you before an AI-analyzed video interview that AI will be used, explain in general terms how it works and what it evaluates, and obtain your written consent. You can also request that your video be deleted within 30 days. - **In the European Union**, the AI Act classifies systems used to recruit, filter applications, and evaluate candidates as high-risk, which places transparency and oversight obligations on the employer. In **France**, the CNIL requires that candidates be clearly informed when AI is used to analyze their application and for what purpose, and it has made recruitment a priority area for enforcement. The practical upshot is simple: it is reasonable to ask the recruiter whether AI is used, how, and whether a human reviews the result. Asking for an accommodation or a human review is a legitimate request, not a red flag. ## How to prepare, step by step This is where the interview is won. The mechanics differ from a live call, so prepare for the mechanics, not just the answers. ### Sort the setup - Test your camera, microphone, and upload speed on the actual platform if a practice question is offered. Most provide one; use it. - Pick a quiet, well-lit spot with a neutral background. Light in front of you, not behind. Camera at eye level. - Have a stable connection and a backup, and close everything that could interrupt a recording. ### Prepare like it is a structured behavioral interview Async questions are usually behavioral or motivational: "tell me about a time," "why this role." Prepare a handful of concrete stories using a clear structure, which is exactly what the [STAR method](/resources/interview/star-method) is for. Because there is no interviewer to ask a follow-up, your first answer has to be complete on its own. - **Answer the words of the question.** A system transcribes what you say and looks for relevance to the role, so be specific and use the concrete, truthful terms that fit the job. Front-load your point, then support it. - **Be concise and structured.** Respect any time limit, and do not ramble to fill it. A tight, ninety-second answer beats three minutes of padding. - **Research the company first** so your motivational answers are specific rather than generic. A [thirty-minute company research routine](/resources/interview/research-company-before-interview) gives you the details that make "why this role" credible. ### Practice the unnatural parts - **Rehearse talking to a lens with no reaction.** Record yourself and watch it back once. The silence where a nod should be is the thing people find hardest; get used to it. - **Look at the camera, not at your own image.** It reads as eye contact to a human reviewer. - **Bring slightly more energy than feels natural.** Recordings flatten warmth, so a touch more animation lands as normal, engaged presence. - **Use re-records wisely.** If the platform allows a retake, know that before you start, but do not burn your prep time chasing a perfect take. Good and done beats perfect and rushed. Read the on-screen instructions before the first question: how many questions, how much prep and answer time each, and whether re-records are allowed. Knowing the rules removes half the stress, and it stops a surprise time limit from cutting you off mid-sentence. ## One honesty caveat Do not wire up an AI to generate or read answers to you in real time. Scripted, model-written answers read as canned, some platforms flag reading-off-screen behavior, and anything you claim here you will have to back up in the live round with a human. Prepare thoroughly, use notes as light prompts if allowed, and then answer as yourself. The goal is to sound like a prepared version of you, not like someone else. ## The takeaway A one-way AI interview is not a test of how well you charm a camera. It is a structured interview with the human moved to later, and it rewards the same things a good live interview does: specific stories, clear structure, genuine motivation, and preparation. Sort your setup, prepare STAR answers that stand on their own, know the rights that let you ask questions or request a human, and bring a little extra energy to a room with no one in it. Do that and the format stops being a hurdle and becomes just another interview you were ready for. --- Getting the interview is step one, and that is where a resume that clearly matches the role does its work. ResumeCommand tailors your resume from your own history against a specific job posting in under 5 minutes, so more of these invitations land in the first place. Then the preparation above is what carries them. Try it free → [ResumeCommand](https://www.resumecommand.com) --- ## Sources - SHRM, *2025 Talent Trends: The Role of AI in HR* (survey of 2,040 HR professionals, February 2025): [shrm.org](https://www.shrm.org/topics-tools/research/2025-talent-trends/ai-in-hr) - SHRM, *HireVue Discontinues Facial Analysis Screening* (2021): [shrm.org](https://www.shrm.org/topics-tools/news/talent-acquisition/hirevue-discontinues-facial-analysis-screening) - New York City, *Automated Employment Decision Tools* (Local Law 144, effective July 2023): [rules.cityofnewyork.us](https://rules.cityofnewyork.us/rule/automated-employment-decision-tools-updated/) - State of Illinois, *Artificial Intelligence Video Interview Act* (820 ILCS 42): [ilga.gov](https://www.ilga.gov/legislation/ilcs/ilcs3.asp?ActID=4015) - European Union, *AI Act (Regulation 2024/1689), Annex III on high-risk systems*: [artificialintelligenceact.eu](https://artificialintelligenceact.eu/annex/3/) - CNIL, *IA et RGPD: recommandations* and *Contrôles prioritaires 2026*: [cnil.fr](https://www.cnil.fr/fr/controles-prioritaires-2026) --- # Showing emerging skills on your resume without faking them Source: https://www.resumecommand.com/resources/resume-tips/emerging-skills Published: 2026-07-26 You picked up a new tool six months ago. You have shipped one real thing with it, you are far from an expert, and now you are staring at a job posting that asks for it. Do you list it? How? The honest answer is more useful than either extreme, because the goal is not to look impressive, it is to get into a room you can actually hold your own in. ## Why emerging skills belong on your resume The skills that define a job are a moving target, and everyone knows it. LinkedIn's 2025 Work Change Report estimates that by 2030, 70% of the skills used in most jobs will have changed, with AI acting as the main accelerant. The same report notes that the rate at which people add new skills to their profiles has jumped 140% since 2022. In other words, showing skills you are actively building is not padding; it is exactly what a current, credible professional looks like. So the question is never "should I mention the new skill." It is "how do I represent it at the level I actually have, so the resume opens a door I can walk through." Overstate it and you win an interview you then lose badly. Understate it and you screen yourself out of roles you could grow into. The skill is threading that needle. An emerging skill is an asset when it is framed as one. The problem is never that you are still learning something. The problem is a resume that implies you have mastered it, followed by a technical screen that proves you have not. ## The trap: overstating proficiency Skills are the easiest part of a resume to inflate and the easiest to expose. A padded years-of-experience line survives until a background check; a padded skill dies in the first technical conversation. Claim "expert in Kubernetes" and a competent interviewer needs about two questions to find the floor. That failure costs you more than never listing it, because now the interviewer is also recalibrating how much to trust the rest of your resume. This matters more as hiring leans on skills. When a role is screened on skills rather than pedigree, the claimed skill gets tested, in a take-home, a pair session, or a pointed question. Honesty here is not just ethics; it is self-interest. The version of you that gets and keeps the offer is the one whose resume matched what showed up in the room. ## How to show a skill you are still building, honestly You have more honest options than a flat keyword list. The trick is to signal level and show evidence, not to hide the skill or oversell it. - **Signal proficiency instead of implying mastery.** A simple, honest scale reads clearly: "Proficient: Python, SQL. Working knowledge: Rust, Terraform." You are telling the reader exactly where you are, which is far more credible than one undifferentiated pile of technologies. - **Show evidence, not adjectives.** "Built and deployed a side project in React" says more than listing "React" among ten others. A repository, a shipped feature, a completed course, or a certification in progress all convert a claim into a fact. - **Name the learning in progress.** "Currently completing the [course or certification]" is a legitimate, honest line. It signals direction and initiative without pretending the journey is finished. - **Anchor the new skill to a proven one.** If you are strong in one area and building an adjacent one, say so: "Applying 6 years of backend experience while building depth in data engineering." That frames the emerging skill as a credible extension, not a leap. - **Put level-setting where it counts.** The strongest place to contextualize a new skill is next to real work. This is the same instinct behind [quantifying your bullet points](/resources/resume-tips/quantify-bullet-points): specifics beat labels. Ask one question of every skill you list: if an interviewer opened with "tell me about a time you used this," could you answer with something real? If yes, list it, at the level your story supports. If no, it is not ready for the resume yet. ## What not to do - **Do not list a tool you touched once as a core skill.** A single tutorial is not "experience." If it belongs anywhere, it belongs under "familiar with," not among your strengths. - **Do not claim years you do not have.** "3 years of TypeScript" is checkable against your own timeline and your projects. Vague is safer than false, but specific and true is best of all. - **Do not keyword-stuff for the ATS.** Cramming every term from the posting into a skills block to beat the filter just moves the failure one step later, into an interview where the mismatch is obvious. Match honestly instead, the way you would when [tailoring rather than tweaking](/resources/resume-tips/tailoring-vs-tweaking) an application. - **Do not bury real strengths under aspirational ones.** If half your skills section is things you are "learning," the reader cannot find what you are actually good at. Lead with proven, add emerging with context. ## Reframe: emerging skills as a skills-first story If you are deliberately pivoting, a whole resume can be built to carry emerging skills well. Grouping your experience around capabilities, and showing the projects that back each one, lets a growing skill sit next to the evidence for it rather than in a decontextualized list. That is the core idea behind a [skills-first resume](/resources/resume-tips/skills-first-resumes), and it is the most honest home for a skill you are still developing: value first, level made clear by the work attached to it. ## The honest takeaway Emerging skills are not something to hide or to fake; they are something to frame. Show them at the level you actually have, back them with evidence, and let the proven skills lead. Do that and your resume does the one thing it is supposed to do: get you into a conversation you can win on the merits, not one you have to survive. In a market where most job skills are changing within a few years, the candidate who represents a growing skill set honestly is not the weaker applicant. Often, they are the more current one. --- ResumeCommand tailors your resume from your own history against a specific job posting, surfacing the skills that genuinely match the role and phrasing them against the work you have actually done. It helps you show relevant, real skills at the right level, rather than padding a list to beat a filter. Paste a job URL and see it in under 5 minutes. Try it free → [ResumeCommand](https://www.resumecommand.com) --- ## Sources - LinkedIn, *Work Change Report* (January 2025): [economicgraph.linkedin.com](https://economicgraph.linkedin.com/research/work-change-report) --- # No salary range posted: should you apply, and what to ask Source: https://www.resumecommand.com/resources/job-search/no-salary-range Published: 2026-07-25 You find a role that fits, you get to the bottom of the posting, and there is no salary. No range, no "competitive," nothing. The instinct is either to skip it out of principle or to apply anyway and hope. Neither is a plan. A missing range is a piece of information, and once you know how to read it, you can decide quickly whether the role is worth your time and how to get a number before you sink hours into it. ## Why so many postings still hide the range Two things are true at once: pay transparency is spreading fast, and plenty of employers still resist it. The spread is real and measurable. More than a dozen U.S. states now require employers to disclose pay ranges, and in most of them the range has to appear in the posting itself, not just be offered on request. A 2025 National Bureau of Economic Research study found that after these laws took effect, employers raised the share of postings that include salary information by about 30 percentage points, and advertised wages rose modestly, between 1.3% and 3.6%. Transparency is becoming the default, and it does not appear to hurt hiring. But where it is not required, many employers leave the number out on purpose. Sometimes the reason is defensible: the band is genuinely wide, or the budget is not final. Often it is strategic: they would rather you name a figure first so they can anchor low, or they want to avoid unsettling current employees who might be paid less than the new posting implies. A missing range is not automatically a bad sign, but the reason behind it matters. "The band is wide and depends on level" is a fair answer. "We do not share that this early" often means they want the negotiating leverage that comes from you guessing first. ## What the silence usually signals Before you decide, read the rest of the posting for context. The absence of a number means different things depending on what surrounds it. - **Small company, detailed and specific posting.** Often just an oversight or a founder who has not caught up to the norm. Low risk. Worth a quick ask. - **Large company in a state with disclosure laws, still no range.** Either the role is based somewhere exempt, or they are cutting it close. Fair to ask directly. - **Vague responsibilities plus a missing range plus "fast-paced environment."** The posting is doing a lot of hiding. Treat it with more caution. - **Recruiter reaches out to you with no range.** Perfectly normal at the outreach stage. This is the easiest case to ask in, because they came to you. The pattern to watch for is not a single missing number; it is a posting that is vague about everything. A specific role that just forgot to list pay is very different from one that is evasive about the work, the level, and the money all at once. ## Should you apply? A quick decision rule You do not need certainty, you need enough signal to justify the time. Apply when at least one of these is true: - The role is a strong fit and you would take a fair offer, so you are willing to spend one message finding out the number. - The company or team is one you specifically want, enough that the range is worth a short conversation. - You have leverage, a current job or other options, so an early screening call costs you little. Think twice when the posting is vague across the board, when you have no room to walk away from a lowball, or when your own market number is far above what the company's size and stage could plausibly pay. In that last case, a two-line question up front saves everyone a week. The goal is to spend your effort where a real offer could actually land, the same discipline behind running a [systematic job search](/resources/job-search/systematic-job-search) instead of applying to everything. ## How to get the number without losing leverage If you decide the role is worth it, do not apply blind and hope the topic comes up. Surface the range early, politely, and without being the one who blinks first. **Ask before you invest hours.** A short note to the recruiter or in the application message works: "Before I put together a tailored application, could you share the budgeted range for this role? I want to make sure we are aligned before we both invest time." This is reasonable, professional, and increasingly expected. **If they push the question back to you,** give a researched range rather than a single number, and frame it around the market: "Based on the scope and comparable roles, I am targeting the region of X to Y, and I am flexible depending on the full package." You have named a floor without boxing yourself in. **Do your homework first** so your number is grounded. Public salary data, postings for the same role at companies that do disclose, and your own recent offers all give you a defensible band. When the real negotiation comes later, the same preparation carries over; this is where a proper read of [salary negotiation for technical roles](/resources/interview/salary-negotiation) pays off. Never volunteer your current salary, and know that in many places they cannot ask. As part of the same transparency push, a growing number of jurisdictions have banned employers from asking candidates their salary history, so pivot a "what do you make now?" into "what I am targeting for this role is X," and stay there. ## The wide-range trap Transparency laws created a loophole, and you should recognize it. Because most laws require a range but rarely say how wide it can be, some employers post enormous bands, think "$90,000 to $190,000," that technically comply while telling you almost nothing. A 2026 study from Cornell researchers, published in Harvard Business Review, found that unusually wide ranges can actually backfire and discourage some candidates, women in particular, from applying at all. Treat a very wide range like a missing one: a prompt to ask where in that band this specific role and your specific experience would land. "The posting lists $90,000 to $190,000; for someone at my level, what part of that range is realistic?" is a fair, level-headed question, and the answer tells you a lot about how the company negotiates. ## Where this is heading The direction of travel is clear. In the United States, more states add disclosure rules each year. In Europe, the EU Pay Transparency Directive requires employers to give candidates the pay or a pay range for the role, and to stop asking about salary history; France's draft transposition goes further and would require the range to appear in the advert itself. Within a few years, a posting with no number will look less like caution and more like a company that is behind, or hiding something. Until then, the missing range is a question, not a wall. Ask it early, and you turn a frustrating blank into useful information. ## The honest takeaway A job posting with no salary is not a reason to give up, and it is not a reason to apply on blind faith. It is a signal to read in context and a prompt to ask one direct question before you spend real effort. Read the rest of the posting, decide whether a fair offer would tempt you, and get the number early using a researched range rather than your own history. Do that and you protect your time, keep your leverage, and only go deep on the roles that could actually pay. --- ResumeCommand helps you move fast once a role clears that bar. Paste the job URL, and you get a tailored, ATS-optimized resume built from your own history in under 5 minutes, so the time you save on rewriting goes into the conversations that decide the offer, including the one about pay. Try it free → [ResumeCommand](https://www.resumecommand.com) --- ## Sources - David Arnold, Simon Quach, and Bledi Taska, *The Impact of Pay Transparency in Job Postings on the Labor Market*, NBER Working Paper 34480 (2025): [nber.org](https://www.nber.org/papers/w34480) - Alice J. Lee, Tae-Youn Park, and Sungyong Chang, *Posting a Wide Salary Range Can Deter Women from Applying*, Harvard Business Review (February 2026): [hbr.org](https://hbr.org/2026/02/posting-a-wide-salary-range-can-deter-women-from-applying) - Patriot Software, *Pay Transparency and Hiring Survey* (1,000 U.S. respondents, February 2026): [patriotsoftware.com](https://www.patriotsoftware.com/blog/payroll/pay-transparency-hiring-survey/) - Paycor, *Pay Transparency Laws by State* (2026): [paycor.com](https://www.paycor.com/resource-center/articles/pay-transparency-laws-by-state/) --- # Employment gaps on your resume: how to handle them honestly Source: https://www.resumecommand.com/resources/resume-tips/employment-gaps Published: 2026-07-25 You have a gap in your history, a few months or a few years out of work, and you dread the moment a recruiter notices it. The temptation is to paper over it: round the dates, stretch a job, quietly erase the awkward stretch. That is a mistake, and an unnecessary one. A well-presented gap costs far less than you fear; a disguised one can cost you the job. Here is how to handle it honestly. ## What recruiters actually think about a gap Start with the evidence, not the anxiety. Yes, a long spell out of work can weigh on your chances, but less than you imagine, and not in the way you fear. A large American field experiment by the economists Kroft, Lange, and Notowidigdo sent roughly 12,000 fictitious resumes to real job postings across the 100 largest U.S. metros. The finding: the likelihood of getting a callback does fall as an unemployment spell lengthens, but the majority of that decline is concentrated in the first eight months. In other words, employers read time out of work as a signal about quality they cannot yet see, not as an automatic disqualification. Past that early window, each additional month matters much less. And attitudes are shifting. LinkedIn's 2022 research, which surveyed nearly 23,000 workers and more than 7,000 hiring managers, found that 62% of employees have taken a career break at some point, and nearly half of employers now view candidates with career breaks as an untapped talent pool. A gap is common, and increasingly ordinary. What you do with it is what separates candidates. The gap is not the problem. The absence of an explanation is. Faced with a blank stretch and no context, a recruiter fills the silence with their own assumptions, and those are rarely in your favor. ## The golden rule: explaining beats hiding If you take one thing from this article, take this: an explained gap beats a silent one. A field experiment titled "Sick and Tell" measured exactly this. Its authors found that an applicant whose gap was explained, even by a serious illness like cancer, received significantly more callbacks than an applicant whose gap was left unexplained. A credible explanation, they concluded, substantially reduces the "scarring" effect of time out of work. The recruiter is not looking for a spotless path; they are looking to not be surprised. Employers say as much themselves. In that same LinkedIn research, 51% of hiring managers said they would be more likely to call a candidate back once they understood the reason for the break. Context is not an excuse. It is the piece of information that unlocks the rest of your resume. ## How to present a gap on the resume, honestly Being honest does not mean laying everything bare. It means falsifying nothing while still framing how the gap is read. A few legitimate techniques: - **Use years, not months.** Writing "2022 to 2024" instead of "March 2022 to January 2024" is an accepted convention that naturally absorbs short gaps. That is not lying; it is choosing the granularity. - **Name the break instead of leaving a void.** A plain line beats a blank: "2023 to 2024, career break, coursework and personal project." LinkedIn even offers a dedicated "career break" entry, precisely because the practice has become normal. - **Show what the time contains.** Training, a certification, freelance work, volunteering, caregiving, a startup attempt: all of it fills a gap with real content. A skill you built during the break is an argument, not a patch. - **Consider a skills-based layout** when the gaps are many. Grouping your achievements by area rather than a strict timeline puts value ahead of dates. That is the same logic behind a [skills-first resume](/resources/resume-tips/skills-first-resumes). Tie the gap to what you can do, not to what you went through. "I used the year to train in X and ship Y" tells a story of progress. "I was unemployed" tells a story of absence. Both are true; one works for you. ## What never to do The line between "presenting well" and "lying" is simple: you may choose what to emphasize, never invent what is false. - **Do not falsify dates.** Stretching a job to cover a jobless stretch is a verifiable lie. Employment verification, reference checks, and a simple cross-check against your LinkedIn profile expose it, and a caught inconsistency does far more damage than the gap it was meant to hide. - **Do not invent a job or an employer.** A fabricated role is grounds for rejection, and for firing even after you are hired. - **Do not over-explain.** The opposite failure is burying the recruiter in justification, which only draws attention to the gap. One calm, matter-of-fact sentence is enough. This is one of the [resume mistakes that get you filtered out](/resources/resume-tips/five-resume-mistakes): saying too much about what should stay brief. - **Do not leave a total blank** and hope it slips by. It does not slip by; it invites speculation. ## In the interview: brief, honest, forward-looking The resume opens the door; the interview decides. Prepare one sentence, two at most, that names the reason without drama, then steers the conversation back to the role. > "I took a year to care for a family member. I used the time to complete a data engineering course, and I am fully available and motivated for this role." The shape is always the same: the reason, what you took from it, your availability now. You do not owe anyone an apology for a break; you owe them evidence that you are ready today. A recruiter who sees that the topic does not rattle you stops treating it as one. ## The honest takeaway A gap on your resume is neither a flaw to hide nor a fate to endure. It is information to frame. The evidence converges on one point: what penalizes you is not the break itself so much as the silence around it. Use year-level dates, name the break, show what it contained, and prepare a short, honest explanation for the interview. You do not need to lie to present yourself well; you need to choose what you put in the light. --- Once the story is clear, every application still has to carry it. ResumeCommand starts from the job posting and your own history to produce a tailored, ATS-optimized resume in under 5 minutes, so the skills and experience that matter for the role lead, and a gap is never the first thing a reader sees. Try it free → [ResumeCommand](https://www.resumecommand.com) --- ## Sources - Kory Kroft, Fabian Lange, and Matthew J. Notowidigdo, *Duration Dependence and Labor Market Conditions: Theory and Evidence from a Field Experiment*, NBER Working Paper 18387 (2012): [nber.org](https://www.nber.org/papers/w18387) - Sheryll Namingit, William Blankenau, and Benjamin Schwab, *Sick and Tell: A Field Experiment Analyzing the Effects of an Illness-Related Employment Gap on the Callback Rate* (2020): [benjaminbschwab.com](https://benjaminbschwab.com/wp-content/uploads/2020/09/sick_and_tellwp.pdf) - LinkedIn, *Career Breaks research* (March 2022): [linkedin.com](https://www.linkedin.com/business/talent/blog/product-tips/linkedin-members-spotlight-career-breaks-on-profiles) --- # Job board consolidation: what the 2025 shakeout means Source: https://www.resumecommand.com/resources/blog/jobboard-consolidation-2026 Published: 2026-07-17 For twenty years the job board was the front door to the labor market: a search box, a wall of listings, an apply button. In 2025 that model came apart. One legacy giant went bankrupt, another was absorbed into its biggest rival, and the survivors started rebuilding themselves around AI. This is not a story about a bad year for a few websites. It is a structural shift in how hiring works, and it changes how you should run your search. ## What actually happened in 2025 Two events, weeks apart, tell the story. In June 2025, CareerBuilder and Monster, the names that defined online job hunting in the 2000s, filed for Chapter 11 bankruptcy; the two had merged in 2024 under Apollo Global Management and Randstad, were still not viable, and their assets were sold off in pieces. A few weeks later Recruit Holdings, the Japanese parent of Indeed and Glassdoor, announced roughly 1,300 job cuts and folded Glassdoor into Indeed, the third straight year of cuts at the group after about 2,200 in 2023 and 1,000 in 2024. One company died, the other consolidated, and both were reacting to the same force. That force is AI. The classic job board made money on friction: charge employers to post, sell visibility on top, monetize job seekers scrolling listings. AI removes that friction on every side at once, because writing a listing, finding a role, and applying are each close to a one-prompt task now. When the cost of every step falls toward zero, a business built on charging for those steps loses its ground. The survivors know it: Recruit's stated goal is to turn Indeed from a search engine for jobs into a matching engine, its CEO says roughly a third of the company's new code is already written by AI, and folding Glassdoor in leaves one fewer independent front door. The layoffs are not a side event; they are the restructuring. ## The arms race that reshaped both sides Here is the part that hits your search directly. As the platforms leaned into AI, so did everyone using them. On the candidate side, volume exploded: LinkedIn says applications on its platform rose more than 45% year over year, with nearly 9,500 submitted every minute, and in HireVue's 2026 research around 71% of candidates said they use AI to help write their resumes. Employers answered with more automation and more suspicion. In Greenhouse's 2025 AI in Hiring Report, a survey of more than 4,100 people across four countries, roughly two in three hiring managers (65%) reported catching applicants using AI deceptively, and about three in four (74%) were more worried about fraud than a year earlier. This is the "doom loop": candidates use AI to send more, employers use AI to filter more, and both sides trust the result less. Sending a higher volume of generic applications now pushes you deeper into the pile the filters are built to discard. Volume is no longer an advantage, because volume is exactly what everyone else also has. ## The catch: not every posting is a real job Now that posting is nearly free, not every listing you see is a job anyone intends to fill, and you usually cannot tell which from the outside. Ghost postings are not new or an AI invention: roles that do not exist have drawn complaints since at least 2003, and the Congressional Research Service, which has written about them, cautions that reliable estimates of how common they are remain hard to pin down. The official data does not settle it either, since it counts roles open on a single day rather than jobs actually filled. Ghost postings persist for ordinary reasons, from building a pipeline for later to projecting growth or testing the salary market. What matters to you is simple: a meaningful share of the roles you see may never hire anyone. ## What this means for how you job-search Put the two forces together. AI has made application volume free for everyone, so volume has stopped being a strategy. And a real slice of postings are ghosts you cannot pre-screen. The losing move in that environment is to spend an hour hand-crafting a resume for a single posting that may not be real, then repeat it fifty times. The winning move is to keep quality high while driving the cost per application down: - **Lead with signal, not volume.** A smaller number of genuinely tailored applications, aimed at roles you can verify are real, beats a spray of generic ones. Our guide on the [hidden job market](/resources/job-search/hidden-job-market) covers how to find roles through people rather than through the flood. - **Spend effort where the role is verifiable.** A posting with a named hiring manager, a specific team, a recent date, and a recruiter who actually replies is worth real tailoring. A vague listing that has sat open for months, with no owner and no visible process, is where a ghost most often hides. Give it a light touch or skip it. - **Tailor efficiently, not obsessively.** Mirror the posting's real requirements, but do not rebuild your resume from scratch each time. The [companion piece on how AI actually screens resumes](/resources/blog/ai-in-hiring-2026) explains what the filters reward and what still needs a human to believe it. - **Keep the substance yours.** With recruiters actively hunting for machine-written applications, an AI-generated resume that reads as generic is now a liability, not a shortcut. Use AI for leverage, keep the facts real and defensible. - **Treat relationships as the moat.** A referral routes around both the AI filter and the ghost-posting problem at once, because a human is vouching that the role and your fit are both real. Reframe the math. If you cannot tell which postings are real, the smart response is not to apply to fewer roles, it is to make each quality application cheap enough that a ghost posting costs you five minutes instead of an hour. Low cost per application, high quality per application. That is the combination the new market rewards. ## The honest takeaway The job board era did not end because job boards were bad. It ended because AI collapsed the friction they were built on, and the market is reorganizing around matching instead of listings. For you, the practical shift is simple to state and harder to live: stop competing on volume, because everyone now has infinite volume, and start competing on signal, tailoring, and real human connection, because those are the things AI has made scarce. That is where a tool earns its place. ResumeCommand works from your own career history: paste a job URL, and it extracts the role's key signals, scores how well your background matches, and produces a tailored, ATS-ready resume in under five minutes. The point is not to help you apply to more ghosts faster. It is to make a genuinely good application cheap enough that you can afford to send it only where it counts, and keep the substance yours. Try it free → [ResumeCommand](https://www.resumecommand.com) --- ## Sources - Recruit Holdings / Indeed Newsroom, *Recruit Holdings shares long-term "Simplify Hiring" vision and strategy* (2024): [indeed.com](https://www.indeed.com/news/releases/recruit-holdings-indeeds-parent-company-shares-long-term-simplify-hiring-vision-and-strategy-through-virtual-investor-update) - CBS News, *Indeed and Glassdoor to lay off 1,300 workers as AI shakes up job search business* (2025): [cbsnews.com](https://www.cbsnews.com/news/indeed-glassdoor-layoffs-ai-job-search/) - ERE, *Indeed and Glassdoor hit by more layoffs as Recruit restructures HR tech division* (2025): [ere.net](https://www.ere.net/articles/indeed-and-glassdoor-hit-by-more-layoffs-as-recruit-restructures-hr-tech-division) - CNN Business, *Monster and CareerBuilder, once popular with job seekers, file for bankruptcy* (2025): [cnn.com](https://www.cnn.com/2025/06/25/business/monster-careerbuilder-bankruptcy) - LinkedIn, application-volume data as reported by CNBC, *Recruiters are drinking through a fire hose of job applications* (2025): [cnbc.com](https://www.cnbc.com/2025/10/29/recruiters-are-drinking-through-a-fire-hose-of-job-applications-experts-say.html) - HireVue, *2026 Global AI in Hiring Report*: [hirevue.com](https://www.hirevue.com/resources/report/2026-global-ai-in-hiring-report) - Greenhouse, *2025 AI in Hiring Report* (November 2025): [greenhouse.com](https://www.greenhouse.com/newsroom/an-ai-trust-crisis-70-of-hiring-managers-trust-ai-to-make-faster-and-better-hiring-decisions-only-8-of-job-seekers-call-it-fair) - US Bureau of Labor Statistics, *Job Openings and Labor Turnover Survey (JOLTS)*: [bls.gov](https://www.bls.gov/jlt/) - Congressional Research Service, *"Ghost" Job Postings* (2025): [congress.gov](https://www.congress.gov/crs-product/IF12977) --- # Cover letters in 2026: do they matter, and how to write one Source: https://www.resumecommand.com/resources/job-search/cover-letters-2026 Published: 2026-07-12 Ask around whether cover letters still matter and you will get confident answers that flatly contradict each other. One camp treats them as a dead ritual, the other as a non-negotiable. Both are wrong, because the real answer depends on the role, the company, and your situation. Knowing when a cover letter actually helps, and how to write one that gets read when it does, is worth far more than another generic template. ## Are cover letters dead? Not dead, but no longer automatic. The clearest signal comes from France, where the APEC tracks executive recruitment practices closely: in its 2024 study, only one company in two still asked for a cover letter when hiring a manager. In its place, the phone pre-screen has taken over, now used in 71% of processes, up 13 points since 2019. That short first call does much of what a cover letter used to: it lets a recruiter probe your motivation, your availability, and your fit before committing to a full interview. So the requirement is fading, but the underlying question a cover letter answers has not. Recruiters still want to know why you, why this role, and why now. The format is optional. The signal is not. "Optional" does not mean "ignored." When a cover letter is optional and you send a good one, you stand out from everyone who skipped it. When you send a bad one, you stand out the wrong way. The choice is not send or skip; it is send well or skip cleanly. ## When a cover letter actually moves the needle A cover letter earns its place in specific situations, and is largely wasted in others. **Write one when:** - **You are changing fields or pivoting.** Your resume shows what you did; a cover letter explains why it transfers. This is the single strongest use case. - **You have a gap or an unusual path** to give context to, without over-explaining. A calm sentence beats a suspicious blank. - **The company is small.** A team hiring a handful of people a year reads what you send. A company processing thousands of applicants often cannot. - **The role is outside pure engineering,** where writing and judgment are part of the job and a good letter is itself a work sample. - **You have a specific, genuine reason** for wanting this exact role, not just any role. That is the one thing a resume cannot fully carry. **Skip it when** the application is a high-volume funnel that never surfaces the letter, when the field is blank and truly optional and you have nothing role-specific to add, or when the only version you could produce is a generic restatement of your resume. A skipped cover letter is neutral. A lazy one is a liability. ## What a modern cover letter is for The most common mistake is writing your resume again, in paragraphs. The recruiter already has your resume. A cover letter that just narrates it wastes the one chance you have to say something the resume cannot. Its actual job is to connect three dots the resume leaves unconnected: the specific problem this role exists to solve, the specific thing you have done that maps to it, and the reason you care about this company in particular. Do that in a few tight sentences and you have given a recruiter a reason to read your resume more carefully, which is all a cover letter can realistically do. ## A structure that respects a recruiter's time Keep it under 200 words. Three short paragraphs, no filler. 1. **Open with the role and why it fits, fast.** Skip "I am writing to apply for." Name the role, then say the one thing about it that lines up with your experience. One or two sentences. 2. **Prove it with a single, concrete example.** Pick the one accomplishment that maps most directly to what this job needs, and quantify it. Not a list, one strong proof point. This is where [quantifying your bullet points](/resources/resume-tips/quantify-bullet-points) pays off twice. 3. **Close with genuine interest and an easy next step.** Say why this company, briefly and specifically, then thank them and stop. Write the middle paragraph first, and tie it to the exact language in the job posting. If the posting stresses "rebuilding data pipelines," your proof point should be the time you rebuilt a data pipeline, in those words. That is the same instinct behind [tailoring rather than tweaking](/resources/resume-tips/tailoring-vs-tweaking): match the role's priorities, do not just describe yourself. Here is the shape, filled in: > Dear [Name], the Senior Data Engineer role caught my attention because it centers on rebuilding an ingestion pipeline at scale, which is exactly the problem I spent the last two years on at [Company]. > > There, I rebuilt a batch pipeline that had grown brittle and slow, cutting end-to-end latency by half and cutting on-call incidents to near zero. The description of what your team is trying to fix reads almost like the brief I was handed. > > I am drawn to [Company] specifically because [one concrete, true reason]. I would welcome the chance to talk it through. Thank you for your time. Under a hundred and twenty words, specific, and it adds something the resume does not. ## Mistakes that get you rejected - **Restating the resume in prose.** If a line could be lifted straight off your resume, cut it. - **Being about you instead of them.** "I am seeking a role where I can grow" tells the recruiter nothing about the fit. Lead with their problem. - **Generic openers and "Dear Sir or Madam."** A little research to find a name, or at least the team, signals you actually chose this role. - **Length.** Past one page, or past 250 words, you are testing the reader's patience. - **Typos and the wrong company name.** In a document meant to show care, a careless error is disqualifying. Read it aloud once before sending. ## Should you use AI to write it? Yes, to draft. No, to send raw. AI is genuinely useful for getting past the blank page and structuring your thoughts, and recruiters know candidates use it. The problem is that a cover letter written entirely by a model reads like one: fluent, generic, and about nobody in particular. That is the opposite of the signal you are trying to send. Use AI to shape a first draft from your real notes, then make it specific and make it yours. The parts a model cannot invent, the actual reason you want this role, the one accomplishment that fits, the detail about the company, are exactly the parts that make the letter work. If those are true and specific, it does not matter that a draft started with AI. If they are missing, no amount of polish will hide it. ## The honest takeaway Cover letters are not required as often as they used to be, and that is fine. Treat them as a tool, not a tax. Send one when your situation needs explaining or the role rewards it, skip it cleanly when it would only repeat your resume, and when you do write one, keep it short, specific, and about the employer's problem. A good cover letter will not rescue a weak application, but paired with a resume that already fits, it can be the thing that gets that resume read. Build the habit into a [repeatable job-search routine](/resources/job-search/systematic-job-search) and it costs you very little per application. --- ResumeCommand includes a cover letter generator that drafts from the same job posting and career history it uses to tailor your resume, so the letter and the resume actually agree with each other. Paste a job URL, get a tailored resume and a first-draft letter in under 5 minutes, then make the letter specific before you send it. Try it free → [ResumeCommand](https://www.resumecommand.com) --- ## Sources - APEC, *Pratiques de recrutement de cadres 2024* (May 2024): [apec.fr](https://www.apec.fr/tendances-emploi-cadre/recrutement-et-pratiques-rh/la-fin-annoncee-de-la-lettre-de-motivation-.html) --- # Build a career command center for a systematic job hunt Source: https://www.resumecommand.com/resources/blog/career-command-center Published: 2026-07-08 Most people approach a job search as a chore to endure: apply when a listing catches your eye, cross your fingers, repeat. Yet those same people run complex projects at work with method, dashboards, and regular reviews. The idea of a career command center is simple: bring to your search the same rigor you already bring to your job. Here is how to build one. ## Why treat your search like a project An unstructured job search fails in predictable ways: you lose track of where you applied, you follow up at random, you learn nothing from rejections, and you judge your progress by mood rather than facts. A project, by contrast, has a goal, metrics, tracking, and checkpoints. Nothing stops you from applying that frame to your career, and everything invites it: this may be the most important project you run this year. A command center isn't a sophisticated tool. It's a habit: a single place where all the information lives, and a regular rhythm for reviewing it. A spreadsheet is enough to start. ## The four components of a command center ### 1. Application tracking The heart of the system. One row per application, with at minimum: the company, the role, the date, the status, the channel (direct application, network, referral), and the next planned action. This simple ledger answers the questions that waste your time: where do I stand? who do I need to follow up? which listings are waiting on a reply? It's also what makes following up possible. Most candidates never follow up, for lack of knowing when and whom; an up-to-date tracker turns follow-up into a reflex, a topic we cover in [following up after applying](/resources/job-search/follow-up-after-applying). ### 2. The search pipeline Your search is a funnel: listings spotted, applications sent, interviews landed, offers received. Tracking the volume at each stage tells you where it stalls. Lots of applications but few interviews? The problem is upstream, in targeting or the resume. Lots of interviews but few offers? The problem is in interview preparation. Without those numbers, you're fixing blind. That's exactly the logic of a [systematic job search](/resources/job-search/systematic-job-search), which details how to set weekly targets per stage. ### 3. The material library Gather your reusable building blocks in one place: your master resume, your variants by role type, your cover letters, your prepared answers to interview questions, your structured stories. The goal is to never start from a blank page. Tailoring an application then becomes a quick adaptation, not a rewrite, what we call the difference between [tailoring and tweaking](/resources/resume-tips/tailoring-vs-tweaking). ### 4. The feedback loop This is the component almost everyone forgets, and the most valuable. After each interview, jot down while it's fresh what went well, the questions that caught you off guard, what you'll improve. Group the reasons for rejection when you know them. After ten applications, these notes reveal patterns no single application shows, and that's where your success rate really starts to climb. The classic trap is to measure everything and change nothing. Tracking is useless if it doesn't lead to an adjustment. Every review should end with a decision: what to keep, what to fix, what to test next week. ## A weekly review rhythm The system only lives if you look at it regularly. Block thirty minutes a week for a review: update statuses, schedule follow-ups, examine your funnel numbers, and decide on one concrete adjustment. This meeting with yourself replaces diffuse anxiety ("am I doing enough?") with a factual answer and a plan for the week. That rhythm also protects your energy. A job search is a marathon, and discouragement often comes from the feeling of going in circles. Seeing in black and white that you've moved forward, even modestly, sustains motivation better than any instruction to "stay positive". ## Start small Don't wait for the perfect tool. Open a spreadsheet today, create the columns for application tracking, and fill in the first row with the next listing that interests you. Add the other components over the following weeks. An imperfect but maintained system beats an elegant one you abandon after three days. ## The takeaway A career command center doesn't make the job search pleasant, but it makes it manageable. You stop enduring an opaque process and start running a project whose gears you can see: where you stand, what's working, and what to adjust. The same rigor that makes you good at your job will make you a better candidate. --- ResumeCommand is designed as one piece of that command center: built-in application tracking, your career history kept in one place, and a resume tailored to each listing in minutes. Your material and your tracking, together. Try it free → [ResumeCommand](https://www.resumecommand.com) --- # 25 behavioral interview questions and how to answer each one Source: https://www.resumecommand.com/resources/interview/behavioral-interview-questions Published: 2026-07-08 Behavioral questions all rest on the same premise: the best predictor of your future behavior is your past behavior. Hence the "Tell me about a time when..." phrasing. They don't test what you would do in theory, they test what you actually did. Here are 25 of the most common ones, grouped by theme, with what the interviewer is looking for and how to answer each. Before we dive in, one foundation: structure every answer with the [STAR method](/resources/interview/star-method), Situation, Task, Action, Result. The rest of this article assumes that framework is in place. You don't need 25 stories. Five to seven strong, detail-rich anecdotes cover the large majority of these questions. A single story can often answer three or four different phrasings. ## Collaboration and teamwork **1. Tell me about a time you worked on an effective team.** What's measured: your actual role in a group. Don't describe the team's success as a block, isolate your specific contribution and what made the collaboration work. **2. Describe a time you had to work with someone very different from you.** Show that you adapt your communication without judging. The strong answer emphasizes what the difference added, not the friction it caused. **3. Tell me about a time you helped a struggling colleague.** They're looking for helpfulness without condescension. Describe how you helped without doing the work for them, and what the colleague took away from it. **4. How did you handle a teammate who wasn't pulling their weight?** Avoid trashing them. Show that you spoke to them directly and tactfully before escalating, and that you looked for the cause rather than the culprit. ## Conflict and disagreement **5. Tell me about a disagreement with a colleague.** The question doesn't test whether you were right, but how you handle divergence. Anchor the disagreement in facts, acknowledge the other person's valid point, and land on a shared decision. **6. Describe a time you disagreed with your manager.** This measures your ability to push back upward without insubordination. Show that you made your case with arguments, then backed the final decision once it was made. **7. Tell me about difficult feedback you received.** The key here is maturity. Pick real feedback, not a fake flaw, show that you took it without getting defensive, and above all what you changed afterward. **8. How did you handle an unhappy client or stakeholder?** They want composure and a solution focus. Describe how you listened, reframed the problem, and turned tension into a concrete result. For conflict questions, never pick a story where you're the sole hero and the other person the sole villain. Interviewers distrust stories that are too clean. A touch of self-criticism makes the answer credible. ## Failure, mistakes, and difficulty **9. Tell me about a failure.** The trap is choosing a fake failure. Take a real setback, own your part without flogging yourself, and spend most of the answer on the lesson and what you did differently next. **10. Describe a mistake you made and how you corrected it.** Similar, but centered on the correction. They want to see that you catch your own mistakes, that you flag them instead of hiding them, and that you put a durable safeguard in place. **11. Tell me about the hardest problem you've solved.** Here, show your reasoning method, not just the result. Break the problem down, explain the paths you ruled out and why, then the solution you chose. **12. Tell me about a time you had to learn something very quickly.** This measures your self-directed learning. Describe how you organized to ramp up under time pressure, and the concrete outcome. **13. Tell me about a project that didn't go as planned.** Avoid blaming circumstances. Acknowledge what was within your control, what you'd do differently, and what the project taught you despite the outcome. ## Leadership and initiative **14. Tell me about a time you took initiative without being asked.** They're looking for autonomy and a sense of priorities. Show that you spotted a problem no one was handling, acted, and created measurable value. **15. Describe a time you had to persuade people without formal authority.** The strong answer rests on influence through facts and listening, not force. Show how you aligned other people's interests with your proposal. **16. Tell me about a time you mentored or grew someone.** This measures generosity and teaching. Describe a concrete improvement in the other person, and your specific role in it. **17. How did you carry an unpopular decision?** Show that you can explain the why behind a decision and absorb pushback rather than dodge it. The ideal result: buy-in earned through transparency. **18. Tell me about a time you improved a process.** They want an optimization mindset. Describe the initial inefficiency, the change you introduced, and the quantified gain (time, errors avoided, cost). ## Adaptability and change **19. Describe a time priorities shifted abruptly.** This tests your agility. Show how you re-prioritized calmly, communicated the change, and limited the damage on work already in flight. **20. Tell me about a time you had to work with incomplete information.** This measures your tolerance for ambiguity. Describe how you made a reasoned decision despite uncertainty, making your assumptions explicit. **21. How did you handle an imposed change of organization or tooling?** Avoid the reluctant-holdout posture. Show that you looked for the logic of the change, helped others adapt, and made the most of the new setup. ## Prioritization, pressure, and time management **22. Tell me about a time you had to juggle several priorities at once.** They want your prioritization method, not your ability to do everything. Explain your trade-off criteria and what you consciously pushed back. **23. Describe a high-pressure situation and how you handled it.** Show composure through actions: which concrete decisions reduced the pressure, not just "I stayed calm". **24. Tell me about a time you had to hit a tight deadline.** This measures your ability to deliver. Describe how you broke down the work, negotiated scope if needed, and protected the essentials. **25. How do you decide what to drop when not everything can get done?** The strong answer owns the trade-off. Show that you can say no or "not now" based on impact, and communicate that choice to stakeholders. ## How to prepare efficiently Don't memorize 25 answers by heart. Do the reverse: list five to seven notable experiences from your career, then for each, note which of the questions above it could answer. You'll find that one good production-outage story covers pressure, problem-solving, and sometimes leadership all at once. Prepare the raw material, not the script. The signal that gives away a lack of preparation isn't hesitation, it's the absence of detail. "We managed to pull through" proves nothing. Every answer should contain at least one specific action and a verifiable result. Finally, several of these questions, especially "why this company" and role-specific scenarios, are best prepared with real upfront research. Our guide on [how to research a company before your interview](/resources/interview/research-company-before-interview) gives you the method. ## The takeaway Behavioral questions reward preparation, not brilliant improvisation. Build a small stock of real, detailed stories, structure them in STAR, and practice telling them out loud. On interview day, you're no longer searching for what to say, you're simply choosing which of your stories best answers the question asked. --- Your best answers come from your real accomplishments, the ones already on your resume. ResumeCommand starts from your career history to surface those accomplishments and align them with the target role, giving you the raw material for your interview stories. Try it free → [ResumeCommand](https://www.resumecommand.com) --- # How to research a company before an interview, in 30 minutes Source: https://www.resumecommand.com/resources/interview/research-company-before-interview Published: 2026-07-08 Researching a company before an interview doesn't need to eat your evening. Thirty well-spent minutes are enough to turn vague answers into specific ones, and to prepare the two or three questions that show you're serious. Here is a five-block checklist, each block on a timer. The goal isn't to know everything, it's to find three or four concrete things you can reuse in the interview: a recent piece of news, an industry challenge, a product detail, a fact about the team. Precision beats exhaustiveness. ## Block 1: the product and the model (8 minutes) Start with the most important thing: what the company sells, to whom, and how it makes money. Skim the site, but focus on the product page and the pricing page, often more revealing than the "about" page. If it's a product you can try, try it for five minutes. Nothing impresses an interviewer more than a candidate who has actually used the thing they're applying to help build. Note: the problem the product solves, the target audience, one or two direct competitors, and what sets the company apart. ## Block 2: recent news (6 minutes) Look for news from the last six to twelve months: a funding round, a new product, expansion, a senior hire, an award or acquisition. A news search on the company name usually does it. These items are gold in an interview: they let you tie your motivation to a specific moment in the company's trajectory, rather than to generalities. ## Block 3: health and size (5 minutes) You don't need an audit, just a sense of scale. Is it an early-stage startup, a scale-up, a large group? Roughly how many employees? Is the company hiring actively or in a freeze? The careers page and the company's LinkedIn profile already tell you a lot. This context also shapes your compensation expectations, a topic we cover in our [salary negotiation](/resources/interview/salary-negotiation) guide. ## Block 4: culture and internal signals (6 minutes) The culture on the website is a marketing pitch; look for rawer signals. Read a few reviews from former and current employees with a critical eye (the extremes are often biased, look for recurring patterns). Watch how the company communicates publicly: tone, the values it foregrounds, how it talks about its teams. These signals help you calibrate your approach and spot any red flags. ## Block 5: the people you'll meet (5 minutes) If you know your interviewers' names, glance at their profiles: their role, tenure, background. You're not there to flatter them, but to understand who you're talking to. An interview with the engineering lead calls for different examples than one with an HR recruiter. Also look for a point in common (a technology, a school, an experience) that can create a natural connection. Don't turn this research into an interrogation. Mentioning that you noticed some news or tried the product is excellent; reciting your interviewer's LinkedIn history is unsettling. Use what you know lightly. ## Turning research into questions The best proof that you did your homework is your questions. For each block, prepare one open-ended question: - On the product: "I tried [feature], what's the next big product direction?" - On the news: "After [recent event], what are the team's priorities for the year?" - On the team: "How is the team I'd join structured, and what do the first few months look like?" These questions show you're picturing yourself in the role, and they actually inform you about the job. Many behavioral questions, especially the classic "why us?", are prepared directly from this research. See our list of [behavioral interview questions](/resources/interview/behavioral-interview-questions) to anticipate them. ## The takeaway Thirty structured minutes are enough: the product, the news, the size, the culture, the people. You'll only keep a handful of concrete facts, but well placed in the conversation, they make all the difference between an interchangeable candidate and someone who clearly wants this role, at this company. --- That same research helps you tailor your resume to the role. ResumeCommand extracts a job's key signals from its URL and aligns your resume to them, so your application reflects the company you just studied. Try it free → [ResumeCommand](https://www.resumecommand.com) --- # Salary negotiation: a step-by-step guide for technical roles Source: https://www.resumecommand.com/resources/interview/salary-negotiation Published: 2026-07-08 Salary negotiation makes most candidates uncomfortable, and that discomfort is expensive: you pay for it every month, for as long as you hold the role, and it becomes the base for every future raise. The good news is that negotiation isn't an innate talent. It's a sequence of prepared decisions. Here is the sequence, for a technical role. ## Step 1: know your worth before you talk about it You can't negotiate a number you don't have. Before any interview, establish a realistic range for the role, based on your experience, your stack, company size, and location. Cross-reference several sources rather than one, and separate base salary from total package (bonus, equity, benefits). That research is part of preparing for the interview overall. Our guide on [how to research a company before your interview](/resources/interview/research-company-before-interview) covers how to triangulate this information, including on compensation and the employer's financial health. Prepare three numbers, not one: your floor (below it, you walk), your target (realistic and ambitious), and an anchor number slightly above target, which you state first. Negotiating without those three markers is improvising. ## Step 2: handle the "what are your expectations" question The "what are your salary expectations?" question often comes early, sometimes on the first phone screen. You have three options: - **Deflect it.** "What range have you budgeted for this role?" Polite, legitimate, and it makes you speak second. - **Give a range.** If you have to name a number, state a range whose bottom is your target, not your floor. People rarely negotiate toward the top of your range. - **Defer.** "I'd like to understand the scope of the role better before talking numbers, but I'm within market for this kind of position." Useful very early in the process. What not to do: give your current salary as if it sets the ceiling. Your current pay isn't the basis for the new one; the value of the role is. ## Step 3: let the offer come to you Don't negotiate before you have an offer. Until the company has decided it wants you, you have no leverage. Your negotiating power peaks right after the offer and before you sign. That's the one window where the company has invested in the process, chosen to hire you, and hasn't yet locked the number. So don't rush to say yes. Thank them, show enthusiasm, and ask for a reasonable window to consider it. "Thank you so much, I'm really excited about the role. Can I come back to you within two days?" That simple pause is already a negotiating position. ## Step 4: respond to the first offer The first offer is rarely the best the company can do. Responding with a reasoned counter is expected, not rude. The formula that works rests on three elements: enthusiasm, a specific number, a justification. > "I'm excited about the role and confident I can have an early impact on [specific area]. Based on my experience in [key skill] and market rates for this level, I was targeting closer to [target number]. Can we get there?" Notice what makes this work: it's warm, it's specific, and it's justified by your value, not your personal needs. "I have a mortgage" is not a negotiating argument; "I bring exactly the stack you need" is. Never name a number you're not prepared to accept. If you say "I'm looking for 60" and they offer 60, you can't back away without looking unreliable. Your first number should be your anchor, not your floor. ## Step 5: negotiate beyond base salary If the company can't move on base, the package offers other levers, sometimes easier to get: signing bonus, variable pay, remote days, a training or conference budget, equipment, extra time off, an early review date. For a technical role, a learning budget or a six-month review clause can be worth more over time than a small bump on base. Raise these one at a time, not in a burst. A list of ten asks feels like haggling; two or three targeted asks read as a discussion. ## Step 6: close it cleanly Once you have a verbal agreement, get it in writing before you resign your current role. That isn't distrust, it's normal practice. Check that base, variable, start date, and the negotiated items all appear in the written offer. And whatever the outcome, stay gracious. You're going to work with these people, often with a future manager who championed your case internally. A well-run negotiation builds respect; an aggressive one leaves a mark. ## The mistakes that cost the most - **Not negotiating at all.** Accepting the first offer out of discomfort is the most expensive choice over time. - **Negotiating with no number in hand.** Without a prepared range, you cave to the first round figure. - **Justifying with needs instead of value.** Rent and kids aren't arguments; skills and impact are. - **Negotiating too early.** Before the offer you have no leverage. After you sign, you have none left. ## The takeaway Salary negotiation is mostly won in preparation. Know your range, let the offer come, respond with a justified anchor number, and widen the discussion beyond base if needed. It isn't a confrontation: it's a professional conversation where you calmly, and on the facts, stand up for what your work is worth. --- A strong negotiation starts with a strong case. ResumeCommand works from your real career history to surface the skills and accomplishments that justify your range, the very ones you'll point to when it's time to negotiate. Try it free → [ResumeCommand](https://www.resumecommand.com) --- # The STAR method, with real software engineering examples Source: https://www.resumecommand.com/resources/interview/star-method Published: 2026-07-08 In a behavioral interview, the question almost always starts with "Tell me about a time when...". What the interviewer wants is not an opinion, it's evidence: a real, structured story that shows what you did and what came of it. The STAR method is the simplest tool for delivering that evidence without rambling. Here is how it works, and what it looks like on real engineering problems. ## What STAR stands for STAR breaks an answer into four beats: - **Situation**: the context, in a sentence or two. Where, when, what was at stake. - **Task**: your specific responsibility in that situation. Not the team's, yours. - **Action**: what *you* did, step by step. This is the heart of the answer. - **Result**: what changed because of your action, ideally measurable. The proportion matters as much as the four letters: keep Situation and Task short, spend most of your time on the Action, and always land on a clear Result. Most failed answers collapse because the candidate spends two minutes setting the scene and ten seconds on what they actually accomplished. Say "I", not "we". A technical interview hires a person, not a team. If your whole story is in the "we" voice, the interviewer can't tell what *you* contributed. ## A full example: a production incident Take the classic question: "Tell me about a time you handled a critical outage." **Situation.** "Last year our payments service started returning 500 errors on roughly 30% of transactions, late on a Friday afternoon, during a high-traffic window." **Task.** "I was the on-call engineer. My job was to restore service as fast as possible, then understand the root cause so it wouldn't happen again." **Action.** "I started with the dashboards and correlated the error spike with a deploy that had gone out twenty minutes earlier. Rather than hunt for a fix under pressure, I rolled back to the previous version, which stopped the errors within a few minutes. Once the service was stable, I reproduced the bug in staging and found that a database migration had locked a table under load. I rewrote the migration to run in batches, added an alert on lock duration, and documented the incident in a post-mortem I shared with the team." **Result.** "Total downtime was held to about eight minutes instead of the hour a hotfix would have taken. The post-mortem led to a team rule: any migration touching a critical table now ships as a batched deploy. We haven't seen that class of incident since." Notice the shape: two sentences of context, one sentence of responsibility, a dense paragraph of concrete actions, and a result that is both quantified and durable. That is exactly what an interviewer can write down and remember. ## A second example: a technical disagreement Behavioral questions aren't only about technical fires. "Tell me about a disagreement with a colleague" tests how you collaborate. **Situation.** "We had to choose between rewriting a legacy service and refactoring it incrementally. A senior colleague argued for a full rewrite, I argued for incremental refactoring." **Task.** "As the owner of that module, I had to make the call, but I wanted a shared decision, not an imposed one." **Action.** "I proposed scoring both options against the same criteria: regression risk, timeline, and one-year maintenance cost. I put together a short comparison doc, and we reviewed it together. On the numbers, the rewrite doubled the timeline for an uncertain payoff. I acknowledged the valid points in his argument about technical debt and proposed a compromise: incremental refactoring, with a targeted rewrite of the one component that was genuinely beyond saving." **Result.** "We shipped in six weeks instead of the three months estimated for the rewrite, with no major incidents. My colleague reused that comparison framework for his own technical decisions afterward." Here the Result isn't just a number: it shows the disagreement was settled on facts and left the relationship intact. That is often what the question is really measuring. ## The mistakes that weaken a STAR answer The most common weakness isn't missing structure, it's a missing result. A story with no quantified or concrete ending leaves the interviewer with no evidence of your impact. A few recurring traps: - **Staying vague on the Action.** "I coordinated with the teams" says nothing. What exactly did you do? Which decisions, which code, which trade-off? - **Picking a story that's too small.** A bug fixed in five minutes proves nothing. Choose a situation with real stakes. - **Forgetting the "I".** See above: "we" dilutes your contribution. - **Not preparing the result.** If you have no number, find a concrete effect: a deadline met, a process adopted, an incident that never recurred. ## How to prepare your stories in advance Don't improvise in the room. Prepare five to seven strong stories from your history, each structured in STAR, covering different themes: a technical win, a failure you learned from, a conflict, a project delivered under constraint, a moment of initiative. Most behavioral questions are variations on those themes, and one good story can often answer several phrasings. These stories already live in your resume. The accomplishments you [quantified in your bullet points](/resources/resume-tips/quantify-bullet-points) are exactly the results that close a STAR answer: the same number that makes a bullet credible makes your spoken story credible. And to cover the range of likely questions, work from our list of [behavioral interview questions](/resources/interview/behavioral-interview-questions). ## The takeaway STAR is not a magic formula, it's a discipline: forcing every anecdote to carry short context, a clear responsibility, concrete actions, and a verifiable result. Prepare your stories, say "I", and always land on what changed. A structured answer impresses not because it's smooth, but because it hands the interviewer evidence they can note and defend after you leave the room. --- Before the interview, there's the resume that gets you into the room. ResumeCommand starts from your real career history, surfaces the quantified accomplishments most relevant to the role, and helps you build the raw material for your future STAR answers. Try it free → [ResumeCommand](https://www.resumecommand.com) --- # Following up after applying: timing and templates that work Source: https://www.resumecommand.com/resources/job-search/follow-up-after-applying Published: 2026-07-05 Following up is one of the highest-leverage, lowest-effort moves in a job search, and almost nobody does it well. Most candidates send an application into the void and wait. The few who do follow up usually pick the wrong moment or write the wrong message, and it lands as noise. Done right, a follow-up is a short, respectful nudge that reminds a busy recruiter you exist at the exact moment they are deciding who to shortlist. ## Why following up works A recruiter is often juggling many open roles at once, and any single posting can draw far more applicants than one person can personally reply to. Your application is not being ignored on purpose; it is sitting in a queue behind dozens of others. A brief, well-timed follow-up does two things: it moves your name back to the top of the pile, and it signals genuine interest in *this* role rather than a mass-apply spray. That second signal matters more than people think, because interest is one of the few things a resume alone cannot fully convey. A follow-up is not about being pushy. It is about being visible at the right moment. The recruiter is busy, not hostile. Assume good faith and make it easy for them to act. ## The timing Timing is where most follow-ups go wrong. Too soon reads as anxious; too late and the shortlist is already set. ### After applying: wait about a week Give it five to seven business days after you submit. That is long enough for the posting to be actively reviewed, and early enough that the shortlist is usually not finalized. Following up the next morning signals impatience; following up after three weeks means the decision has often already been made without you. ### After an interview: two touches Send a short thank-you note within 24 hours of any interview. This is not the follow-up; it is basic courtesy, and its absence gets noticed. The actual follow-up comes later: if the recruiter gave you a timeline ("we will decide by Friday"), wait until a day or two past it before checking in. If they gave you no timeline, about a week of silence is a reasonable trigger. Always ask, at the end of an interview, what the next steps and timeline are. It gives you the exact date your follow-up becomes appropriate, so you never have to guess. ## What a good follow-up says A follow-up should be short, specific, and add something rather than just ask "any update?" Reaffirm your interest, add one concrete detail that reinforces your fit, and make the reply effortless. **After applying, no response:** > Subject: Senior Data Engineer application, [Your Name] > > Hi [Name], I applied for the Senior Data Engineer role on [date] and wanted to reaffirm how interested I am. The part of the job description about rebuilding the ingestion pipeline lines up closely with the work I did at [Company], where I cut pipeline latency by half. Happy to share anything that would help. Thank you for your time. **After an interview, past the timeline:** > Subject: Following up, [Role] conversation > > Hi [Name], thank you again for the conversation last [day]. I know you mentioned deciding by [date], so I wanted to check in and reaffirm my interest. The discussion about [specific topic] made me even more confident I would be a strong fit. Please let me know if there is anything else useful from my side. Notice what both do: they name a specific detail, they stay under a hundred words, and they close with an easy out. No guilt, no urgency, no third and fourth message. ## What not to do - **Do not follow up daily.** Two or three touches total, spaced out, then move on. Persistence past that point works against you. - **Do not send a bare status request.** "Just checking on my application" gives the recruiter nothing to respond to and no reason to prioritize you. - **Do not follow up on every channel at once.** Pick one. Email is safest. A polite LinkedIn message can work if you do not also have an email, but do not do both simultaneously. - **Do not let a follow-up carry a weak application.** The nudge gets your resume re-read; it does not fix a resume that does not fit. Make sure the underlying document is [tailored and ATS-clean](/resources/job-search/linkedin-vs-resume) before you draw attention back to it. ## The honest takeaway Following up will not rescue a bad fit, and it will not force a "yes." What it does is make sure a strong application is actually seen, and that your interest is on record when the shortlist is drawn. Wait about a week after applying, send a thank-you within a day of any interview, follow up once more past the stated timeline, and keep every message short and specific. That is the whole system. It costs you ten minutes and puts you ahead of the large majority of candidates who never do it at all. Build it into a repeatable routine and it compounds, which is the core idea behind running [a systematic job search](/resources/job-search/systematic-job-search). --- ResumeCommand includes an application tracker, so you always know which roles you applied to, when, and which ones are due for a follow-up. Paste a job URL, get a tailored resume in under 5 minutes, and keep the whole pipeline in one place instead of a spreadsheet. Try it free → [ResumeCommand](https://www.resumecommand.com) --- # Hidden job market: what is real and how to reach roles early Source: https://www.resumecommand.com/resources/job-search/hidden-job-market Published: 2026-07-05 You have seen the pitch: "70 to 80% of jobs are never advertised | they're filled through the hidden job market before you ever see them." It gets repeated everywhere, usually right before someone sells you a networking course. The number is invented. But the instinct underneath it | that who you know changes your odds | is backed by some of the best labor-market research we have. The useful version of "the hidden job market" is not about secret listings at all. It's about which relationships actually move you into a role. ## The "80% hidden" number is fabricated Start with the honest part: there is no credible study behind the claim that 70, 80, or even 60% of jobs are never posted. When people have tried to trace it, the citation trail loops through articles quoting articles quoting a "study" that turns out not to exist, eventually landing on decades-old career writing from the era of newspaper classifieds | when "advertised" meant something completely different from a searchable global job board. Today the pressure runs the other way. Companies face hiring accountability, post to comply with pay-transparency laws, and want maximum applicant volume, so real openings almost always get posted somewhere. A secret vault of unlisted jobs is not a real thing. Be skeptical of any advice that leads with "80% of jobs are hidden." It's a marketing hook, not a statistic. The evidence-based version of this idea is narrower and far more actionable | so let's use that instead. ## It's not secrecy | it's who opens the door The role was posted. You could have found it and applied. What changes your outcome is *how you arrive*. Applications that come with a referral convert at a completely different rate: Ashby's analysis of more than 38 million applications (2021 to 2024) found that referrals are barely 1% of all application volume, yet 40% of referred candidates advance from application to interview | a rate cold applicants come nowhere near. So this isn't about access to secret jobs. It's about entering *public* jobs through a much higher-converting door. That reframes the whole task: you're not hunting for hidden listings, you're trying to reach the right person before you become application #51. (For how to budget your week across referrals, outreach, and cold applications as a system, see [building a systematic job search](/resources/job-search/systematic-job-search) | this article is about the relationship half specifically.) ## The science of weak ties: acquaintances beat close friends Here is the counterintuitive part, and it's unusually well-evidenced. In 2022, researchers from MIT, Harvard, Stanford, and LinkedIn published a study in *Science* that ran randomized experiments on LinkedIn's "People You May Know" feature across more than 20 million users over five years, a period in which about 600,000 people changed jobs through new connections. It is the largest causal test of networking and jobs ever run | not a survey, an actual experiment. The finding overturns the intuition that you should lean on your closest contacts. **Weaker ties drove more job mobility than strong ones** | but not without limit. The relationship is an inverted U. Your inner circle helps less than you'd expect, and total strangers help little either. The sweet spot is *moderately weak* ties: roughly the acquaintances you share about ten mutual connections with and rarely speak to. The effect was even stronger for jobs in digital and tech-heavy industries. The mechanism is information overlap. Your close friends mostly know the same people, companies, and openings you already know | their network is a copy of yours. A colleague from two jobs ago sits in a *different* network, sees roles you can't see, and can vouch for you into a room you'd never find on a job board. That, and not secrecy, is the real engine behind "the hidden job market": reach, not concealment. The people most likely to change your job search are not your five closest contacts. They're the couple of dozen former colleagues, past managers, and loose acquaintances you haven't spoken to in a year or two. That's exactly the group most job seekers never think to contact. ## Who to reach, and how The weak-ties finding turns networking from a vague "put yourself out there" into a specific, short list of moves. ### Reactivate dormant ties first Make a list of former colleagues, past managers, and people you worked *near* but not with | from previous roles, not your current daily team. These dormant, moderately-weak ties are precisely the ones the *Science* data says matter most, and reaching out costs you almost nothing. A short, specific message reopens the tie without asking for a favor upfront: > "Hi Sara | I'm exploring senior data roles and saw your team is scaling its platform work. Could we grab 15 minutes? Would love to hear how things are going there." No ask for a referral yet | just a reconnection. The referral, if it fits, comes naturally later. ### Make a referral effortless to give A referral is a small reputational risk for the person giving it, so lower that risk to near zero. When you do ask, include the exact role link, two or three sentences on why you fit, and a ready-to-forward blurb they can paste without editing. You're not asking them to sell you | you're asking them to forward something you've already made frictionless. The best referral ask is one the other person can act on in under a minute: the job URL, a one-line reason you're a fit, and a short summary they can forward as-is. The less work it is, the more often the answer is "sure." ### Follow target companies before they post Roles aren't hidden, but they are often *early*. Growth signals | a funding round, a new office, a senior hire, a product launch | reliably precede hiring. Following 15 to 20 target companies and a few key people at each means you frequently catch the signal weeks before the listing, giving you time to line up a warm intro instead of arriving in the day-one applicant pile. ## When the intro works, your resume still has to A warm referral gets your resume *read by a human, sooner*. It does not read the resume for them. Once you're through the door, the same fundamentals decide what happens next: does the document mirror the role's actual language, is it cleanly parseable, and does it lead with outcomes a hiring manager can verify? Hand your referrer a resume that's already doing its job | start with [ATS optimization](/resources/resume-tips/ats-optimization-2026) and [quantifying your bullet points](/resources/resume-tips/quantify-bullet-points). ## The honest takeaway The hidden job market, as usually sold, is a myth: jobs aren't locked in a vault, and no one has a credible "80% unadvertised" number. What's real is quieter and more useful. The public listing you can already see converts far better when you arrive referred | and the people most likely to open that door aren't your inner circle, but the acquaintances just outside it. Not a secret market. A better way into the open one. --- Once a warm intro points you at a specific role, ResumeCommand turns it around fast: paste the job URL and get a tailored, ATS-optimized resume built from your own career history in under 5 minutes, with a match score that tells you how well you fit before you send it to your contact. The intro is yours to earn | the tailoring is handled. Try it free → [ResumeCommand](https://www.resumecommand.com) --- ## Sources - Rajkumar, Saint-Jacques, et al., *A causal test of the strength of weak ties*, **Science** (2022) | randomized experiments across 20M+ LinkedIn users, ~600,000 job transitions: [science.org](https://www.science.org/doi/10.1126/science.abl4476) · summary via [MIT Sloan](https://mitsloan.mit.edu/press/a-team-mit-harvard-and-stanford-scientists-finds-weaker-ties-are-more-beneficial-job-seekers-linkedin) - Ashby, *Talent Trends Report: Referrals* (data from 38M+ applications across 93,000 jobs, 2021–2024) | [ashbyhq.com](https://www.ashbyhq.com/talent-trends-report/reports/referrals) --- # LinkedIn profile vs resume: what recruiters look at first Source: https://www.resumecommand.com/resources/job-search/linkedin-vs-resume Published: 2026-07-05 Most people treat their LinkedIn profile as a copy of their resume with a headshot on top. That is the mistake. The two documents are read by the same recruiters, often within minutes of each other, but they do two completely different jobs. One is built to be found. The other is built to win a single specific role. Optimize each for what it actually does, and you stop competing against yourself. ## The two documents have two different jobs A resume is a targeted argument. It exists to answer one question for one opening: why are you a strong fit for *this* role? It is narrow by design, tailored to the job description, and read once by someone who has already decided to consider you. A LinkedIn profile is a standing advertisement. It is not aimed at one job; it is aimed at every recruiter who might search for someone like you next month. It has to be broad enough to surface in searches you will never see, and complete enough to reassure a recruiter who found you cold. Different audience, different moment, different job. The resume is pull: you send it toward a role you chose. The profile is push: it works while you sleep, surfacing you for roles you never applied to. Writing one as a clone of the other wastes both. ## What a recruiter looks at first depends on how they found you There is no universal order. The order is set by how you entered their pipeline. ### If you applied, the resume goes first When you submit an application, your resume is the primary document. It gets a fast, structured skim before anything else. The 2018 Ladders eye-tracking study clocked the average initial resume screen at just 7.4 seconds, and found recruiters lock onto job titles more than any other element, scanning the left side of the page in an F-shaped pattern. LinkedIn comes second here, as a verification and personality check after the resume has earned it. ### If they sourced you, LinkedIn goes first When a recruiter is hunting for candidates rather than reading a stack of applications, your LinkedIn profile is the entire first impression. There is no resume yet. They found you through a search, they judge you on your headline, your current role, and your recent activity, and only then do they reach out and ask for a resume. Here the profile is the door, and the resume is what happens after you are already through it. This is why the "first" in the question is a trick. For active applications, the resume is first. For passive sourcing, the profile is first. You need both to hold up, because you rarely control which path a given recruiter takes. ## The resume: written for one role Because the resume answers one job description, it should be ruthlessly specific. Mirror the language of the posting, lead with the outcomes that matter for *that* role, and cut anything that does not serve the argument. This is the document where [tailoring](/resources/resume-tips/tailoring-vs-tweaking) pays off, where [quantified bullet points](/resources/resume-tips/quantify-bullet-points) do the heavy lifting, and where clean, [ATS-parseable structure](/resources/resume-tips/ats-optimization-2026) decides whether a human ever reads you at all. A good resume is not comprehensive. It is edited. Everything that does not push toward this specific role is noise. ## The LinkedIn profile: written to be found The profile plays the opposite game. Its first job is to appear in searches, so it needs the breadth your resume deliberately cuts: the full range of skills, tools, and titles a recruiter might type into a search bar. Recruiters search by keyword, so your headline and your "About" and "Experience" sections should carry the terms for the roles you want next, not just the one you hold now. - **Headline:** not just your job title. Say what you do and the value you bring, using searchable terms. - **About:** written to a stranger who found you cold, not to a hiring committee that already knows the role. - **Experience:** the same real accomplishments as your resume, but broader, because you are not tailoring to one posting. - **Openness:** a recruiter deciding whether to spend an outreach message wants signals you might move. Quick test for your headline: would it surface you if a recruiter searched the exact words for your next role, not your current one? If the keywords for the job you want are missing, the search never reaches you. ## Where most candidates get it backwards The common failure runs in both directions. People write a LinkedIn profile as narrow as a tailored resume, stripped down to their current title, and then wonder why recruiters never find them. Or they write a resume as broad as a LinkedIn profile, a comprehensive career dump that answers no specific job description, and wonder why applications go nowhere. Flip it. The resume should be narrow and tailored to the role in front of you. The profile should be broad and built to be discovered. When you catch yourself copy-pasting one into the other, that is the signal you are optimizing the wrong document for the wrong moment. If reaching people before roles are even posted is your goal, the profile is doing most of that work; see [the hidden job market](/resources/job-search/hidden-job-market) for how the two connect. ## The consistency test Different jobs does not mean different facts. A recruiter who reads your resume and then opens your LinkedIn, or the reverse, is quietly checking that the two agree. Same titles, same companies, same dates, same story. Contradictions read as carelessness at best and dishonesty at worst, and they surface exactly when a recruiter is deciding whether to trust you. So: same facts, different framing. The profile casts a wide net; the resume makes a focused case. Neither should ever contradict the other on anything a background check could verify. ## The honest takeaway Stop maintaining one document twice. Your LinkedIn profile is a searchable advertisement that has to be broad enough to get you found for roles you have not seen yet. Your resume is a targeted argument that has to be narrow enough to win the one role in front of you. Keep the facts identical, keep the framing distinct, and let each do the job it is actually there to do. Most candidates get this backwards. Getting it right costs you an afternoon and quietly changes how often the right people reach you. --- Once a role is in front of you, whether you found it or it found you, ResumeCommand turns your broad career history into a tight, tailored resume fast: paste the job URL and get an ATS-optimized draft in under 5 minutes, with a match score that tells you how well you fit before you send it. Your profile brings them to you; the tailoring is handled. Try it free → [ResumeCommand](https://www.resumecommand.com) --- ## Sources - Ladders, *Eye-Tracking Study* (2018): the average initial resume screen lasts 7.4 seconds, and recruiters spend more time on job titles than on any other element, scanning in an F-shaped pattern. Reported by [HR Dive](https://www.hrdive.com/news/eye-tracking-study-shows-recruiters-look-at-resumes-for-7-seconds/541582/) --- # How to build a systematic job search (with weekly templates) Source: https://www.resumecommand.com/resources/job-search/systematic-job-search Published: 2026-07-01 Most job searches are run on vibes. You see a posting, feel a spike of motivation, fire off an application, and wait. A few days later the spike fades, you apply to three more in a slump, and two weeks in you have no idea how many roles you've contacted, which ones replied, or whether anything you're doing is working. That's not a strategy | it's a coping mechanism. A better model already exists, and you probably use it at work: the sales funnel. Treat your job search like a pipeline with defined stages, weekly targets, and a feedback loop, and the whole thing stops feeling like luck. This guide gives you the system and the templates to run it. ## Why "apply to everything" fails The instinct to spray applications comes from a real observation: hiring is a numbers game. What people miss is that the conversion rate is wildly different depending on *how* you enter the funnel. Look at the data from platforms that see the whole pipeline. Ashby's Talent Trends Report, built on more than 38 million applications across 93,000 jobs between 2021 and 2024, found that referral applications are barely 1% of the total volume | yet 40% of referred candidates make it from application to interview. Inbound applicants (the "apply online" crowd) convert at a small fraction of that rate. Pinpoint's analysis of 4.5 million applications reached the same conclusion from a different angle: referred candidates are roughly 7x more likely to be hired than candidates who apply through job boards. So "apply to 50 jobs" isn't wrong because volume is bad. It's wrong because it pours all your volume into the lowest-converting channel. A systematic search fixes that by measuring where your effort goes and steering it toward the stages that actually move. The funnel model doesn't mean applying less. It means knowing your numbers well enough to spend each hour where it converts | and noticing within a week, not a month, when something isn't working. ## The four stages of your funnel Every job search, whether you've named the stages or not, has four: 1. **Sourcing** | roles you've identified and qualified as worth pursuing. 2. **Applications** | roles you've formally applied to (with a tailored resume, ideally). 3. **Conversations** | any two-way contact: recruiter screen, hiring-manager call, referral chat, interview. 4. **Offers** | the end of the funnel. The point of naming them is that you can now count what's in each one, and watch how many move from one stage to the next. A search that feels "stuck" is almost always leaking at a specific stage | and until you've drawn the funnel, you can't see which. | Stage | What it contains | The question it answers | |---|---|---| | Sourcing | Qualified target roles | Am I finding enough good-fit roles? | | Applications | Submitted, tailored applications | Am I actually applying, or just browsing? | | Conversations | Screens, calls, interviews | Is my resume converting to human contact? | | Offers | Written offers | Am I closing? | ## Set weekly targets for each stage Targets turn the funnel from a rear-view mirror into a steering wheel. Set them per week, because a week is short enough to correct course and long enough to smooth out the randomness of who happens to reply. Reasonable starting targets for a full-time search (scale down by half if you're searching while employed): - **10–15 qualified roles sourced.** Not 50 skimmed listings | 10–15 you'd genuinely take. - **8–12 tailored applications.** Quality over volume: a resume matched to the posting converts far better than a generic one blasted everywhere. - **3–5 outreach touches.** Referral asks, recruiter messages, or reconnecting with someone at a target company. - **2–4 conversations.** This one you influence but don't fully control | it's the output you're optimising for. Don't treat these as quotas to hit mindlessly. Treat them as a hypothesis. If you consistently blow past your sourcing target but never hit your conversation target, the funnel is telling you exactly where to dig. Track applications *tailored*, not applications *sent*. Ten applications where your resume mirrors the job's actual language will out-convert forty copy-paste submissions | and take less total time once you have a system for tailoring. See our guide on [tailoring vs. tweaking](/resources/resume-tips/tailoring-vs-tweaking) for how much each role deserves. ## Your weekly operating rhythm Random effort produces random results. Batching similar work into fixed blocks does two things: it kills the context-switching tax, and it makes the search sustainable for the eight-plus weeks it often takes. Here's a template rhythm | adapt the days, keep the structure. | Day | Focus | Time | What you do | |---|---|---|---| | Monday | Sourcing | 60–90 min | Scan boards, company pages, and your network. Add qualified roles to the tracker. Set the week's targets. | | Tuesday | Applications | 90–120 min | Tailor and submit. Work the batch you sourced Monday while fit is fresh. | | Wednesday | Outreach | 45–60 min | Referral asks, recruiter messages, alumni pings. Follow up on last week's applications. | | Thursday | Applications + prep | 90 min | Second application batch. Prep for any scheduled conversations. | | Friday | Review | 30–45 min | Update the tracker, run the weekly review (below), diagnose leaks, set next week's targets. | Two rules make this hold up: - **Protect the blocks.** A recruiter reply can pull you into reactive mode all day. Answer it, schedule it, then return to the plan. The plan is what keeps volume steady through the weeks when nothing is replying. - **Separate sourcing from applying.** Doing both at once is how you end up applying to whatever's in front of you instead of what fits. Source in one block, judge fit, *then* apply in another. ## What to track You don't need software. A single spreadsheet with one row per role does the job. What matters is capturing the fields that let you diagnose the funnel later: | Field | Why it's there | |---|---| | Company / Role | The basics | | Source | Board, referral, recruiter, or direct, so you can compare channel conversion | | Date applied | To measure follow-up timing and response lag | | Match score / fit | Your honest read on how well you fit, which later correlates with what converts | | Stage | Sourced / Applied / Conversation / Offer / Rejected | | Last contact + next action | So nothing falls through the cracks | | Notes | Names, referral threads, interview feedback | The single most valuable column is **Source**, because it's what tells you your referral applications convert 5–10x better than your cold ones | which is the insight that should reshape where you spend next week's hours. A tracker you don't update is worse than none | it gives false confidence. Update it in the Friday review block, every week, even the weeks you'd rather not look. The whole system depends on honest numbers. ## Feedback loops: reading your own funnel This is the part that separates a system from a spreadsheet. Every Friday, look at where candidates drop and let the pattern point you at the fix. **Lots of applications, almost no conversations.** Your resume isn't converting to human contact. The problem is upstream of your search behaviour | it's the document. Are you matching the posting's actual language? Is it getting parsed cleanly? Start with [ATS optimisation](/resources/resume-tips/ats-optimization-2026) and [quantifying your bullet points](/resources/resume-tips/quantify-bullet-points), which is where most resumes leak. **Plenty of conversations, no offers.** The resume is doing its job; the interview isn't. Effort should shift from applying to interview prep | structured answers, company research, negotiation. **Can't even hit your sourcing target.** You're either too narrow or looking in the wrong places. Widen titles, add adjacent roles, and lean harder on the [hidden job market](/resources/job-search/hidden-job-market) | referrals and dormant contacts reliably out-convert cold applications. **Everything's moving but slowly.** That's often normal. Searches routinely run two-plus months; the fix isn't panic, it's consistency. Keep the volume steady and let the pipeline fill. The discipline here is to change *one* thing per week and watch its effect the next. Change five things at once and you'll never know which one worked. ## The weekly review template Fifteen minutes every Friday. Answer six questions: 1. **Did I hit each target?** Sourced / applied / outreach / conversations vs. plan. 2. **Where did candidates drop this week?** Name the leaking stage. 3. **What does my best-converting source look like?** Referral vs. board vs. direct. 4. **What one experiment am I running next week?** New resume angle, a different channel, more outreach. 5. **What's overdue?** Follow-ups, thank-you notes, dormant applications needing a nudge. 6. **Next week's targets.** Adjusted based on the above. Write the answers down in the same sheet. Over a month you'll have a paper trail of what actually moved your funnel | which is more than most job seekers ever get. ## Channel mix: stop spending 100% on job boards If the data says anything, it's this: the channel most people spend all their time on is the one that converts worst. Job boards are easy | that's exactly why they're crowded and low-yield. The higher-converting channels take more effort per touch, which is why so few people do them, which is why they convert. A healthier weekly mix: - **~50% applications** through boards and company pages | still your volume base. - **~30% warm outreach** | referral asks, recruiters, people at target companies. This is the channel the data says pays off, and it's where most searches under-invest. - **~20% relationship-building** | alumni, past colleagues, communities. It rarely converts *this* week, which is precisely why to start it early. You don't have to choose between volume and relationships. You have to *budget* between them | which is the entire point of running your search as a system instead of a scramble. --- Running a search this way means a lot of small, repeated tasks: tailoring each resume to the posting, logging every application, tracking what's converting. ResumeCommand handles the repetitive half of the funnel | paste a job URL and get a tailored, ATS-optimised resume in under 5 minutes, with a match score that tells you how well you fit before you apply, and a built-in application tracker so your funnel stays honest without a separate spreadsheet. Try it free → [ResumeCommand](https://www.resumecommand.com) --- ## Sources - Ashby, *Talent Trends Report: Referrals* (data from 38M+ applications across 93,000 jobs, 2021–2024) | [ashbyhq.com](https://www.ashbyhq.com/talent-trends-report/reports/referrals) - Pinpoint, *Referrals are 7x more likely to be hired than job board candidates* (analysis of 4.5M applications, 2023) | [pinpointhq.com](https://www.pinpointhq.com/insights/referrals-are-7x-more-likely-to-be-hired-than-job-board-candidates/) --- # AI in hiring: what the 2026 data says about resume screening Source: https://www.resumecommand.com/resources/blog/ai-in-hiring-2026 Published: 2026-06-28 There is a lot of noise about AI in hiring, and most of it lands in one of two camps: panic ("a robot rejects you in milliseconds") or denial ("recruiters still read everything"). The truth is more specific, and the 2026 data is finally good enough to talk about it honestly. Here is what the research actually shows, and what it means for how you write your resume. ## How widely AI is actually used Start with the layer underneath the AI: the applicant tracking system. An ATS is the database every application flows into. According to RecruitCRM's 2025 survey, around 93% of recruiters use one, and ATS use is standard across large organisations. If you have applied for a job in the last few years, your resume has almost certainly lived inside an ATS. The AI layer on top of that is newer and growing fast, but the headline numbers depend heavily on how each survey defines "AI". SHRM's 2025 Talent Trends research found AI use across HR roughly doubled in a year (from 26% to 43% of organisations), and that among organisations using AI in HR, about 44% apply it to screening resumes. Other 2026 reports put adoption higher (HireVue's 2026 report found 77% of HR teams use AI regularly), which tells you the category is real but the precise figure depends entirely on definition. Two different things get blurred together: an **ATS** (storage and keyword search, almost everywhere) and **AI screening or ranking** (automated scoring, common but not universal). Design for both, but don't assume a sentient gatekeeper is reading every line. ## What AI screening actually does to your resume When AI is involved, it usually does one of two jobs: parsing and ranking. **Parsing** turns your PDF or DOCX into structured fields (name, roles, dates, skills). This is where most silent failures happen, not because you were "rejected" but because the system mangled your text and a keyword search missed you. **Ranking** scores or sorts candidates against the job description, and this is where automation gets consequential. In some pipelines, candidates are filtered out at the first pass before a person ever sees their name. The Stanford research below documents exactly this kind of automated, systemic rejection at scale. So the panic camp is not entirely wrong: software can filter you out before a human reads your resume. But the volume framing matters. For most applicants the bigger day-to-day risk is not a dramatic AI rejection, it is a quiet parsing miss that drops you from a keyword search. ## The bias problem the data keeps surfacing This is the part of the AI-in-hiring story with the strongest evidence, and it is not flattering. The largest study to date came out of Stanford's Institute for Human-Centered AI in 2025. Researchers analysed 3.4 million people submitting roughly 4 million applications to 1,700 postings across 150 employers, all screened by a single third-party AI tool. They found that 26% of Black applicants and 15% of Asian applicants applied to roles where the system discriminated against their group, and that about 10% of applicants who submitted four applications were rejected from every one, a "systemic rejection" rate higher than independent decisions would predict. A separate study from University of Washington researchers found that AI resume-screening tools favoured white-associated names in the large majority of cases (around 85%). Different method, same direction. Bias in screening tools is not your fault and you can't fully engineer around it. But the practical takeaway is clear: don't hand an opaque system extra reasons to misread you. Clean, literal, well-structured information is your best defence. ## The paradox: everyone uses AI, nobody trusts it Here is where 2026 gets genuinely strange. Both sides of the table now use AI, and almost nobody trusts the result. On the candidate side, HireVue's 2026 Global AI in Hiring report found that 71% of candidates already use AI to help write their resumes. On the employer side, 77% of HR teams use AI regularly, yet only 41% fully trust the tools. And candidates remain wary of the whole arrangement: a Pew Research Center survey found that 66% of Americans would not want to apply for a job with an employer that uses AI to help make hiring decisions. That gap creates conflicting signals for applicants. Recruiters increasingly say they can spot fully AI-written applications, so a resume that reads as machine-generated can trigger skepticism from the human even as the screening software rewards keyword coverage. The resolution is not "never use AI". It is to use AI for leverage, not for ghostwriting: let it find gaps, surface relevant experience, and structure information, while the substance stays yours and verifiable. ## What this means for how you write your resume None of the above changes the fundamentals as much as it sharpens them. Five things matter more in an AI-screened pipeline, not less: ### 1. Use the employer's exact terms Ranking and search both reward literal matches. If the posting says "Kubernetes" and you wrote "container orchestration", a keyword filter misses you. Mirror the job's terminology where it is genuinely true of your experience. Our [ATS optimisation guide](/resources/resume-tips/ats-optimization-2026) covers the mechanics in depth. ### 2. Keep the structure boringly parseable Standard section headers (Work Experience, Education, Skills), single-column layout when the employer's stack is unknown, consistent date formats, and a real text-layer PDF exported from a document editor. Fancy layouts are where parsing breaks. ### 3. Lead with verifiable outcomes Both AI ranking and human reviewers weight specifics. Numbers you can defend in an interview beat adjectives. See our framework on [quantifying bullet points](/resources/resume-tips/quantify-bullet-points) for how to do this even when you don't have clean metrics. ### 4. Tailor per role, but don't over-rewrite A resume aimed at the specific posting will out-rank a generic one. That does not mean a full rewrite for every application. Match the effort to the opportunity, as we argue in [tailoring vs. tweaking](/resources/resume-tips/tailoring-vs-tweaking). ### 5. Keep it human-readable Assume a skeptical person reads it after the software passes it through. If it reads like a keyword dump, the screen may like it and the recruiter won't. Run the 30-second test before you submit: paste your resume into a plain-text editor. If the structure survives and your top five target keywords are present and readable, you are in good shape for both the machine and the human. ## The honest takeaway AI in hiring in 2026 is real, widely deployed, and demonstrably imperfect. It is not an all-knowing gatekeeper, and it is not a myth you can ignore. It is a layer that rewards clarity and literal matching, occasionally rejects people unfairly, and sits in front of a human who is increasingly wary of content that looks machine-made. You can't control the screener. You can control how cleanly your real experience is presented to it. That is where the leverage is. --- ResumeCommand is built for exactly this layer. You paste a job URL and it extracts the role's key signals, scores how well your resume matches, and flags the keyword and structure gaps an ATS would trip on, working from your own career history rather than rewriting it from scratch. AI for leverage, with the substance still yours. Try it free → [ResumeCommand](https://www.resumecommand.com) --- ## Sources - Stanford Institute for Human-Centered AI (HAI), *AI Hiring Tools Can Yield Racial Bias and Systemic Rejection* (2025): [hai.stanford.edu](https://hai.stanford.edu/news/ai-hiring-tools-can-yield-racial-bias-and-systemic-rejection) - SHRM, *2025 Talent Trends: AI in HR*: [shrm.org](https://www.shrm.org/topics-tools/research/2025-talent-trends/ai-in-hr) - HireVue, *2026 Global AI in Hiring Report*: [hirevue.com](https://www.hirevue.com/resources/report/2026-global-ai-in-hiring-report) - Pew Research Center, *AI in Hiring and Evaluating Workers: What Americans Think* (2023): [pewresearch.org](https://www.pewresearch.org/internet/2023/04/20/ai-in-hiring-and-evaluating-workers-what-americans-think/) - University of Washington, *AI tools show biases in ranking job applicants' names according to perceived race and gender* (2024): [washington.edu](https://www.washington.edu/news/2024/10/31/ai-bias-resume-screening-race-gender/) - RecruitCRM, *Applicant Tracking System Statistics* (2025): [recruitcrm.io](https://recruitcrm.io/blogs/applicant-tracking-system-statistics/) --- # Skills-first resumes: writing for skills-based hiring Source: https://www.resumecommand.com/resources/resume-tips/skills-first-resumes Published: 2026-06-28 "Skills-first hiring" is the headline talent trend of the last few years: hire for what someone can do, not the title they held or the degree they hold. It is a genuinely good idea, and the data backing the upside is strong. It is also, according to the best research available, something employers talk about far more than they actually practice. Both of those facts matter for how you write your resume. ## What "skills-first" actually means A skills-first process evaluates candidates on demonstrated competencies and evidence, rather than using job titles and credentials as the first filter. In practice it shows up in two places that affect you directly: how recruiters search their database (by skill keywords rather than by previous title), and how some employers have rewritten job postings to drop or soften degree requirements. The implication for a resume is simple to state and easy to get wrong: your skills need to be legible, specific, and evidenced, not buried inside a job title or assumed from your degree. ## The case for it is real Part of why skills-first thinking took hold is that skills themselves are moving targets. The World Economic Forum's Future of Jobs Report 2025, drawing on over 1,000 employers across 55 economies, found that employers expect 39% of workers' core skills to change by 2030, down from 44% in 2023. When the useful life of a skill set keeps shrinking, what you can do now is a sharper signal than the title you held five years ago. When hiring genuinely shifts from titles to skills, the candidate pool also changes shape in measurable ways. LinkedIn's Skills-First research found that talent pools expand on average nearly 10x when employers search by skills instead of job titles. The same analysis found a skills-first approach increases the proportion of women in candidate pools by 24% more than it does for men, and increases pools of workers without bachelor's degrees by 9% more than those with degrees. For Gen Z candidates, the pools grow more than 10x. In other words, when a recruiter searches by skill, far more people become visible, including people whose previous job title would never have matched the search. If your skills are explicit and well-worded, you are one of the people who becomes visible. If they are implied, you are not. ## But employers say it more than they do it Here is the honest counterweight, and it is the part most "skills-first" advice leaves out. A Harvard Business School and Burning Glass Institute study led by Joseph Fuller, looking at more than 11,000 US job postings from 2014 to 2023, found that the real-world impact of dropping degree requirements was tiny. After firms removed the requirement, hiring of workers without a bachelor's degree rose by just 3.5 percentage points, and once you adjust for the limited scope of the change, by less than one. Their estimate of the net effect: fewer than 1 in 700 hires actually benefited. Don't read "skills-first" as "credentials no longer matter". For most employers the change is still mostly rhetoric. Plan for a reader who claims to hire on skills but quietly still scans for familiar titles and degrees. So the situation a job seeker faces is genuinely mixed: keyword and skills-based search is real and growing, while the deeper cultural shift away from titles and degrees is slow and uneven. The good news is that the resume move that wins in a true skills-first process is the same one that protects you in a traditional one. Making your skills legible costs you nothing with an old-school reviewer, and gains you a lot with a modern one. ## What this means for your resume ### 1. Make skills explicit, not implied Don't rely on a reader inferring "SQL" or "stakeholder management" from a job title. State the skill, then back it. A grouped, scannable skills section helps both keyword search and the human skim: > **Data:** Python (pandas, scikit-learn), SQL, dbt > **Cloud:** AWS, Docker, Terraform > **Leadership:** mentoring, cross-functional delivery Group by type and only list what you can defend in an interview. A focused set of credible skills beats a long flat list, which reads as keyword stuffing. We break this down in [the five resume mistakes that get you filtered out](/resources/resume-tips/five-resume-mistakes). ### 2. Prove the skill in context A skills section tells a reader you have the keyword. Your experience bullets prove you can use it. Pair them: if "experimentation" is in your skills list, a bullet should show an experiment you ran and what it changed. > Cut onboarding drop-off 18% by running a 4-week A/B test on the activation flow That is the difference between claiming a skill and evidencing it. Our [guide to quantifying bullet points](/resources/resume-tips/quantify-bullet-points) gives a framework that works even when you don't have clean numbers. ### 3. Mirror the posting's skill language Skills-based search matches on specific terms. If the role asks for "Kubernetes" and you wrote "container orchestration", a skill search misses you. Use the employer's exact terminology wherever it is genuinely true of your experience. The mechanics are covered in our [ATS optimisation guide](/resources/resume-tips/ats-optimization-2026). ### 4. Keep credentials, but frame them as evidence Since most employers have not really moved off degrees, don't strip them out. Reframe them as proof of skill rather than as the headline: a certification listed next to the skill it validates does more work than a standalone credentials section. Before you submit, read your resume as a recruiter running a skill search. Pick the five skills most central to the role. Are all five stated explicitly *and* evidenced in a bullet? If a skill only appears as an adjective, it won't survive the search. ## The honest takeaway Skills-first hiring is real where it counts for your resume (search and matching) and mostly aspirational where it would help you most (degree and title bias). You can't control which kind of employer you're facing. You can control whether your skills are explicit, specific, evidenced, and worded the way the role describes them. That is the rare resume change that has no downside: it makes you findable in a modern process and credible in a traditional one. --- ResumeCommand works from your real career history and the specific job posting: it surfaces the skills the role is asking for, flags the ones you have but haven't made explicit, and checks that they actually appear in your resume. Skills-first, without inventing anything you can't back up. Try it free → [ResumeCommand](https://www.resumecommand.com) --- ## Sources - World Economic Forum, *Future of Jobs Report 2025* (survey of 1,000+ employers across 55 economies): [weforum.org](https://www.weforum.org/publications/the-future-of-jobs-report-2025/in-full/3-skills-outlook/) - LinkedIn Economic Graph, *Skills-First: Reimagining the Labor Market and Breaking Down Barriers*: [economicgraph.linkedin.com](https://economicgraph.linkedin.com/research/skills-first-report) - Harvard Business School (Joseph Fuller) and The Burning Glass Institute, *Skills-Based Hiring: The Long Road from Pronouncements to Practice* (2024, data 2014–2023): [hbs.edu](https://www.hbs.edu/bigs/joseph-fuller-college-degree-gap) · [burningglassinstitute.org](https://www.burningglassinstitute.org/research/skills-based-hiring-2024) --- # The 5 resume mistakes that get you filtered out in seconds Source: https://www.resumecommand.com/resources/resume-tips/five-resume-mistakes Published: 2026-06-03 Eye-tracking studies of recruiter behaviour consistently show the same thing: the first pass takes 6–10 seconds. In that window, a recruiter forms an impression — continue reading or move on — based on a handful of visual signals. Most resumes fail not because of weak experience but because of avoidable presentation mistakes that hit in the first 6 seconds. Here are the five that appear most often. ## 1. No clear job title at the top Recruiters scan for role continuity. When they open your resume, the first question they're answering is: *is this person one of us?* The fastest way to answer that is a clear, current job title directly under your name. If your resume starts with a generic objective statement ("Motivated professional seeking a challenging opportunity..."), the recruiter has to read further to understand what you do. Most won't. **Fix:** Replace the objective statement with your current or target title — one line, directly under your name. `Senior Product Manager` or `Data Engineer (ML Infrastructure)` tells the story in under a second. If you're changing careers, use the target title but ground it immediately: *"Software Engineer — transitioning from 4 years in QA automation."* One line, no ambiguity. ## 2. Bullets that describe tasks, not outcomes The most common resume mistake, by volume. Recruiters know what a Marketing Manager does — they read 50 of these a week. What they're looking for is what *you* achieved in that role, specifically. **Weak:** > Managed social media accounts across three platforms **Strong:** > Grew organic Instagram following from 12k to 48k in 8 months by introducing a weekly video series; reduced paid spend by 30% while maintaining lead volume The difference is not complexity — it's outcome. What changed because you were there? If you genuinely don't have metrics for a role, use qualitative outcomes: "reduced manual QA time by eliminating a redundant test suite", "first hire to introduce code review standards adopted by the full team". Specific beats vague every time. See the [full guide on quantifying bullet points](/resources/resume-tips/quantify-bullet-points) for a framework that works even when you don't have numbers. ## 3. A skills section that's a keyword dump A long flat list of tools and technologies looks like you're trying to pass keyword filtering. Recruiters see it for what it is. More importantly, if you list 40 skills with no structure, the ones that actually matter — the ones that match the role — get lost. **Weak:** > Python, SQL, Tableau, Excel, PowerPoint, Jira, Confluence, Slack, Notion, Google Analytics, Salesforce, HubSpot, Figma, Miro, Trello, Asana... **Strong:** > **Analytics:** Python (pandas, scikit-learn), SQL, dbt, Tableau > **Platforms:** Salesforce, HubSpot > **Tools:** Jira, Notion Group by type. Cut anything you can't speak to confidently in an interview. A skills section with 8 credible entries is more trustworthy than one with 35 questionable ones. Don't list tools you used once or briefly. If it comes up in the interview and you struggle, it damages your credibility more than if you hadn't listed it at all. ## 4. Dense blocks of text in experience bullets Even a great bullet loses impact if it takes more than two lines to read. In the first 6-second pass, a recruiter isn't reading — they're scanning. Walls of text signal effort to read, and effort to read means skipping. **Fix:** Keep each bullet to one or two lines maximum. If the impact takes more than that to explain, break it into two bullets. Lead with the outcome, follow with the method: > Cut customer onboarding time by 40% — redesigned the activation flow based on 3 months of session recordings and exit survey data One line. Outcome first. Context second. ## 5. Inconsistent or amateur formatting Formatting mistakes signal carelessness, which is the last impression you want to make. The most common ones: - **Mixed date formats** — `Jan 2023` in one role, `01/2024` in another - **Inconsistent bullet punctuation** — some bullets end with periods, others don't - **Multiple font sizes or weights** that weren't intentional design choices - **Margin creep** — shrinking margins to squeeze content onto one page makes the document feel cramped and hard to read None of these affect your qualifications. All of them affect how you're perceived. Formatting signals how you approach detail work — and for most roles, that matters. **Fix:** One final pass focused exclusively on consistency. Don't read the content — look at the structure. Check dates, punctuation, spacing, and alignment as a separate review step. --- ## The pattern behind all five Each of these mistakes has the same root cause: the resume was written for the author, not the reader. When you write your own resume, you know your context, your story, and your outcomes. The recruiter has none of that. Every sentence needs to work standalone, in 6 seconds, with zero prior context. Read your resume as if you've never heard of yourself. That's the standard it needs to meet. --- ResumeCommand analyses your resume against each job posting and flags gaps in keyword coverage, outcome-focused language, and structure — before you submit. No more second-guessing. Try it free → [ResumeCommand](https://www.resumecommand.com) --- # How to quantify your resume bullet points (with 30 examples) Source: https://www.resumecommand.com/resources/resume-tips/quantify-bullet-points Published: 2026-05-20 Numbers are the single biggest upgrade you can make to a resume. Recruiters scan fast — a bullet that starts with a metric stops the eye before the sentence even registers. This guide covers the formulas, the common objections ("I don't have exact numbers"), and 30 ready-to-steal examples across different job types. ## Why numbers work A bullet without a number forces the recruiter to trust you. A bullet with a number forces them to think. Thinking means engagement. Engagement means your resume gets read rather than discarded. Compare: - *Managed a team and improved delivery speed* - *Led a 6-person team, cutting average delivery time from 3 weeks to 8 days* The second version answers the questions every recruiter has in the back of their head: *How big was the team? How much faster? How do I know this person actually moved the needle?* ## The four number types Not every impact is measured the same way. There are four categories that cover almost every role: **1. Volume** — how much you handled *Processed 300+ customer tickets per month, maintaining a 98% satisfaction score* **2. Growth** — percentage increases or decreases you drove *Grew organic search traffic by 140% in 9 months through a structured content calendar* **3. Scale** — the size of what you worked with (budget, users, revenue) *Managed a €1.2M marketing budget across four channels* **4. Speed** — how much faster or more efficiently something happened *Reduced onboarding time from 14 days to 4 days by automating the welcome sequence* Pick the number type that makes your impact look **biggest and clearest**. Sometimes volume is more impressive than percentage; sometimes the reverse. Use whichever is honest and more striking. ## The "I don't have exact data" problem Most people didn't track their numbers obsessively. That's normal. Here's what you do: **Use ranges.** "Handled roughly 50–80 inbound leads per week" is more credible than a suspiciously round "100 leads per week." **Estimate from what you know.** If your team closed €2M in revenue and you were one of four reps with similar performance, it's reasonable to write "contributed to ~€500K in closed revenue." **Use proxies.** If your change reduced time in a meeting from 60 minutes to 20 minutes and that meeting happened weekly, that's 40 minutes × 52 weeks = ~34 hours saved per year, per attendee. **Cite the observable.** If you can't measure the outcome, measure the input: "Authored 3 technical RFCs adopted by a team of 18 engineers." Never fabricate numbers. Interviewers verify. A single challenged metric destroys your credibility for the entire interview. ## The formula Almost every strong bullet follows the same structure: > **[Action verb] + [what you did] + [metric] + [context if needed]** Examples following this formula: - *Rebuilt the checkout flow → reduced cart abandonment by 22% → over a 3-month A/B test* - *Trained 40 new support agents → cutting average handle time by 35%* - *Migrated legacy monolith to microservices → enabling the team to deploy 4× more frequently* ## 30 quantified bullet examples by role ### Sales & business development - Generated €380K in new ARR over Q3 and Q4, finishing 118% of quota - Sourced and closed 14 enterprise accounts with an average deal size of €27K - Reduced average sales cycle from 42 days to 28 days by introducing a structured discovery call template ### Marketing & content - Grew email list from 4,200 to 31,000 subscribers in 11 months through gated content campaigns - Increased landing page conversion rate from 2.1% to 5.8% through iterative copy and layout tests - Produced 24 long-form articles per quarter that generated an average of 6,400 organic sessions each ### Engineering & product - Reduced API response time from 420ms to 95ms by refactoring the data-access layer and adding Redis caching - Decreased CI pipeline duration from 18 minutes to 4 minutes, saving ~120 engineer-hours per week - Led migration of 3 million user records to a new schema with zero data loss and under 4 hours of planned downtime ### Operations & project management - Managed rollout of a new ERP system across 6 offices, delivered 3 weeks ahead of schedule and 8% under budget - Reduced vendor costs by €340K annually by renegotiating 12 supplier contracts - Improved on-time delivery rate from 71% to 94% by redesigning the fulfilment workflow ### Customer success & support - Maintained a 96% CSAT score across a portfolio of 120 enterprise accounts - Reduced average first-response time from 6 hours to 45 minutes by implementing a triage playbook - Onboarded 80 new clients in Q2 with a 91-day retention rate of 98% ### Finance & analysis - Built a cash-flow model that identified a €1.8M working capital shortfall 4 months before it materialised - Automated 11 weekly reporting processes, saving the finance team 22 hours per week - Reduced accounts-receivable days outstanding from 47 to 31 by implementing automated payment reminders ### HR & people operations - Reduced time-to-hire from 52 days to 28 days by streamlining the interview process from 6 stages to 4 - Improved employee NPS from 31 to 64 over 18 months through a structured manager-training programme - Designed a retention initiative that reduced voluntary attrition from 24% to 14% year-over-year ### Design & UX - Redesigned the mobile checkout flow; usability testing showed a 40% reduction in task-completion time - Produced 120 production-ready screens for a product launch delivered on a 6-week timeline - Increased design system adoption from 30% to 85% of components across 4 product teams ## Common mistakes to avoid **Stacking too many numbers in one bullet.** One metric per bullet is usually enough. Two is sometimes fine. Three makes the reader do arithmetic. **Picking vanity metrics.** "Got 10,000 impressions" is weak because impressions are cheap. Revenue, retention, conversion, and time-to-X are almost always more credible. **Forgetting the verb.** Metrics without action verbs make bullets passive. *"A 40% improvement in conversion"* is weaker than *"Lifted conversion 40% by…"* **Using the same verb for every bullet.** Rotate between: led, built, reduced, grew, designed, launched, automated, negotiated, trained, shipped. --- ## How ResumeCommand helps When you paste a job description into ResumeCommand, it analyses which skills and outcomes the employer is signalling. The AI then matches those signals against your career history and rewrites your bullets to emphasise the metrics most relevant to *that specific role* — so the right numbers are front and centre before a recruiter even starts reading. Try it free → [ResumeCommand](https://www.resumecommand.com) --- # Tailoring vs. tweaking: knowing when each approach wins Source: https://www.resumecommand.com/resources/resume-tips/tailoring-vs-tweaking Published: 2026-05-12 Tailoring your resume for every application sounds like the right advice — and it is, in principle. In practice, a full rewrite for every role is unsustainable, and it's often unnecessary. The skill is knowing which jobs deserve deep work and which ones just need a light pass. ## The difference between tailoring and tweaking **Tailoring** means restructuring. You reorder bullets to lead with the most relevant experience, swap in the employer's exact terminology, and reframe your role descriptions to speak directly to the job's priorities. It takes 20–40 minutes done properly. **Tweaking** means adjusting. You update the professional summary, add one or two keywords that are missing, and make sure the skills section reflects the job's language. It takes 5–10 minutes. Both are legitimate. The question is which the application warrants. ## When to tailor fully ### The role is a strong match but not an obvious one If your experience maps to the role but through a non-obvious path — you're coming from an adjacent industry, or your title doesn't match despite the work being equivalent — tailoring is what makes that connection visible to a recruiter doing a 6-second scan. Without tailoring, a recruiter sees a title mismatch and moves on. With tailoring, they see the right keywords in the right positions and read further. ### Seniority is at the edge of the range If the role says "5–8 years of experience" and you have 4 or 9, tailoring can close the gap. At 4 years, you surface the scope and ownership of your work more prominently. At 9, you trim strategic-level detail that might read as overqualified. A tweaked resume doesn't move the needle here. A tailored one can. ### Competition is high Roles at well-known companies, remote-first roles, and roles in currently crowded markets (tech, fintech, consulting) get hundreds of applications. At that volume, recruiters rely more heavily on keyword filtering and structured review — which means the difference between a tailored and a tweaked resume is the difference between an interview and a pass. Check the LinkedIn "applicants" count before deciding how much effort to invest. Under 50 applicants: tweak. Over 200: tailor properly. ### You really want the role This sounds obvious, but it's worth saying explicitly. If you're applying to a dream company or a role that would genuinely change your trajectory, the 30 minutes of tailoring is not optional. This is not the place to reuse a version from two applications ago. ## When tweaking is enough ### Your title and experience match closely If you're a Senior Product Manager applying for Senior Product Manager roles at companies of similar scale, the heavy structural work is probably done. A recruiter sees your title and immediately understands the fit. Your job is to make sure the language matches theirs — not rebuild from scratch. ### You're applying at volume to a broad category If you're doing a wide search across many similar roles — say, 20 SDR positions at different SaaS companies — a strong base resume, tweaked per application, is a reasonable strategy. Tailoring all 20 would take your full week. Tweaking 20 takes a few hours. The tradeoff: slightly lower conversion rate per application, higher total volume. For a broad job search in the early stages, that's often the right call. ### You're testing the market If you're not actively looking but want to see what's out there, a tweaked resume is appropriate. Don't spend 40 minutes tailoring a role you're only 60% interested in. The risk with always tweaking: it's easy to convince yourself a tweak is enough when the role actually requires tailoring. Be honest about the match before you decide. ## A simple decision framework Ask yourself three questions before you start: 1. **Is my title and seniority an obvious match?** If no → tailor. 2. **Are there more than 100 applicants, or is this a competitive employer?** If yes → tailor. 3. **Do I genuinely want this role?** If yes → tailor. If all three answers lean toward tweaking, tweak. If any one of them leans toward tailoring, tailor. ## What to do first either way Whether you're tailoring or tweaking, always start with the job description. Read it fully — not just the headline and first paragraph. Note the specific terms they use for skills, tools, and responsibilities. That language should appear somewhere in your resume, verbatim where possible. For a full tailoring guide, see [how ATS systems read your resume](/resources/resume-tips/ats-optimization-2026) — it explains exactly which signals matter most and why matching terminology is so effective. --- ResumeCommand handles the decision automatically. Paste the job URL and it surfaces a match score before you start editing — so you know immediately whether you need a light pass or a proper tailoring session. Try it free → [ResumeCommand](https://www.resumecommand.com) --- # ATS optimisation in 2026: what actually matters Source: https://www.resumecommand.com/resources/resume-tips/ats-optimization-2026 Published: 2026-04-08 Applicant Tracking Systems (ATS) have a reputation as black boxes that eat resumes and spit out rejections. Most of what you read about them is either a decade out of date or based on speculation. This guide separates the myths from what modern ATS platforms actually do in 2026. ## What an ATS actually does An ATS is fundamentally a database with a search interface. Recruiters post a job, candidates apply, and the ATS stores every application. When a recruiter wants to review candidates, they either scroll through the list or use a search bar to filter by keyword, location, or status. **Parsing** is the first step: the ATS reads your PDF or DOCX, extracts text, and stores it in structured fields — name, email, work history, education, skills. This is where most resume "fails" happen — not because the system rejected you, but because it mangled your text and the recruiter's keyword search missed you. **Ranking** is the second step, and only some ATS platforms do it. Systems like Workday, Greenhouse, and Lever focus on storage and workflow. Others, like iCIMS and Eightfold, apply ML-based matching to score candidates automatically. The advice differs slightly depending on which type you're up against — but the foundations are the same. You rarely know which ATS a company uses. Design for all of them: clean parsing first, keyword density second. ## The myths **Myth: You need to stuff keywords to beat the ATS.** Keyword stuffing was a real hack circa 2012. Modern ATS platforms penalise it, and even if they don't, the recruiter who reads your resume will. Focus on natural, relevant language. **Myth: Graphics and tables break all ATS systems.** Some older systems can't parse multi-column layouts. Most modern systems (Greenhouse, Lever, Workday) handle them fine. The safer rule: if you're applying via a small company with an unknown stack, use single-column. If you're applying via a major platform with known ATS, you have more flexibility. **Myth: The one-page rule.** Length matters much less to an ATS than it does to a human. The ATS doesn't care if your resume is 1 page or 3. Recruiters at large companies who process hundreds of applications per week do care — brevity signals self-awareness. For roles with under 10 years of experience, one page. For senior and executive roles, two pages is fine. **Myth: PDF = bad for ATS.** PDFs generated from Word or Google Docs are machine-readable and parsed reliably by all major ATS platforms. The exception: scanned PDFs (images of paper resumes) — these are not searchable and will fail parsing. Always export from a proper document editor, never scan. ## What actually matters in 2026 ### 1. Exact keyword matching Job descriptions contain specific terms. If the job says "Python" and your resume says "scripting languages", a keyword search for Python will miss you. Use the exact terms from the job description. That doesn't mean copying the JD verbatim — it means using the terminology the employer uses: - "Account executive" vs "sales representative" - "Product roadmap" vs "feature planning" - "CI/CD pipeline" vs "continuous integration" Paste the job description and your resume into a word-frequency tool. Any high-frequency term from the JD that's missing from your resume is a gap worth filling — if it's genuinely true of your experience. ### 2. Clean, parseable structure The ATS reads your resume top to bottom, left to right. Help it by using standard section headers: - **Work Experience** (not "Career Journey" or "My Story") - **Education** (not "Academic Background") - **Skills** (not "Superpowers" or "Toolkit") Avoid headers in text boxes, tables, or sidebars — they often parse as body text or get dropped entirely. Use consistent date formatting: `Jan 2023 – Mar 2025` or `01/2023 – 03/2025`. Don't mix styles. ### 3. File quality Export as a text-layer PDF from your editor. Check it by opening the PDF and trying to copy-paste a sentence — if the text is selectable and readable, you're in good shape. If it isn't, regenerate. If the employer's portal accepts DOCX, consider submitting both: DOCX for maximum parsability, PDF as a backup if you can attach an additional file. ## Section-by-section checklist **Contact information** - Full name at the top, not in the header area of a Word document template (headers often get dropped) - Professional email — no `cooldude1987@` addresses - LinkedIn URL (shortened: `linkedin.com/in/yourname`) - Location: City, Country is enough. Full street address is outdated and a privacy risk **Work experience** - Reverse chronological order (most recent first) - Company name, your title, dates, and location for each role - 3–6 bullet points per role, starting with action verbs - Metrics in at least half your bullets (see our [guide on quantifying bullet points](/resources/resume-tips/quantify-bullet-points)) **Skills section** - List technologies, tools, and methodologies explicitly — don't embed them only in bullet points - Group by type: *Languages: Python, SQL, JavaScript | Tools: dbt, Airflow, Tableau* - Avoid proficiency bars — they're subjective, not parseable, and trained recruiters ignore them **Education** - Degree, institution, graduation year - GPA only if above 3.5 and you graduated in the last 3 years - Relevant coursework or thesis only if directly relevant to the role ## How modern ML ranking works ATS platforms with ML ranking (Eightfold, Beamery, some Workday/SAP configurations) go beyond keyword matching. They: - Parse semantic meaning, so "reduced churn" and "improved retention" may score similarly - Weight recency (your last 2 roles matter more than roles from 10 years ago) - Score title matching separately from skills matching - May factor in trajectory — a series of promotions is a positive signal The practical implication: tailor your resume to every job, but don't obsess over synonyms at the expense of clarity. ## The 30-second test Before submitting any application, do this: 1. Copy your entire resume text and paste it into a plain text editor (Notepad, TextEdit in plain text mode) 2. Read through it. Does the structure hold up? Can you parse your own work history quickly? 3. Ctrl+F your top 5 target keywords from the job description. Are they all present? If the answer to all three is yes, your resume is ATS-ready. --- ResumeCommand runs this analysis automatically. When you paste a job URL, it extracts the key signals and highlights gaps between the JD and your current resume before you even start editing. Try it free → [ResumeCommand](https://www.resumecommand.com)