Resume & ATS Glossary

Software that employers use to manage job applications, candidate profiles, and hiring workflows. Resume parsing, search, and automated screening features depend on the product and employer configuration.

Uploading a resume, extracting its fields, and deciding whether to advance an application are different steps. For example, Greenhouse application rules can tag, advance, or reject candidates based on configured answers to application questions. That is not a universal resume score or a Pika diagnostic result.

The process of extracting structured fields, such as name, email, work experience, education, and skills, from a resume into a candidate profile. Successful upload does not guarantee complete or accurate parsing.

Parsing can miss fields or put information in the wrong place; it is not evidence of automatic rejection. Greenhouse documents that a failed parse leaves the resume attached to the candidate and requires manual field entry. Where the application lets you review imported details, correct them before submitting.

An ATS score is a tool-specific diagnostic, usually presented on a 0-100 scale. Some tools compare a resume with a job description; Pika's free ATS resume checker evaluates resume-wide parsing, structure, content, keyword, and file-quality risks using Pika's own rubric.

There’s no universal “ATS score” - tools and employer screening configurations can differ. A Pika score does not reveal an employer’s criteria. Treat the score as a direction under that tool’s own rubric, not as a guaranteed result.

Examples of applicant tracking platforms include Workday, Greenhouse, Lever, Taleo, and iCIMS. This list is illustrative, not a market-share ranking or evidence that they parse and screen resumes identically.

Follow the specific vacancy’s file requirements and check any imported application fields. A Pika ATS diagnostic identifies risks under Pika’s own rubric; it is not a live test inside each of these employer platforms.

A 3-5 line block at the top of your resume that tells the reader who you are professionally. Best version: a specific role label, a quantified scale of impact, and one differentiator. (“Senior Software Engineer with 8 years scaling consumer products from 0 to 1M+ users; specialised in mobile performance.”)

A summary is the section recruiters read first when they scan for 6 seconds, and the one ChatGPT pulls when you ask “what does this candidate do?”

A 1-2 line statement of what kind of role you’re seeking. Increasingly considered outdated for experienced candidates - the role you want should be obvious from the JD you’re applying to - but still useful for entry-level resumes, career changers, and applicants whose target role isn’t obvious from their work history.

See our 50+ career objective examples if you need a starting point.

A single bold line at the top of your resume - usually below your name - that names the role you do or want. “Senior Backend Engineer · Distributed Systems · ex-Stripe”.

Headlines are optional but high-signal; recruiters use them to immediately classify which role bucket you belong in.

A 1-page document accompanying your resume that explains, in narrative form, why this role specifically and what you’d bring. Cover letters are required for ~30% of applications today (down from ~70% a decade ago), most often at non-tech employers, government roles, and senior positions.

When required, write one specifically for that application - generic cover letters underperform no cover letter at all.

Any period longer than ~3 months between formal jobs. Whether to explain a gap is contextual: short gaps (under 6 months) usually need no explanation; longer gaps (caregiving, education, illness, sabbatical, entrepreneurship) are best addressed in one neutral line on the resume itself or in the cover letter.

ATS systems don’t penalise gaps; some recruiters do, but transparent gap explanations consistently outperform hidden ones.

The verb that opens a resume bullet point: Built, Shipped, Led, Negotiated, Reduced, Scaled. Strong action verbs describe what you did, not what your team did or what your role nominally included.

“Responsible for” is the canonical weak opener; “Led” is the canonical strong one for the same scope.

A single line inside a work-experience entry describing one thing you did and the outcome. Format that consistently works: [Action verb] + [what you did] + [quantified outcome].

Example: “Reduced p99 API latency from 800ms to 90ms by introducing a Redis caching layer; improved checkout conversion by 4%.”

A resume bullet that includes a number: a percentage, a dollar amount, a count, a duration, a rank. Resumes with quantified achievements consistently outperform those without - recruiters anchor on numbers because they’re easier to compare across candidates.

“Improved page load time” → “Reduced page load time by 47% (from 4.1s to 2.2s) across 12M monthly users.”

A framework for structuring achievement bullets and interview answers: Situation, Task, Action, Result.

On resumes, a compressed STAR - “In a fragmented onboarding flow [Situation], led a 2-month redesign [Action] that cut drop-off by 31% [Result]” - makes for the strongest single-line bullets.

Vague, over-used terms that occupy space without conveying signal: synergize, ninja, rockstar, results-driven, detail-oriented, proven track record, team player. Recruiters skip them; ATS systems don’t weight them.

Replace every buzzword with a specific outcome. “Results-driven sales manager” → “Sales manager who grew Mid-Market ARR 3.4x in 18 months.”

The default resume format: most recent job first, then backwards in time. Used by ~90% of candidates because it’s what ATS parsers expect and what recruiters scan for.

If you’re not sure which format to pick, pick this.

