the portfolio advantage: showcasing your AELO Swiss Academy projects to employers

A few years ago JAA to FAA conversion I sat on a hiring panel for a junior strategy role at a mid-sized logistics firm. Two finalists. Both fresh out of their studies, both with respectable grades, both with one internship of roughly equal weight. On paper they were nearly interchangeable. The difference was a link. One candidate attached a short portfolio to her application, four projects built entirely from coursework, and we spent the better part of the interview inside one of them: a market entry analysis she had produced for a group assignment. By the end of that hour the panel understood how she framed a problem, how she worked with incomplete data, and how she argued for a recommendation her teammates initially resisted. The other candidate was talented, I am fairly sure. We simply had no way of seeing it.

That is the portfolio advantage compressed into a single hiring decision. Most students treat coursework as something to survive, then file it away the day the grade is released. Employers, meanwhile, are starved for evidence. At entry level, where nobody has much of a professional track record yet, the projects you completed during your studies are often the only substantial work you have. Discarding them is like an apprentice burning everything he built during his training, then wondering why no workshop will take him on.

A transcript tells employers what you studied. A portfolio shows how you think

A grade is a proxy. It compresses months of research, argument, revision, and presentation into a single number, and then that number gets squeezed into one line on a CV between two other numbers. A hiring manager reading forty applications cannot reconstruct the work from the grade. All the signal has been averaged away.

A portfolio reverses the compression. It lets an employer see the shape of your thinking: how you defined a vague brief, which constraints you treated as fixed and which you challenged, what you measured, what you chose not to measure, and how you defended a recommendation when someone pushed back. Those are the behaviours companies actually hire for, and they are almost impossible to demonstrate through a CV alone.

There is a second, quieter benefit. Building the portfolio forces you to review your own work with distance, and that review is where the professional growth happens. I have watched students go through this exercise and discover, sometimes with some embarrassment, that their strongest project was not the one with the best grade. It was the one where the scope collapsed halfway through and they had to rebuild the plan in a week. The grade said "satisfactory." The story said "handles pressure and makes trade-offs under constraint." Employers care about the second thing far more than the first.

Curate ruthlessly: three projects beat ten

The most common mistake, and the one I would eliminate first, is volume. A portfolio is not an archive. It is closer to an investment portfolio in the original sense of the word: its value comes from deliberate selection, not accumulation.

Three to five projects is the sweet spot for a graduate portfolio. Fewer than three and the reader starts wondering what is missing. More than six and nobody reads past the second. A recruiter's first pass over an application is measured in seconds, not minutes, and a dense wall of project titles produces the same result as no portfolio at all: a skim, a shrug, a pass.

When choosing which AELO Swiss Academy projects make the cut, I would weigh four things. Relevance to the roles you are targeting comes first, and it regularly overrules pride. You may have loved the brand repositioning exercise, found it glamorous, poured your best design instincts into it, but if you are applying for operations roles, the supply chain simulation you found tedious is the one that belongs in the portfolio. Second, look for projects where you made a real decision, where there was a fork in the road and you can explain why you took the left path. Third, favour projects with some form of outcome you can point to, whether that is a number, a panel verdict, a professor's assessment, or a clear before-and-after comparison. Fourth, pick projects you can talk about for ten minutes without notes, because if the portfolio works, that is exactly what will happen in the interview.

The translation problem: from academic brief to business language

Here is a pattern I see constantly. A student titles a portfolio entry "Strategic Management, Group Assignment 3" and then opens with two paragraphs on the module requirements. The work underneath might be excellent, but the framing tells the reader nothing and signals, unfairly but reliably, that the writer still lives in the academic world.

Translate everything. "Strategic Management, Group Assignment 3" becomes "Market entry analysis: Swiss wellness brand expanding into Vietnam." The reader now knows the industry, the geography, and the question at stake before reaching the second line. Strip out module codes, word counts, and grading criteria. Replace them with the constraints a business person would recognise: a fixed budget, a timeline, a data limitation, a stakeholder who disagreed.

Verbs matter more than adjectives. "Was responsible for the analysis" is dead weight. "Modelled three pricing scenarios and recommended the middle path" moves. Build, test, negotiate, cut, redesign, pilot, recommend. If a sentence in your portfolio contains none of those verbs, ask whether the sentence is earning its place.

One caution from experience: translation has a limit, and past that limit it becomes inflation. Do not describe a classroom exercise as a "consulting engagement" or a peer review as "client feedback." Interviewers ask follow-up questions, and the moment you start hedging about what the project actually was, the whole portfolio loses credibility. The honest version, "a capstone project structured around a real market question," is entirely respectable on its own.

What each project page needs

Whatever the format, each project deserves roughly a page, and every page should carry the same five load-bearing elements:

• the brief in one or two sentences, including the constraints you worked under
• your specific role, stated plainly, if the project was group work
• the key decision you made and the reasoning behind it
• the outcome, with numbers wherever they exist and qualitative evidence where they do not
• what you would do differently now, with a sentence on why

