If you are reading this in your first or second year of university, with no internship lined up, no public GitHub, and nothing on your CV that did not come from a class assignment — you are not behind. You are at the start. The students who graduate with strong portfolios are not the ones who started with connections. They are the ones who started, kept going, and were patient about how slowly the work compounds at the beginning.
This is the path. It is meant to be specific enough to act on this week.
Why the start feels impossible (and why it is not)
The hardest part of building a portfolio is the first piece, because the first piece has to do something the later ones do not — it has to convince you that you can actually finish a piece of work. Every later piece benefits from that proof. The first one has to manufacture it.
The standard mistake is to wait for permission. Wait for an internship offer. Wait for a course assignment that happens to be portfolio-worthy. Wait until you "know enough" to start. The waiting feels productive — you are studying, you are preparing — but it produces nothing reviewable, which is the only thing the next person looking at your CV is going to ask for.
The other mistake is the opposite: trying to build a portfolio of impressive-looking pieces before you have built anything at all. The pattern is recognisable: a half-finished side project that aimed too high, abandoned at 30%, replaced by another half-finished project that aimed too high. The cure is to scope smaller than feels worthwhile. The first piece should be embarrassingly small relative to your ambition. That is the point.
The first three things to make
The first piece is a study. You take a real problem in your target field — not invented, not abstract — and produce a written analysis of it. Not a research paper. A briefing document, the kind a junior analyst would hand to a manager. Five to ten pages. Sourced. Specific. Concluding with an actual recommendation, not a hedge.
If you are in business: pick a company that operates in your country, look at a strategic decision they recently made (a market entry, a product launch, a pricing change), and write a feasibility analysis as if you were a consultant briefing a partner before the decision was made. If you are in engineering or computer science: pick a real open-source project, identify a feature that has been requested in the issues but not implemented, and write a design document for that feature. If you are in marketing: pick a brand whose positioning you find weak, and produce a market-segmentation analysis with three concrete repositioning recommendations.
The second piece is a build. Take what you wrote in the first piece and produce the next-step artefact. The feasibility analysis becomes a financial model in a spreadsheet. The design document becomes a working prototype, even a rough one. The market segmentation becomes a campaign brief with creative direction and a media plan. The build does not have to be polished. It has to exist and be linkable.
The third piece is a review. You publish a piece that reviews someone else's work in the field — a recent paper, a competitor's product launch, a public-sector initiative — and offers a structured critique. Not a takedown. A practitioner-level review with what worked, what did not, and what you would have done differently. The review piece signals something the first two cannot: that you can read the field, not just contribute to it.
Three pieces. Six to twelve weeks of focused work. By the end of it, you have a portfolio.
How to choose what to build first
Choose the first piece by asking what you would be assigned in your first year of an entry-level job in your target field. Not the most impressive thing you can imagine. The most plausible junior task. If you cannot guess what that is, find someone two or three years ahead of you in the field and ask them. They will know.
The reason to anchor on plausibility is calibration. A first-year analyst at a consulting firm does feasibility studies. A first-year software engineer does feature-level design documents and bug fixes. A first-year marketing associate does competitive teardowns and channel-mix analyses. If your first portfolio piece looks like the first task in those jobs, hiring managers reading it can map it directly to the work they would assign you. If your first piece looks like a master's thesis or a TED talk, it is harder to evaluate — and harder to trust.
The other useful filter is review-ability. Pick a topic where someone you can reach — a professor, an alumnus, a senior student — knows the field well enough to give you concrete feedback on the artefact. The first piece becoming better through review is the moment your skill curve actually starts.
Where the work lives
The portfolio is not a folder on your laptop. It is a set of links a hiring team can click on Tuesday afternoon. There are four standard places.
The first is your CV — the line that says you produced this, with the link. CV pages are scanned in seconds, which means the line has to communicate the artefact in a phrase. Not "Conducted research on market entry in Southeast Asia." That is a generic claim. Try "Wrote feasibility study recommending against XYZ Corp's Vietnam entry; defended position in 8 cited sources." A specific claim with a link survives the seven-second scan.
The second is your digital portfolio — a personal site, a Notion page made public, a GitHub README, a substack. Pick one and own it. Keep it minimal. Three pieces, three short context paragraphs each, three links. Not a CMS. Not a logo. The purpose is to host the artefacts; the purpose is not to be a personal brand exercise.
The third is LinkedIn. Use the Featured section to highlight your three pieces. Each gets a one-line caption — the same kind of specific claim that appears on the CV. Do not write essays in the captions. The caption sells the click; the artefact sells the work.
The fourth is a credential layer. This is what platforms like Ewance exist for: every challenge-based learning piece you ship through the platform produces a verifiable credential anchored alongside the deliverable, so a recruiter can confirm in one click that the work is real, was reviewed against rubric criteria, and has not been altered. The credential layer is what distinguishes a portfolio piece you produced from one that someone else produced and you uploaded. For the same reason that a CV with linked references is stronger than a CV without them, a portfolio with verified credentials is stronger than a portfolio of self-uploaded files.
When to graduate from "first portfolio" to "real portfolio"
The first portfolio is done when three things are true. You have at least three pieces, each linkable, each clearly your own work. You can describe each piece in two sentences without trailing off into hedges. And someone outside your university — a working professional in your field — has reviewed at least one piece and given you feedback you took on board.
The first portfolio is not done when it looks impressive enough that you are no longer self-conscious about it. That bar is unreachable in the first year of building. If you are waiting for that, you will not graduate. The bar is reachable, linkable, defensible — that is the bar.
The transition to a real portfolio happens when you start replacing pieces. The early studies and builds get retired as you produce stronger versions of the same kind of work. By the time you are applying for first-year roles, the portfolio you defend is unlikely to contain anything from the first six weeks. That is normal. The first six weeks were not for the eventual portfolio. They were for proving to yourself that you could finish a piece. Once that proof is in, the rest is iteration.
What to do this week
Pick the field. Not the company. The field — engineering, marketing, finance, public policy, design, research. If you cannot pick yet, pick the one you are studying, even if you are not certain about it. The first piece does not lock you in.
Find the most plausible first task in that field. Three minutes on a recent job description for a first-year role gives you the list. Pick one of the items on that list and treat it as your brief.
Block five hours next week to scope the piece. Not to produce it — to scope it. What is the deliverable? Who is the audience? What is success? Where will it live? Who could review it? At the end of those five hours, write down a one-paragraph project plan and put a date on it.
Then start. The rest of the path is patient repetition. The students who finish their first piece are not the ones with the most talent. They are the ones who scoped small, started, and did not stop.
If you want a structured way to ship pieces against real briefs — with rubric-graded review and verifiable credentials attached — that is what Ewance is for. See your options, or try a challenge for free. Either way, the start of the portfolio is what stops being theoretical the moment you finish the first piece.
