Guides
CV projects and languages: show evidence without overclaiming
Projects and languages are two of the places a CV can show evidence rather than claims: what you actually built and how well you can actually work in another language. Both go wrong the same way - overclaiming - and both are easy to test in an interview.
Describe a project
Name the project, when it ran and what it was for, then your part in it: what you did, with which tools, and what came out of it. A school, volunteer or personal project is valid evidence when it is labelled as what it is. In a team project, say which part was yours.
Do
- Say what you did, not what the team did.
- Name the tools you used yourself.
- Link a portfolio or repository only if it is current and public.
Avoid
- Presenting a course exercise as client work.
- Metrics you cannot explain.
- A link instead of a description.
Describe a language
Use a CEFR level (A1 to C2) or a short description of what you can do at work: negotiate with suppliers in German, handle customer emails in Czech. Do not claim fluency because you can read a menu or follow a meeting passively; the interview may switch languages.
Build this CV in Appliora
Start from a layout that suits the role, then build and preview your CV free.