The one idea
Adjectives are claims. Evidence is a claim plus a way to check it.
Compare:
- "Hardworking team player with excellent leadership skills."
- "Coordinated a 4-person team for a college tech fest; delivered the registration system two days before the deadline and processed 340 sign-ups."
The second is shorter to doubt and harder to fake. It names a number, a timeframe, and a result. A recruiter can picture it. An interviewer can ask about it — and wanting them to ask about it is exactly the point.
Nothing on your resume should be a word you could apply to yourself for free.
Do not say you are hardworking. Say what you did, how big it was, and what happened.
Every bullet follows action + scope + outcome. Adjectives about yourself are removed entirely; the evidence implies them.
A resume is a set of falsifiable claims. Specificity makes a claim checkable, and checkable claims carry information. Unfalsifiable claims carry none, so a reader correctly discounts them to zero.
The bullet formula
Action + scope + outcome.
| Part | What it answers | Example |
|---|---|---|
| Action | What did you actually do? Start with a verb. | "Built a weekly sales tracker" |
| Scope | How big, how many, how long, for whom? | "covering 3 regions and 60 SKUs" |
| Outcome | What changed because of it? | "cut manual report prep from 4 hours to 30 minutes" |
Full bullet: Built a weekly sales tracker in Excel covering 3 regions and 60 SKUs; cut manual report preparation from about 4 hours to 30 minutes.
Two rules that do most of the work:
Start with the verb, not with "Responsible for". "Responsible for managing inventory" describes a job title. "Reduced stock-out incidents by reorganising the reorder schedule" describes a person.
If you have no number, use a comparison or a consequence. Not everything is measurable. "Wrote the onboarding document new joiners now use in their first week" has no number and is still evidence — it names who uses it and when.
When you have no work experience
You have more material than you think. The mistake is believing that only paid employment counts.
Academic projects. Not the title — the decisions. "Final-year project on sentiment analysis" is a title. "Built a sentiment classifier on 5,000 product reviews; compared three approaches and documented why the simplest performed best on our data" is evidence.
Coursework with an output. A case study you presented, a lab report someone else now uses, a dataset you cleaned.
Volunteering and college roles. Event committees, NSS, club secretary, placement coordinator, running a fest. These involve budget, people, deadlines and things going wrong — exactly what employers are trying to test.
Freelance and informal work. Tuition you gave, a shop's Instagram page you ran, a cousin's accounts you organised. Paid or not, if you did it for a real person with real stakes, it counts.
Self-directed projects. Something you built because you wanted to. Strong precisely because nobody assigned it — it shows you can start work without being told to.
Weak: "Participated in college annual fest as a volunteer."
Strong: "Managed registrations for the inter-college fest: built the entry sheet, coordinated with 6 department heads, and handled 340 sign-ups across three days with no duplicate entries."
Same event. The second version tells the reader that you can organise, that you work across groups, and that you cared enough about accuracy to notice duplicates.
Weak: "Good knowledge of Excel and data analysis."
Strong: "Cleaned and analysed a 12,000-row public dataset on district literacy rates; produced a 4-chart summary and identified two districts whose figures contradicted the state report."
The second version proves the first version's claim, and it gives an interviewer something to talk to you about for ten minutes.
ATS, honestly
An ATS (Applicant Tracking System) is the software an employer uses to receive and organise applications. There is a large amount of nonsense written about it. Here is a defensible version.
What actually matters:
- Plain structure. Standard headings — Experience, Education, Skills, Projects. One column. No text inside images, no text inside text boxes, no tables holding your job history. Anything that renders visually but is not plain text can be lost when the file is parsed.
- Real keywords from the job description. If the JD says "reconciliation" and you wrote "matching accounts", a keyword search will not find you. Use their word — where it is honestly true of you.
- A file that reads as text. A PDF exported from a word processor is normally fine. A PDF that is a scan or an exported image is not, because there is no text in it to read.
- Your contact details as plain text at the top, not in a header or footer.
What is largely myth:
- That an ATS "scores" you and auto-rejects below a threshold. Most systems in ordinary use are databases with search, not judges. The filtering is usually done by a person searching them.
- That white keyword text hidden in the background helps. Recruiters see it in the parsed view, and it reads as an attempt to deceive.
- That there is one universally safe template. Systems differ. Plain structure is the reliable answer precisely because it survives all of them.
Recommendation Optimise for the human, keep the structure plain enough for the machine. In
that order. A resume that parses perfectly and says nothing still fails.
Fix this resume
Try this
Here is a real-shaped fresher resume section. Rewrite it.
CAREER OBJECTIVE To secure a challenging position in a reputed organisation where I can enhance my skills and contribute to organisational growth.
EXPERIENCE Intern, Sharma Textiles — Jun 2025 to Aug 2025
- Responsible for various data entry tasks
- Helped the team with daily activities
- Worked on Excel
- Assisted senior staff members
SKILLS Excel, MS Word, Communication, Teamwork, Leadership, Hardworking, Punctual, Quick learner
Before reading the answer, write down at least four specific things that are wrong, and rewrite one bullet properly.
Your challenge
Level 3 · IndependentRewrite your own resume's experience section using the formula.
Success criteria, all four:
- Every bullet begins with a past-tense verb — not "Responsible for", not "Helped with".
- Every bullet contains at least one element of scope: a number, a duration, a count of people, or a named group.
- At least half your bullets contain an outcome — what changed.
- Zero adjectives describing your personality anywhere on the page.
Then hand it to someone who does not know what you do and ask them: "What can this person actually do?" If they cannot answer in one sentence, the evidence is not doing its job yet.
What people usually get wrong
- Objective statements that describe your wishes. The reader is deciding whether you can help them. Lead with what you are, not what you want.
- One resume for every application. The load-bearing items differ per job. Reorder your bullets and match their vocabulary; you do not need to rewrite everything.
- Listing personality traits as skills. "Hardworking" in a skills section actively signals that you had nothing concrete to list.
- Two pages as a fresher. One page, unless you have genuine multi-year experience. Length is not evidence.
- Decorative templates with sidebars, icons and photos. They compete with your content for attention and parse unpredictably. In most countries a photo on a resume is unnecessary; where local convention expects one, follow the local convention.
- Inflated numbers. The interview is where invented figures die, and it dies loudly.
- Sending a
.docxwhen a PDF was asked for. Formatting shifts between machines. Send PDF unless told otherwise, and name the fileFirstname-Lastname-Resume.pdf. - No projects section when you have no experience. This is the section that saves freshers, and it is the one most often left out.
How someone experienced does it
Experienced people write the resume backwards from the job description. For each load-bearing requirement identified in the JD lesson they place a bullet that proves it, in the reader's own vocabulary. The resume becomes an answer to a specific question rather than a biography.
They also know what the top third of page one is worth. The first pass is short and spatial: name, most recent thing, whatever is visually first. Anything you need them to know goes there. A brilliant bullet at the bottom of page two has not been read.
And they keep a master document — every project, number and outcome, added the week it happened. The resume is then an edit, not an act of memory. The most common cause of vague bullets is not modesty; it is writing them eighteen months late, when you can no longer remember whether it was 9,000 rows or 900.
When not to use this
A resume is the wrong instrument for some paths. For a referral, a short message describing one relevant thing you did works better, with the resume attached as backup. For creative and technical roles, the portfolio often does more work than the resume does, and the resume just routes people to it.
Academic applications use a CV instead — longer, and expected to list publications, teaching and grants exhaustively. The evidence principle still holds; the length convention does not.
Why 'contributed to' is the most damaging phrase on a resume
Hedged verbs — contributed to, assisted with, was involved in, helped — are usually written out of honesty. You genuinely did not do the whole thing alone, and you do not want to overclaim.
The reader does not receive it as honesty. They receive it as an absence of information, because the phrase is compatible with having done almost anything, including nothing.
The fix is not to overclaim. It is to name your specific part, which is both more honest and more impressive: "Contributed to the migration project" becomes "Wrote the data validation checks used to verify 40,000 migrated customer records." You have claimed less and communicated more, and you have given yourself something you can talk about for five minutes if asked.
Prove it
Produce a one-page resume where you can point at any bullet and answer three questions immediately: what did you do, how big was it, what changed.
Then, for the three strongest bullets, write two or three sentences of backstory you did not put on the page — what went wrong, what you decided, what you would do differently. Those become the raw material for your story bank, and they are the difference between a resume that gets you an interview and one that survives it.
Keep learning this
Paste this into any AI assistant. It turns the assistant into a tutor that tests you instead of just answering you.
Act as an experienced practitioner who is good at teaching. I have just learned writing resume bullets with evidence instead of adjectives. Assume I am intelligent but relatively new to this — treat me as beginner level. Work through this in order, and wait for my reply at each step: 1. Ask me 5 questions that test whether I actually understood writing resume bullets with evidence instead of adjectives. Do not reveal the answers yet. 2. After I answer, tell me which parts I got right, which I got wrong, and which I only half-understand. Explain only what I misunderstood — do not re-teach what I already know. 3. Give me one practical challenge based on something I could genuinely encounter at work or in daily life. Do not solve it for me. 4. Evaluate my solution the way an experienced person would judge it, including what a professional would have done differently. 5. Tell me what to learn next, and why that comes next. 6. Give me trustworthy sources for deeper study — prefer official documentation, primary research or standards bodies over blogs and videos. Rules for you: no buzzwords. No motivational filler. Say "I'm not certain" when you are not certain, and tell me which parts of your answer I should verify myself. Clearly separate facts from your recommendations and your opinions.
Become independent at this
Use this when you want a path from where you are to actually good, with checkpoints you can test yourself against.
I want to become independently capable at writing a resume that proves what you can do — not permanently dependent on AI, tutorials or step-by-step guides. Design a progression for me with five stages: Beginner, Guided practice, Independent practice, Real-world application, Professional level. For each stage tell me: - what I must know - what I must be able to do without help - the mistakes people make at this stage - one practical challenge - one real project that would prove I reached this stage - one way I can test myself honestly Then tell me the signals that I am ready to move to the next stage, and the signals that I have skipped ahead too early. Keep the theory to the minimum I actually need. Focus on ability I can transfer to situations you and I have not discussed.