A portfolio for your job application: choose work samples, explain projects and demonstrate your skills

A job application portfolio is a selected collection of work samples with short explanations. It might be a PDF, a website or a group of accessible project pages. The important point is not the packaging but the connection between the advertised task and your demonstrable contribution. Austria’s public employment service, AMS, describes work samples as evidence of previous work that makes skills and working methods visible. That basic distinction is useful when applying in Germany as well.

A portfolio does not replace your CV or a required qualification document. It answers a different question: how do you approach a specific problem? A gallery without context provides little help. Neither does a list of every project since your first semester. A small, understandable selection is usually more useful than a large archive that forces the reader to discover the relevant evidence independently. Make the purpose of each sample immediately apparent.

[1] AMS: work samples and portfolios

Start with the job advertisement. If it explicitly asks for work samples, a GitHub profile, a showreel or project examples, follow the requested format. Concrete work can be particularly informative in design, writing and software development. A short case study may also help in project management, data analysis or technical roles, provided it genuinely demonstrates an important requirement rather than merely adding attractive pages.

Where no portfolio is requested, ask whether it supplies information your CV cannot communicate adequately. For an administrative application with clearly specified documents, an extra attachment might be unnecessary. For graduates and international professionals, however, it can make practical experience understandable when a degree name or former job title says little to the employer. Do not attach the same portfolio automatically to every application. Select it with the same care you use for the rest of your documents.

Read a German job advertisement carefully

Arrange your application documents

Create a short mapping exercise: what are the three most important tasks in the target role, and which project demonstrates your experience with each? For a marketing role focused on analysis, a clear campaign comparison may be more relevant than an impressive poster. For a backend position, a small, well-documented service can reveal more than a large website where your contribution was limited to one minor feature.

Assess potential examples for relevance, personal responsibility, ease of explanation and permission to share. A project needs to be understandable without confidential background information. As an editorial starting point, we suggest choosing two to four samples; this is not an employer rule or an industry requirement. Follow a different number if the advertisement specifies one. Remove a weak example rather than letting it dilute stronger evidence. Keep additional projects available for technical follow-up questions during a later interview.

Begin with the situation and objective: which problem needed solving, and for whom? Then describe constraints such as time, budget or technical limitations, but only where that information is authorised for sharing. Explain your role next. “Developed as a team” does not mean “conceived and implemented alone”. Responsibilities should remain visible even when you are proud of a collective result and several people contributed to the same deliverable.

Next, describe two or three key decisions and your reasons for making them. Show a selected result and finish with a factual reflection: what worked, and what would you change? This structure makes a sample useful for a professional discussion. Do not record every intermediate step. Readers should understand your contribution quickly and explore further if interested. Short descriptive headings are more helpful than long promotional paragraphs or a dramatic story that obscures the actual work.

The following example is fictional, not real client work. An applicant presents a self-directed analysis using public data that is permitted for reuse. Her aim was to compare regional demand patterns. She documents the source, cleaning process, analysis and limitations. One chart illustrates the central observation, while a short methods section explains why the chosen comparison is meaningful and where the evidence does not support a stronger conclusion.

The case study explicitly says “personal project” and claims no commercial impact for an employer. Instead of “substantially increased revenue”, it states: “Compared similar regions using a consistent framework and documented differences and missing data.” For an analyst role, this can demonstrate relevant skills without inventing business achievements. The CV needs only a brief project entry with methods and a link. The portfolio contains the reasoning, and the interview can explore decisions and limitations in greater depth.

Describe genuine achievements on your CV

For software development, consider authorised code samples with clear instructions, tests and an explanation of your architecture decisions. A repository should show how the project runs, not simply contain files. For UX or graphic design, the problem, audience, alternatives and reasoned choices are often more informative than finished screens alone. For editorial roles, select texts and explain your contribution to research, structure or revision rather than implying you completed every stage yourself.

In project management, an authorised case study covering planning, risks and coordination may be useful. Do not simply publish internal project schedules. In a skilled trade, approved photographs of your own work with brief explanations can help. Patient information has no place in a nursing or medical application portfolio; apparently anonymised documentation may still be problematic. Permitted qualification evidence or suitable non-personal learning projects can be safer alternatives. If the material’s suitability or permission is uncertain, leave it out.

