Not a lecture on resume tips. A supervised working session with pre-work, a scoring rubric, a peer-review protocol and a checkout step — designed so that every student leaves having actually rewritten their resume, and so that a small team can review hundreds of them.
Almost every placement cell runs a resume session, and almost none of them change the resumes. The reason is structural: a lecture produces notes, and notes do not become an edited file. A workshop that ends with every student uploading a second version does. This kit is the agenda, the rubric and the review method — the parts you can lift and run next week. It is the readiness intervention with the shortest lead time and the most visible result, which makes it the right place to start if the batch's placement season is close.
The standard resume session is a slide deck of dos and don'ts delivered to a hall. Students agree with all of it, and their files do not change, because rewriting a resume is not a knowledge problem. It is a work problem: the student must sit with their own document, decide what to cut, and find a measurable outcome for a project they have never described in outcome terms before. That work does not happen unless it is supervised and time-boxed.
One link, one deadline, a fixed filename convention such as roll number and version. Students without a resume get a starter template with the section order fixed, so they arrive with a populated skeleton rather than nothing.
Each student brings one real job or internship description they would genuinely apply to. Tailoring is impossible to teach in the abstract, and this is what makes the exercise concrete.
A rough list — projects, internships, competitions, positions of responsibility, certifications — with any numbers they can remember. Doing this in the room wastes the most expensive part of the session.
Score the submitted drafts against the rubric before the session, even roughly. You will find that the batch clusters into two or three defect patterns, and you can then aim the teaching at what is actually wrong instead of at a generic checklist.
| Time | Segment | What actually happens |
|---|---|---|
| 0–15 | Framing | How a resume is read: a screening pass measured in seconds, then a parsing system, then an interviewer using it as a question bank. Three readers, three different requirements. |
| 15–40 | The rubric, taught live | Walk through all eight criteria on two anonymised examples from the batch's own drafts. Score them aloud. Disagreement here is useful — it calibrates everyone. |
| 40–70 | Supervised rewrite of one bullet | Every student rewrites exactly one bullet, from duty to outcome, out loud in a pair. Facilitators circulate. This is the core of the workshop and should not be shortened. |
| 70–95 | Peer review | Swap documents, score against the printed rubric, write one specific improvement per criterion. Reviewers sign their sheet, which changes the quality of feedback immediately. |
| 95–125 | Structure and formatting clinic | Section order, the education block, projects with links and outcomes, and the formatting choices that break parsing. Students fix their own file live. |
| 125–155 | Tailoring and machine check | Each student tailors against the job description they brought, then runs an ATS or parsing check and fixes what it flags. |
| 155–180 | Checkout | Version two uploaded, rubric self-score recorded, and each student writes down the single next change they will make. Nobody leaves without submitting. |
Eight criteria, scored 0, 1 or 2 — sixteen points in total. Keep it to one printed side. The scale matters: three points force a judgement, five invite everyone to award a middling score to avoid deciding.
| Criterion | What a 2 looks like |
|---|---|
| Contact block | Name, one phone number, a professional email address, and working links to a code or portfolio profile. No photograph, no full postal address, no date of birth, no marital status. |
| Headline and summary | Two or three lines naming the target role and the strongest evidence for it. No objective statement about 'seeking a challenging position'. |
| Education block | Degree, institution, year, and the grade in one consistent format across all entries. Correct and complete, because a recruiter checks this against eligibility criteria before reading anything else. |
| Projects | For each project: what it does, what the student personally built, the technologies used, and either a link or a result. Not a course title with a list of tools. |
| Skills honesty | Skills that appear somewhere else on the document as evidence, grouped sensibly, with no self-assessed proficiency bars. Anything listed here is fair game in a technical interview. |
| Bullet quality | Each bullet: strong verb, what was done, and an outcome that is measurable or at least concrete. Duties described without result score 1 at best. |
| Machine-readability | Single column, standard section headings, no text in tables, headers, footers, text boxes or images, a common font, and a file saved as text-bearing PDF rather than an exported picture. |
| Length and targeting | One page for a fresher with no substantial work experience, ordered so the most relevant content for the target role is in the top third. |
Use the total for triage, not for grading students. A score of 12 and above needs individual polish; 7 to 11 needs one targeted correction, usually bullets or projects; below 7 usually means the document needs rebuilding from the template rather than editing.
'Responsible for the database module' says nothing a hundred other students' resumes do not. The fix is a sentence pattern practised until automatic: what you did, how you did it, and what changed as a result. Where no metric exists, a concrete outcome still beats a duty — the module shipped, the club ran the event, the model was evaluated against a baseline.
Twenty technologies listed because they appeared in a curriculum. It reads as noise and it fails in the technical interview, where anything listed is legitimately examinable. The fix: cut to what the student can be questioned on, and make sure each survivor appears again in a project or internship.
A project title, a technology list, and nothing about what it did or what the student built. The fix is a fixed three-part shape — problem, contribution, result or link — and a repository or demonstration link wherever one can exist.
An opening paragraph about seeking growth in a reputed organisation, occupying the most valuable space on the page. Replace it with a headline naming the target role and the strongest evidence, or delete it entirely.
Two-column layouts, contact details inside a header, section titles inside tables, skill ratings as graphics, and files exported as images. These look designed and can arrive at the recruiter as a resume with no phone number and no education. The fix is a plain single-column layout and a machine check before every submission.
The arithmetic defeats most cells: if a careful individual review takes ten minutes, a batch of three hundred is fifty hours of faculty time that does not exist. The answer is a pyramid — automate the mechanical layer, delegate the rubric layer, and reserve expert attention for the documents that need judgement.
Parsing, section detection, keyword match against a target job description. This catches the entire machine-readability criterion and most tailoring problems with no human time at all. Resumere's ATS check and job-description matching do exactly this layer, and students can re-run it themselves as often as they like.
Train twenty student coordinators on the rubric first, in their own session, by scoring the same three anonymised resumes and arguing about the differences until they converge. Trained peers reliably catch bullets, projects and skills honesty.
Faculty coordinators re-score a random sample of peer-reviewed documents to check the reviewers, not the students. If sampled scores drift from the coordinator's, retrain rather than re-review everything.
Reserve individual review for the lowest tier and for students targeting selective roles. This is a small fraction of the batch and is where an experienced reader adds something no rubric can.
Measure the document, not the outcome. Rubric score at version one against version two is a clean, attributable measurement you can report. Shortlist rate is not: it is confounded by which recruiters visited, which roles were open, and how the batch prepared for assessments — and claiming a workshop caused a change in shortlists is exactly the kind of unfounded claim that erodes trust in the cell's reporting.
Then run the follow-up. A single workshop produces a good version two and a slow decay afterwards, because resumes need re-tailoring for every application. Schedule a short re-check before each major drive, tied to the pre-placement talk debrief so students tailor against a role they have just heard described.
Partner institutions get Resumere for their students at no platform cost — ATS-ready resumes, JD matching, and an HR partner network that sources from partner campuses.
The rest of the campus operations library.
Resumere is free for partner institutions. Your students build ATS-ready resumes; verified HR partners source from partner campuses.
These guides describe process and judgement, not recruiter-specific criteria. Eligibility rules, test patterns, compensation and hiring dates change every cycle and differ between campuses — always work from the Job Announcement Form and test invite you actually receive, and from the current official framework documents for any ranking or accreditation submission.