A portfolio that argues: editing student work for applications
A portfolio for an application is a short argument, not an archive. What to leave out and the order that carries the point.
A first application is thin for a reason that is fixable. Not because nothing has happened, but because what happened tends to be described as a set of titles rather than as work, and a title tells a reader nothing about what you did or what came of it.
This section covers the three documents and conversations that decide a placement: the single page and the verb that starts each line on it, the short list of things every interviewer is trying to establish and the four real examples that answer them, and the reference request that is only as specific as the material you send with it. Each guide also says where its own advice stops working, because none of these documents wins anything on its own.
A portfolio for an application is a short argument, not an archive. What to leave out and the order that carries the point.
A late payment is usually process, not malice. The evidence file, the reminder ladder and the point where chasing stops working.
Offices run on macros nobody maintains. A little VBA, learned in short sessions, carries a placement application further than expected.
Coursework, a summer job and a society treasurer role are enough material for one honest page. What matters is which verb starts each line.
The same handful of questions turns up in almost every placement interview. Preparing one example properly beats rehearsing five answers badly.
A reference is written from what the writer can actually remember. How to ask, who to ask, when to ask, and what to send so the letter says something.
The examples that make an interview answer concrete come from work that was recorded while it happened, which is the same habit that makes a set of notes worth reopening. The binder starts again at the first section.