Why a portfolio is needed alongside a resume
A resume briefly describes a candidate's experience, skills, and achievements. A portfolio complements the resume with examples of your work: projects, cases, visual materials, code, analytical dashboards, or marketing results. Indeed describes a portfolio as material that helps an employer see more relevant information about a candidate's qualifications, rather than just a list of job titles and skills in a resume.
A portfolio is especially important for professions where work results can be shown: designers, marketers, analysts, developers, copywriters, photographers, architects, and other specialists. Indeed specifically notes that portfolios are often used by creative professionals, designers, writers, architects, and developers.
The main task of a portfolio is not just to collect beautiful examples. It should explain what problem you were solving, exactly what you did, what tools you used, and what result you achieved. A Behance article on case studies emphasizes that employers and clients look not only at the final picture but also at how a candidate thinks, makes decisions, and solves problems.
What should be in the basic structure of a portfolio
A portfolio does not necessarily have to be a large website. It can be a separate page, a PDF, a Notion document, a Behance profile, GitHub, Tableau Public, a Google Drive folder, or a personal website. The format depends on the profession, but the structure should be clear.
A universal portfolio structure:
A brief description of yourself: who you are, what you work with, and what problems you solve.
Selected projects or cases.
Your role in each project.
Context of the task: client, product, team, or educational project.
Work process: research, ideas, solutions, tools.
Results: metrics, finished product, changes made after your work.
Links: website, presentation, GitHub, dashboard, mockup, publication.
Contacts.
For a UX portfolio, Coursera recommends having a home page, an "About" page, and a section with case studies. For cases, Coursera advises indicating context, scope, timeline, role, collaboration, problem, method or hypothesis, research, findings, user journey, wireframes, prototypes, and design iterations.
How many works to add
It is better to show a few strong works than many weak or similar examples. For a UX portfolio, Coursera suggests adding about 3–5 in-depth case studies as the candidate's best work.
For an analytics portfolio, Graphed also recommends focusing on quality over quantity: 3–5 well-structured and documented projects can be stronger than a large number of superficial dashboards.
For a developer portfolio, Magic Self Dev suggests adding 3–6 projects with a problem, technical approach, stack, measurable result, live demo, and GitHub repository.
What to add for a designer
It is important for a designer to show not only the final visual but also the path to the solution. A portfolio should include cases that explain the task, constraints, the designer's role, the process, and the result. In an article on case studies, Behance recommends starting with a project overview: what the project is, who it was created for, and what the goals were.
For a UI/UX designer, it is worth adding:
Projects with different types of tasks: landing page, mobile application, web interface, redesign, design system, or research case. Coursera advises showing the problem, method of solution, research, findings, user persona, user journey map, wireframes, prototypes, and design iterations in a UX case study.
For a graphic or brand designer, it is worth showing identity, logos, brand assets, social banners, presentations, printed materials, or campaign visuals. Adobe/Behance recommends avoiding repetition, alternating general shots with close-ups, combining photos, digital images, GIFs, or videos, and maintaining visual consistency through lighting and palette.
It is important for a designer to label every project. A picture title without context does not explain what exactly the candidate did. In a case, you must indicate the role: for example, "created wireframes," "prepared UI kit," "performed checkout flow redesign," "adapted design for mobile and desktop."
It is also worth showing not only the perfect final result but also the stages: research, sketches, moodboard, wireframes, UI screens, prototypes, before/after. Behance explicitly formulates a case study as a story that should show not just "what was done" but also "why it was done."
What to add for a marketer
A marketer needs to show not only creatives or texts but also the business result. A portfolio should include campaign cases that show the task, channel, audience, your role, actions, and the result.
HubSpot describes a case study as a detailed story about a task, actions, and solution that shows real results; it also notes that a good case study should contain research and statistics that confirm the results.
In a marketer's portfolio, you should add:
Performance marketing cases: advertising channel, budget, goal, audience, creatives, campaign structure, CPA, CPL, ROAS, CTR, conversion rate, or other metrics relevant to the task.
Content marketing cases: articles, email newsletters, content plans, SEO materials, tone of voice examples, organic traffic, search rankings, engagement, or lead generation.
Social media cases: strategy, categories, post examples, creatives, reach, engagement rate, audience growth, or applications.
Email marketing cases: segmentation, email sequences, subject lines, open rate, click rate, conversion rate, revenue, or other metrics that were the campaign goal.
Branding or launch campaign cases: positioning, messaging, pages, promotional materials, PR publications, presentations, launch results.
For a marketer, it is especially important to explain which results were a direct consequence of their work, rather than just the general results of the company. If the data is confidential, you can show relative changes: for example, "18% increase in conversion," "24% reduction in CPL," "2.1x growth in organic traffic." HubSpot provides examples of marketing case studies where results are presented at the beginning and supported by charts, icons, or statistics.
What to add for an analyst
An analyst needs to show that they can not only build charts but also answer business questions through data. A portfolio should include projects with a clear analytical task, data source, data preparation, analysis method, visualization, and conclusions.
Graphed writes that a strong data portfolio project should have a clear objective, data sourcing and prep, and demonstrate the entire analytical process: from connecting to raw data and cleaning to creating interactive dashboards.
In an analyst's portfolio, you should add:
Dashboards: sales, marketing, finance, product analytics, customer behavior, cohort analysis, retention, funnel analysis, or operational dashboard.
SQL projects: examples of queries, aggregations, JOIN, CTE, window functions, query optimization, building a dataset for analysis.
BI projects: Tableau, Power BI, Looker Studio, or other tools. Graphed notes that a Tableau portfolio can show the path from raw data and cleaning to interactive dashboards.
Python/R projects: notebooks with cleaning, EDA, statistical analysis, forecasting, or simple models.
Description of the business question: for example, "which channels provide the best return on investment," "where do users drop out of the funnel," "which products generate the highest margin," "what factors influence retention."
For each analytical case, you need to explain where the data was taken from, what transformations were made, what metrics were used, and what conclusions were obtained. Graphed explicitly states that describing the data source and cleaning/transformation steps shows an understanding of an important part of the data analysis lifecycle.
A weak analytical project is a set of random charts without a question. The Bricks writes that a common mistake for beginners is to create a dashboard as a random collection of bar charts, line charts, and KPIs; a strong dashboard should lead the user through a logical story, from general KPIs to details.
What to add for a developer
A developer needs to show not only a list of technologies but also working projects, code, architectural decisions, live demos, and documentation. GitHub notes that a profile can show repositories, gists, contribution activity, pinned repositories, and a profile README, where you can describe yourself, your contributions, and the project context.
In a developer's portfolio, you should add:
3–6 projects with a live demo, GitHub repository, description of the task, stack, role, technical solutions, and result. Magic Self Dev describes exactly this as a basic set for a developer portfolio: projects with impact, technical approach, technologies used, measurable outcome, live demos, and GitHub repositories.
A README for each project. It should explain what the project does, how to launch it, what technologies were used, what the key features are, which solutions were difficult, and what could be improved.
Live demo. For a frontend or full-stack developer, it is important to show that the project can be opened and tested. For a backend project, you can add API documentation, Swagger/OpenAPI, a Postman collection, or a short demo scenario.
Technical context. For example: authentication, authorization, database schema, caching, server-side rendering, background jobs, integrations, tests, CI/CD, deployment, performance optimization.
Contribution to team or open-source projects. A GitHub profile can show contribution activity, pull requests, issues, and repositories that the candidate created or contributed to.
For a developer, it is important not to hide your strongest works. GitHub allows for pinned repositories to show the best repositories and gists on your profile.
How to structure a case in a portfolio
One case should answer simple questions: what was needed, what was done, how it was done, and what the conclusion was.
Case structure:
Project title.
Short description of the task.
Your role.
Team or work format.
Constraints: time, budget, technical framework, data access.
Process: research, planning, production, testing, iteration.
Tools.
Final result.
Metrics or proof of result.
Links to materials.
For a designer, evidence can be mockups, prototypes, before/after, design system, or a published product. For a marketer — campaign metrics, creatives, landing page, promotional materials, analytics screenshots without confidential data. For an analyst — dashboard, notebook, SQL queries, dataset description, and conclusions. For a developer — live demo, GitHub repository, README, screenshots, architecture notes, and tests.
What not to add to a portfolio
Do not add everything. If the work is weak, outdated, or does not match the vacancy, it may lower the quality of your portfolio. Coursera advises showing your best works and updating case studies when new projects appear.
Do not add projects without explaining your role. If the case is a team project, you need to specify exactly what you did. Coursera advises describing your role in the project and the people who participated in the work.
Do not add confidential data without permission. Indeed mentions a statement of originality and confidentiality as one of the possible elements of a portfolio, where you can note that materials are original or confidential.
Do not make the portfolio difficult to navigate. A recruiter or hiring manager should be able to quickly find your best work, understand your role, and follow the necessary link.
How to add a portfolio to your resume
A link to your portfolio should be placed at the top of your resume next to your contacts. For a developer, this could be a GitHub profile and a personal website. For a designer — Behance, Dribbble, Figma preview, or your own website. For an analyst — Tableau Public, a Power BI link, a GitHub with notebooks, or a personal page. For a marketer — a website, a PDF with cases, a Notion page, or a Google Drive folder with examples.
The link title should be clear. It is better not to write just "Portfolio," but "UX case studies," "Marketing case studies," "Tableau dashboards," "GitHub projects," or "Frontend portfolio." This helps the recruiter immediately understand what they will open.
Conclusion
A portfolio attached to a resume must prove your skills through concrete examples. A designer should show the process and visual solutions. A marketer — campaigns, channels, and results. An analyst — business questions, data, dashboards, and conclusions. A developer — working projects, code, README, live demos, and technical solutions.
A strong portfolio does not need to be huge. A few well-structured cases that show your role, logic, and results are enough.