Module 02 · Resume Engineering
Beating Applicant Tracking Systems Without Keyword Stuffing
Open lesson + course map
On this lesson
Course outline
Module 1 · Your AI Job-Search Toolkit
Module 2 · Resume Engineering
Module 3 · LinkedIn as a Lead Engine
Module 4 · Interview Preparation With AI
An applicant tracking system, or ATS, stores applications and turns resume text into searchable candidate records. Your goal is not to defeat a robot. It is to make your truthful evidence easy for software to parse and easy for a recruiter to find and verify.
By the end, you will have an ATS-safe master resume format plus a method for aligning it to a real job post without copying a wall of keywords or claiming skills you do not have.
// concept
What an ATS Does — and What the Myths Get Wrong
There is no single universal ATS algorithm. Employers use different products and configure different workflows. A useful mental model has three separate parts:
- Parsing: the system extracts fields such as name, contact details, job titles, employers, dates, education, and skills from the uploaded document.
- Search or matching: a recruiter may search for a role title, skill, certification, location, or phrase. LinkedIn's current help documentation, for example, says Recruiter users have advanced keyword filters and that job matching compares a profile and resume with required and preferred qualifications.
- Application questions: the employer may ask about work authorization, location, availability, education, or another requirement. Some answers can be essential screening questions. Answer these separately and truthfully; hiding a phrase in the resume cannot change the answer.
This exposes the popular claim that “75% of resumes are rejected by robots” as folklore, not a safe universal fact. No credible percentage applies across every employer, vacancy, ATS, and configuration. Do not buy an “ATS score” as if it predicts a hiring decision. Test whether the form extracts the right fields and the resume shows the vacancy's evidence clearly.
// concept
Build a Format That Survives Parsing
Use one readable column with conventional labels: Summary, Skills, Experience, Projects, and Education. Keep contact details in the document body. Use text bullets, consistent dates, and full job titles.
| Element | Do | Avoid | Why |
|---|---|---|---|
| Columns | Use one main text column | Two-column sidebars | Reading order can become scrambled during extraction |
| Graphics | Keep essential information as text | Skill bars, icons, photos, logos, or text inside images | A parser may ignore or misread visual content |
| Headers and footers | Keep contact details in the body | Placing the only email or phone number in a page header/footer | Some parsers treat these areas inconsistently |
| Section names | Use familiar labels such as Experience and Education | Creative labels such as “My Journey” | Standard labels make fields easier to identify |
| Tables and text boxes | Use ordinary paragraphs and bullets | Nested tables or floating text boxes | Export order may differ from visual order |
| File type | Follow the employer's stated requirement; use a text-based PDF or DOCX when both are accepted | Scanned PDFs, image-only files, or an unsupported format | The document must contain selectable text and meet the portal's rules |
File type is not a contest between PDF and DOCX. Follow the actual application's current upload instructions, then inspect every auto-filled field before submitting.
Keep this plain master structure as your canonical file:
FULL NAME
City, Pakistan | phone | professional email | portfolio/LinkedIn
TARGET-ALIGNED SUMMARY
Two or three lines using only verified role, domain, and skill evidence.
SKILLS
Group exact, truthful skills: Analytics: Excel, Power BI | Marketing: SEO, email
EXPERIENCE
Job Title — Employer, City Mon YYYY–Mon YYYY
- Action + scope + result or observable outcome
- Action + tool/method + responsibility
PROJECTS
Project Name | link
- What you built, how you built it, and verifiable evidence
EDUCATION
Degree — Institution YYYYPerform a plain-text test: select all, copy, and paste into a notes app. Sensible heading, date, and bullet order is a useful parsing proxy, not a guarantee; the real portal's extracted fields are the stronger test.
// concept
Align Keywords to Evidence, Not Frequency
Separate the job post's required, preferred, and responsibility/context language. Map each important phrase to evidence you can prove.
Copy this prompt into your AI assistant after removing the employer's private contact details. Paste only the public job post; do not include your CNIC, home address, or references' phone numbers.
You are analysing a public job post for truthful resume alignment.
TASK
1. Extract every explicit requirement.
2. Classify each as REQUIRED, PREFERRED, or RESPONSIBILITY/CONTEXT.
3. Quote the shortest exact phrase that supports the classification.
4. Do not infer an unstated requirement.
OUTPUT TABLE
| Exact phrase | Class | Evidence in post | Resume term to consider |
JOB POST
<paste the full public job post here>Compare the table with your record. If “stakeholder reporting” truthfully describes weekly reports for two department leads, use it in that bullet. University work remains project experience. A phrase with no evidence belongs in a learning plan, not the resume.
Keyword stuffing includes repeating “SEO, SEO specialist, search engine optimisation” or hiding white text. One exact phrase beside specific evidence is stronger than unsupported repetition.
// worked_example
Worked Example
The extraction prompt returns this sample output:
| Exact phrase | Class | Areeba's verified match |
|---|---|---|
| Excel reporting | Required | Weekly internship summary in Excel |
| Written communication | Required | Summary email to supervisor |
| Power BI | Preferred | Learning only; no work evidence |
| Internal stakeholders | Responsibility/context | One supervisor, not multiple teams |
Her first draft says: “Power BI expert delivering stakeholder analytics and advanced Excel dashboards.” It fails because “expert,” “stakeholders,” “analytics,” and “dashboards” go beyond her record. The specific fix is: “Cleaned campaign spreadsheets and prepared a weekly Excel performance summary for internship supervisor review.” Under Skills she may list “Power BI — beginner coursework” only if that label is accurate. She must not add it as professional experience merely to improve a match.
Finally, Areeba runs the Notes test and checks the portal's auto-filled employer, title, and dates. She submits the file type the vacancy requests.
// failure_cases
Failure Cases to Diagnose
6 cases to diagnose
Contact details disappear after upload
they were placed only in a header, footer, icon, or text box. Move them into ordinary body text and upload again.
Experience appears in the wrong order
a column or table changed the extraction sequence. Rebuild the section as one column with one role after another.
The application form shows wrong dates or employers
inconsistent date formats or visually complex lines confused the parser. Use one date format and separate title, employer, and dates clearly; then correct the form manually.
The resume contains every job-post phrase but no proof
this is keyword stuffing. Delete unsupported terms and place each remaining phrase beside a truthful bullet or project.
A knockout answer conflicts with the resume
the resume cannot repair an eligibility mismatch. Re-read the question, answer accurately, and do not apply if an essential condition is not met.
An online “ATS score” drives endless rewrites
the score belongs to that tool's model, not the employer's decision process. Prioritise extracted-field accuracy, job evidence, and human readability.
// pakistan_angle
Pakistan Angle
For Pakistani applications, keep city and mobility precise: “Lahore; available for on-site work” or “Islamabad; open to relocation” only when true. State notice period accurately if the form asks. Do not paste a CNIC number, full home address, references' phone numbers, salary slips, or another person's WhatsApp details into an AI prompt. A city and professional contact channel are usually enough for the resume itself unless the employer explicitly and legitimately requires more later.
Many learners prepare applications on a phone or during load-shedding. Keep the master DOCX and exported PDF available offline with clear filenames, and upload only after checking which variant is selected. Mobile previews can hide layout problems, so run the plain-text test and inspect the portal's auto-filled fields. For Rozee.pk, Mustakbil, LinkedIn, or an employer's own portal, treat the current form instructions as authoritative; do not assume one file format works identically everywhere.
// hands_on
Hands-On Exercise
6 steps
Build your ATS-safe master resume from verified material.
Choose one real vacancy and save its public job description.
Copy your verified experience into the one-column structure above without tailoring yet.
Run the requirement-extraction prompt and classify every phrase as required, preferred, or context.
Create a mapping table with three columns: job phrase, your evidence, and action. Mark missing evidence as learn, never add.
Align wording only where the same concept is true; then export the file type requested by the employer.
Run the plain-text test, upload the file if you are ready to apply, and inspect all extracted fields before submission.
// completion_rubric
Completion Rubric
5 checks — tick as you verify
// sources
Sources
// check_yourself
Check yourself
4 questions · answers and options are taken word-for-word from this course
1 / 4 · diagnose
Your work shows this failure mode: “Contact details disappear after upload.” The lesson describes it like this: “They were placed only in a header, footer, icon, or text box.” What does the lesson tell you to do about it?