A class project is already evidence. It usually looks like homework, which is why employers skip it. The fix is a short public version of one project you finished, written for one role.
CareerOneStop says a resume summary can hold academic work when a job history would hide the best thing you have done. It also says a reader may only give the page 15 to 20 seconds, so the proof has to be visible in the same words the posting uses. NACE’s Job Outlook 2026 Spring Update says employers want coursework tied to professional skills, and they want an example of you using a skill on a problem. A project write-up is that example, if you stop describing the assignment and start describing the decision you made.
Pick one project and one posting
Choose a project you can explain without opening the rubric. If you need the prompt in front of you to remember what you did, it is not the one. Choose a posting you would actually apply to this month. Read the required skills. Keep the project only if at least two of those skills show up in the work. A beautiful project that uses none of the posting’s tools is a portfolio piece for a different search.
You need the artifacts you are allowed to share. A lot of course work can be described but not posted in full, because of a syllabus rule, a partner, or a data set you do not own. Describe the method and the result, and leave the restricted file off the internet. If a partner did half the work, say so. Claim the half you did. Employers are more wary of a solo claim that falls apart in the interview than of a shared project with a clear split.
Rewrite it in one page
Use five headings and no more.
The problem. Two or three sentences a stranger can understand. Not “for class we had to.” What was broken, unknown, or needed.
What you did. The steps, in order, with the tools named the way the posting names them when the tool is truly the same. If the posting says SQL and you used a spreadsheet, write spreadsheet. Do not upgrade the tool.
The result. A number if you measured one. If you did not measure one, do not invent a percentage. “The script processed the sample file in one pass” is a result. “Improved efficiency by 40%” is a fiction unless you timed both versions.
What you would change. One sentence. This is where judgment shows up. NACE’s readers are looking for problem-solving.
The link or the attachment. A readme, a PDF, a short screen recording, or a photo of the poster. If the only copy is trapped in a learning portal, export what you are allowed to export this week. A project nobody can open is a story, and stories without an artifact get discounted.
Put the page where a resume line can point. A single PDF named with the project and the year is enough. You do not need a personal site to start. CareerOneStop’s formatting advice still applies when you paste a line onto the resume: plain language, near the top if this is your main evidence, and the posting’s term when it is accurate.
The resume line and the interview line
The resume gets one line. Verb, task, tool, result. The interview gets the same story in under a minute, ending with the change you would make. Practice it once out loud. If you stumble on the result, the result is too vague. Go back to the file and write a result you can say.
Do this for one project before you start a second. Two half-finished pages are not a portfolio. One finished page can anchor several applications if the skills overlap. When a new posting needs a different skill, you either add a second project later or you lead with a different line from the same project. You do not rebuild the world for every form.
Ask one person who was not in the class to read the page and tell you what they think you did. If they cannot say it back, the problem statement is still written for the instructor. Fix that paragraph only. Do not add adjectives.
Example
Example. You built a small survey analysis for a methods course. The posting you want is a research assistant role that asks for data cleaning and a written summary. Your page says the problem was a messy export with duplicate rows, you removed duplicates and wrote the comparison the instructor asked for, the result was a three-page memo and a cleaned table you can show, and next time you would save the cleaning steps in a script instead of clicking. The resume line uses “cleaned” and “wrote,” which are the posting’s ideas, and it does not say you “led analytics strategy.” Your partner designed the questionnaire. You say that in the second sentence so the interview does not surprise you.
How Flightpath helps
A resume you upload is turned into suggested skills and experiences. The file is not stored. Nothing counts until you confirm it, so a class project on that resume becomes a fact the gap list can use only after you say the line is true. Bringing in projects as their own confirmed items, separate from a resume parse, is coming soon, and a one-page portfolio generated from those confirmed projects is later still. A tailored resume rewrites the line for a pinned posting. You see the changes before anything is used, and you approve anything before it is sent.