The last item is the one people skip, and it is the one I read most carefully. Anyone can list achievements. A candidate who writes "in hindsight, I weighted survey data too heavily against the interviews, and I would rebalance that" is showing me a person who metabolises experience instead of collecting it. On a panel, that sentence does more work than a full page of polished claims.

Numbers deserve a note of their own. Students often assume academic projects cannot be quantified, which is rarely true once you look. A marketing plan projected a revenue range. A process redesign had an estimated time saving. A simulation produced a result against a benchmark. Even where the project was hypothetical, you can quantify the analysis itself: twelve stakeholder interviews, forty competitor SKUs mapped, three scenarios modelled. Precision about your method is a credible substitute for precision about results.

Group work: claiming your share without inflating it

Much of what you produced at AELO Swiss Academy was probably collaborative, and this creates the trickiest honesty problem in portfolio writing. Write "we" throughout and the reader cannot tell what you contributed. Write "I" throughout and you are borrowing your teammates' work.

The solution is structural, not stylistic. State the team size and your role in the first two lines: "Team of five; I owned the financial modelling and led the final presentation." Then write the body in the first person about your slice, and use "we" where the decisions were genuinely collective. Interviewers will probe this, so prepare a precise verbal answer to the question "what did you personally do?" The candidates who answer that question well, with specifics and without disparaging anyone, come across as people who can be trusted on a real team. The ones who answer vaguely, or who suddenly claim credit for everything, do not.

Credit your teammates generously in the reflection section. It costs you nothing and reads as maturity. Nobody has ever lost an offer because they said a teammate's design work made their analysis look good.

When the project touches a real company

Some coursework involves live briefs, family businesses, or data shared under informal confidentiality. If a company could be identified from your portfolio, anonymise it. Rename the business, round the sensitive figures, and describe the industry rather than the client. Then say so: "details anonymised at the client's request" or simply "the company is anonymised."

I once watched a candidate do this beautifully. Her strongest project involved real margin data from a mid-sized retailer, and her portfolio page opened with a note explaining exactly what she had changed and why. Two panel members remarked on it afterwards, independently, as a professionalism signal. She had turned a legal courtesy into evidence of judgement. That is the pattern worth copying.

Format, logistics, and the unglamorous details

The format matters less than people think, but the execution matters more. A clean PDF of eight to twelve pages works perfectly well and has the advantage of being readable offline, attachable to an email, and impossible to break. Keep it under about five MB, name it something sane like "Surname_Portfolio_2025.pdf," and check that it opens on a phone, because a surprising share of first reads happen there. A simple personal site or a public Notion page works too, and pairs naturally with the Featured section on your LinkedIn profile, which is where most recruiters will look first.

Then test everything the day before you send it. A dead link in an application is a small thing that reads as a large thing. I have seen a strong candidate lose momentum purely because his portfolio URL returned a 404 during the panel's preparation, and by the time he fixed it the comparison had already been made.

Using the portfolio in the room

Getting the portfolio read is half the advantage. The other half is what it does to the interview. A link in the header of your CV and one line in your cover letter, "a portfolio of four selected projects is available at this link," is usually enough. Do not attach heavy files unrequested.

When the moment comes, walk through one project in about ninety seconds: the situation, the complication, the move you made, the result. Then stop and let the panel choose where to dig. The portfolio converts an interview from a recital of claims into a guided tour of evidence, and the candidate holding the map controls the terrain.

The best interview moment I ever witnessed came from a portfolio. A candidate walked us through a forecasting decision that turned out badly wrong, showed us the error in her assumptions on the slide itself, and explained what she now checks differently. She got the role because of that page, not despite it.

Five mistakes that quietly sink portfolios

Having reviewed a fair number of these over the years, the failure modes repeat:

• dumping every assignment into one folder with no curation or narrative
• academic jargon left untranslated, from module codes to grading rubrics
• outcomes described without any numbers, benchmarks, or qualitative evidence
• group work written in "we" throughout, with no personal contribution visible
• broken links, desktop-only formatting, or files too heavy to open

None of these reflects the quality of the underlying work. All of them are fixable in an afternoon, which is what makes them so frustrating to see.

The work is already there

There is a strange modesty in the way graduates treat their studies, as though work only counts once someone has paid for it. I would argue the opposite. The projects you completed at AELO Swiss Academy involved real constraints, real deadlines, real collaboration, and real consequences for your grade. That is professional work in every sense that matters to a hiring panel. The only question is whether anyone gets to see it.

Keep the portfolio alive after you land the first job. Add a project every six months, retire the weakest entry, and let it grow alongside you. Within a few years it stops being a graduate portfolio and becomes something more valuable: a running record of how your judgement has developed. The people who maintain that record are consistently the ones who can prove their value when the promotion, the pivot, or the unexpected opportunity arrives. The work is done. Package it, translate it, and put it in front of the people who are looking for exactly what you already built.