Resume¶
~14 min
In short¶
A resume is a one-page summary that a reader scans quickly. Write only what you can back up, use a plain layout, follow one bullet pattern, and use clearly marked placeholders where you lack a number. Do not guess numbers. A true, checkable line beats an impressive invented one.
One-page rules¶
- One page. Cut content before you shrink the font.
- Use a single column with plain headings. Keep key information out of tables, text boxes, icons and images, because some recruiting systems read the text in order.
- Body text around 10 to 11 pt, margins around 0.5 to 0.75 inch. (Author's guidance.)
- Save a PDF and keep the editable source. Name the file something like
Firstname-Lastname-Resume.pdf. - Order for a student or fresher: header, education, projects, skills, achievements. Put experience above projects only if you have real work experience.
- Use one date format throughout and list the most recent item first.
- Put your GitHub and LinkedIn links in the header, and open both in a private window to check they work.
- Leave out details that are not needed to judge software skills, such as a photo, religion or marital status.
The bullet pattern¶
Use this pattern for every project or job bullet: did X using Y, result Z.
- Weak: "Worked on a web project using Python."
- Better: "Built a REST notes API in Python with FastAPI and SQLite storage; [N] endpoints, [N] tests, documented in the README."
- With a measured result: "Cut repeated query time for the note list from [before] ms to [after] ms by adding an index; measured with [tool] over [N] runs."
Placeholder rule: anything in square brackets is a value you must fill with a real figure before you send the resume. If you have not measured something, do not write a percentage. Write a result you can check instead, such as "all endpoints covered by tests", or "runs from a clean clone in one command". A bullet with a placeholder left in it signals carelessness, so search for brackets before you export the PDF.
Resume checklist¶
| Check | Done |
|---|---|
| Fits on one page in the PDF, not only in the editor | [ ] |
| Every project bullet follows the "did X using Y, result Z" pattern | [ ] |
| Every number is measured, or was written as a bracket and then filled | [ ] |
| Every skill listed appears in a project or course you can explain | [ ] |
| No brackets or leftover placeholders remain | [ ] |
| GitHub and LinkedIn links open in a private window | [ ] |
| Dates, names and project titles match LinkedIn exactly | [ ] |
| Email address and phone number are current and professional | [ ] |
| Spelling checked, and tool names spelled as their official docs spell them | [ ] |
| A friend can ask about any bullet and you can answer for two minutes | [ ] |
What NOT to claim¶
- A skill you have only read about. Put it under "currently learning", labelled as such, or leave it out.
- A role, team size, title or responsibility you did not have. Write "led" only if you led.
- Numbers you did not measure, including users, downloads or GitHub stars you did not get.
- A certificate you have not finished, or a course you did not complete.
- A grade or CGPA you do not have, or a rounded-up figure.
- Tutorial or course work described as a production system used by real people.
- "Expert" for a tool you used in one project. Write "used in [project]" instead.
- Rating, problem counts or ranks from a platform unless the profile is public and matches the claim.
Try this¶
Rewrite your three strongest resume bullets using the pattern. For each bullet, name the file, test or commit that proves it. Delete any bullet you cannot prove, and replace it with one you can.