write-a-project-description-for-a-resume

# write-a-project-description-for-a-resume Show the candidate's contribution within the project's real context. ## When to use - Use for independent, academic, open-source, volunteer, client, or internal projects. - Do not imply production use, team ownership, client permission, users, revenue, or performance that cannot be verified. ## Procedure 1. Record project purpose, audience, dates, team, constraints, candidate role, and evidence. 2. Select the challenge and decisions most relevant to the target role. 3. State individual ownership and credit collaborators accurately. 4. Name tools or methods only when they explain a meaningful decision. 5. Describe a tested output, adoption, learning, or bounded result with verified units. 6. Link only to public, functioning, permissioned artifacts. 7. Remove confidential data, copied descriptions, vanity metrics, and unsupported causal claims. 8. Check that title, dates, link, role, and result match the source project. ## Done - A project entry records context, individual contribution, relevant decisions, method, and verified result - All dates, metrics, links, permissions, and team attribution are checked against the project evidence