THE FIELD NOTES / STUDENT RESUMES
Little experience.
Plenty to work with.
A student resume does not need to pretend you have a long career. It needs to show what you can do, where you have applied it, and how that connects to the opportunity. Here is a practical way to prepare a resume for internships and graduate roles.
Start with a structure that is easy to scan.
Use your name and contact details, education, relevant projects, experience and skills as a starting point. Put your strongest relevant evidence near the top. If a substantial internship is your best evidence, it can come before projects. Include a portfolio or repository link when it contains work you are comfortable sharing.
Keep section labels clear. Use selectable text and check that copying your exported PDF into a text editor preserves the important information. A clean text extraction is useful, but it cannot guarantee how every employer’s applicant tracking system will process the document.
Treat projects as evidence, not just titles.
For each project, explain the problem, your contribution and the tools you used. Separate your own work from the team’s overall output. A reader should understand what you personally designed, built, tested or researched.
Coursework, volunteering, student clubs and independent projects can all be relevant. Select work that supports the role rather than listing everything. A data analyst application benefits from evidence of cleaning data, checking assumptions and explaining findings; a software role may benefit from implementation, testing and debugging examples.
Replace a duty with a specific contribution.
Worked on a college event website.
MORE SPECIFIC — ILLUSTRATIVE EXAMPLEBuilt the event registration form in React, added field validation and tested the mobile signup flow with five classmates.
Use a simple pattern: action + what you changed + how you did it + evidence. Add numbers only when you can explain where they came from. If you did not measure revenue, speed or adoption, describe a concrete deliverable or test instead of inventing a percentage.
Match the role without stuffing keywords.
Read the job description and identify its main responsibilities and required tools. Include relevant skills you actually have, then connect them to a project or experience bullet. Listing SQL is less informative than describing a query you wrote and the question it answered.
A missing-skill suggestion is a learning direction, not an instruction to add an unsupported claim. If a role asks for automated testing and you have not used it, build and test a small feature before adding it to your resume.
Before you send it.
- Check your email address, dates and portfolio links.
- Remove claims you could not explain in an interview.
- Make your contribution clear in each project.
- Read the exported file on both desktop and mobile.
- Check the employer’s required file type and application instructions.
- Proofread names, technologies and repeated words.
Resume Lab reviews selectable-text PDF and DOCX files up to 4 MB. Its score combines clarity, evidence, relevance and completeness. Use the recommendations to decide what to improve; the score is not an ATS certification or a hiring prediction.