Before using any material, establish whether you are allowed to share it. Customer logos, internal figures, source code, workplace photographs and meeting notes are not automatically cleared for your application. Removing the company name does not necessarily make confidential content safe. A combination of sector, timing and project details may still identify an organisation or an individual even when obvious names and addresses have been deleted.

Obtain documented approval for the intended use or create a wholly independent example using permitted data. Check your employment agreement, confidentiality commitments and rights to images or text. A password restricts access but does not replace permission to disclose. Exclude material where approval is unclear. These practical cautions are not legal advice: a legal uncertainty requires individual assessment, not creative rewriting. Before sending files, also check properties, comments and hidden spreadsheet tabs for information that should not be included.

A portfolio PDF can be tailored and preserves the intended sequence. A website can display interactive work and offer additional detail. Some roles benefit from both: a concise PDF overview with a clearly labelled project link. Choose according to the employer’s instructions and avoid unnecessary access barriers. There is no need to build a complex personal website if a readable document already explains the evidence effectively.

Test links in a private browser window without your own sign-in details. Check document readability, video playback and the experience on a phone. If access requires permission or a password, explain that briefly and provide the necessary information through an appropriate channel. Compress images without making important details illegible. Large attachments can exceed upload limits, so check the actual application portal rather than assuming a universal file-size allowance. Use a clear file name that connects the portfolio with your application.

PDF or DOCX for applications

Your CV must remain understandable even when nobody clicks the portfolio link. Include important tasks, verified results and relevant tools in the CV itself. For a suitable project, add a short reference such as “Work sample: analysis project, see portfolio link”. The link supplements your professional information; it should not be the only location where your experience, methods or technical skills are described.

The same caution applies to applicant tracking systems. Do not assume every system visits external websites or assigns their contents to your application. Put relevant professional terms in ordinary CV text, but only for skills you actually possess. Then check consistency across your portfolio, CV and professional profile: dates, role descriptions and project titles should agree. Different wording can be understandable, but conflicting claims about responsibility create avoidable questions. Keep labels factual and make it obvious which organisation, period and contribution each sample relates to.

Use CV keywords appropriately

Align LinkedIn and Xing with your CV

A portfolio can help expats explain unfamiliar employer names or job titles. Briefly describe the sector, audience and working environment without artificially elevating your previous employer. If collaboration was multilingual, name the languages actually used and your specific task. “International experience” becomes meaningful through this context, not through a flag icon or a general claim that you can work with every culture.

Choose the language according to the advertisement and your contact with the employer. In a German application, a German summary alongside an approved English work sample can be practical. Avoid translating every technical title literally; explain it clearly instead, and have important wording reviewed. A portfolio does not replace required professional recognition or permission to work. When a foreign qualification needs explanation, keep project evidence separate from the formal details in your education section. Both should be independently understandable and verifiable.

List foreign qualifications on a German CV

Apply in German or English

Prepare a short explanation of each selected project: situation, personal contribution, main decision, result and lesson learned. Ask whether you may briefly show the relevant example. For a video interview, test screen sharing beforehand and open only the file or window you need. Private messages and unrelated customer documents should not appear on the shared screen, even for a moment while you search for the correct presentation.

Expect questions about alternatives, mistakes and collaboration. A credible answer does not need to describe a flawless process. “That assumption did not hold, so I changed the analysis” can reveal more than a polished success narrative. Give team members fair credit and explain your own contribution. Do not disclose confidential details verbally without permission either. The portfolio should support a useful professional discussion, not tempt you to reveal information that would be inappropriate to publish in the document itself.

Prepare a video interview

Structure your interview self-introduction

Before sending, review the portfolio from a stranger’s perspective. Does the first page make the target role clear? Are your contributions separated from the team’s achievements? Are links, language and contact details correct? Can you explain every claim and every figure? If not, remove or clarify that part instead of hoping the reader will not ask about it later in the process.

Compare the portfolio with the advertisement once more. Remove examples that occupy space without showing professional fit. Ask someone unfamiliar with the projects to check whether the case studies make sense. Save the exact version used for that application so you can refer to the same selection at interview. The last step is not another design change: confirm that the CV also names your relevant experience clearly. A strong portfolio supports a coherent application, but it cannot resolve contradictory or incomplete documents on its own.