A resume organised by skill categories instead of by job. Designed to hide gaps or major career changes by foregrounding skills and pushing job history to a single line at the bottom.

Honest about its purpose, but recruiters know what it’s hiding the moment they see the format - most consider functional resumes a red flag. We don’t recommend it for most candidates.

A blend of reverse-chronological (job-by-job timeline) and functional (skill grouping). Used most effectively by career changers who want to emphasize transferable skills without hiding their actual work history.

Hybrid resumes work when designed deliberately; they fail when they look like the candidate couldn’t decide what to write.

A resume layout intended to reduce common text-extraction and reading-order risks through clear sections, text-based content, and contact details in the main body. ATS-friendly does not mean certified for every employer system or guaranteed to pass screening.

Start with Pika’s ATS-friendly template gallery, then inspect the exported file rather than relying on the template label. Selectable text and a sensible copy-and-paste order are useful checks, not proof that every parser will interpret the file correctly.

A resume layout that runs content from top to bottom in one column without sidebars. It reduces reading-order complexity but does not guarantee accurate parsing or a hiring outcome.

Columns and tables can create extraction problems in some parsers. For a practical first check, copy the exported text into a plain-text editor and verify that job titles, employers, dates, and bullets stay in order. This is an editorial self-check, not an employer-platform certification.

Repeating document areas at the top and bottom of a page. Contact details placed there can be missed by some resume parsers; putting essential details in the main body reduces that risk.

A prominent heading in the normal document body is not the same as a document header region. Keep your name, email, and phone as visible text in the main body, then verify those fields if the application auto-fills a candidate profile.

A resume saved in Portable Document Format. Use PDF only when the application accepts it, and follow any explicit DOCX or other file-format requirement. No file extension guarantees successful parsing.

Greenhouse supports PDF, DOC, DOCX, RTF, and TXT uploads, but accepting a file is different from extracting its fields accurately. Check that your exported text is selectable and readable; image-only content adds extraction risk. Pika exports PDF, not Word. See the resume format guide for a pre-submission checklist.

How long your resume should be. The honest answer is contextual:

• 1 page if you have under 10 years of experience or are applying in a 1-page-default market (US tech, consulting, finance)
• 2 pages if you have 10+ years or are applying in a 2-page-default market (most of Europe, academia, UK senior roles)
• 3+ pages is reserved for academic CVs (every publication listed) and federal resumes

Cramming 15 years onto one page by shrinking the font is a worse signal than going to 2 pages.

The specific terms a recruiter or ATS is looking for: skills, tools, methodologies, certifications, job titles, and industry vocabulary. Pulled directly from the job description you’re applying to.

Generic resume keywords don’t exist - what’s a keyword for one role is irrelevant for another. The phrase “managed cross-functional team” is a keyword for product management roles, not for backend engineering roles.

Repeating keywords unnaturally or hiding them in a resume instead of showing relevant qualifications in context. Repetition is not evidence of a skill, and there is no universal keyword density or hidden-text rule that predicts employer selection.

Use a job description’s terminology only where it accurately describes your experience. A concrete project, qualification, or achievement explains a skill more usefully than a hidden list of keywords. Do not invent qualifications to improve a diagnostic score.

Rewriting your resume to match a specific job description, by mirroring its vocabulary, surfacing the experience it asks for, and de-emphasizing the parts of your background it doesn’t care about.

Tailoring can make relevant experience easier to find, but it does not guarantee a recruiter callback. Our Pika Match tool helps compare a resume with a job description.

Concrete, demonstrable, often technical skills: programming languages, design tools, languages spoken, certifications held. They’re either present or absent - no judgment call.

“Python” or “Adobe Illustrator” or “CPA” are hard skills.

Behavioural and interpersonal capabilities: communication, leadership, conflict resolution, time management. Soft skills are notoriously hard to evidence in a resume (anyone can claim them); strong resumes evidence them indirectly through bullet points that imply the skill rather than name it.

(“Mediated a contract renegotiation with a strategic vendor that recovered $1.2M in committed spend” evidences negotiation without using the word.)

Skills you developed in one industry or role that apply to another. The single most important concept for career changers.

A teacher applying to product management has transferable skills in stakeholder management, curriculum design (read: roadmap planning), and presenting complex ideas. The resume’s job is to translate, not hide, the original context.

The 30-90 second initial scan a recruiter does on your resume before deciding whether to advance you to a hiring manager. Decisions are made on:

1. Does the role title roughly match what we’re hiring for?
2. Does the seniority and company calibre match?
3. Is there one specific, scannable accomplishment that justifies a longer look?

Most rejections happen here.

The percentage of applications that result in a recruiter or hiring manager reaching out for a screen. Industry baselines:

• 2-5% for cold applications through ATS systems
• 8-15% for tailored applications
• 30-50% for warm referrals

Tracking your own callback rate is the single highest-signal metric for whether your resume is working.