Writing Your Bio and Positioning Statement¶

Why This Is Harder Than It Sounds¶

Writing about yourself professionally is genuinely difficult.

Not because you lack things to say. Because you have too many options, no clear template to follow, and a strong internal editor that flags every sentence as either too modest or too presumptuous.

Most students resolve this difficulty by defaulting to one of two failure modes:

The inflated bio — written to impress, full of strong claims, reading like a summary of the person they intend to become rather than the person they currently are. Experienced readers recognise this immediately and discount everything that follows.

The deflated bio — written to avoid criticism, full of hedges and qualifications, beginning with an apology for not having more experience. This gives the reader permission to move on before they have seen the work.

Neither is honest. Both are avoidable.

This document helps you write a bio and positioning statement that is specific, credible, and accurate to where you actually are.

The Bio and the Positioning Statement — Two Different Things¶

Before writing anything, it is worth distinguishing between two related but distinct pieces of writing.

The bio is a brief, third-person or first-person narrative description of who you are professionally — your background, your focus, your current stage. It appears at the top of your portfolio, on your LinkedIn profile, and sometimes as an author note or introduction in other professional contexts.

The positioning statement is a more focused, often shorter declaration of your professional direction — what you do, for whom, and what approach you bring. It is the distillation of your narrative anchor into one or two sentences. It is what goes in a LinkedIn headline, a GitHub profile bio, or the introductory line of a CV personal statement.

They serve the same identity — but different purposes, lengths, and placements.

Writing the Bio¶

Length and Format¶

A portfolio bio should be between 80 and 150 words. That is short enough to be read fully by someone who is deciding whether to keep going, and long enough to communicate something substantive.

A bio longer than 200 words in a portfolio context has almost certainly included things that belong elsewhere — in case studies, in about pages, in extended professional narratives. Keep the bio to its job: introduce you, orient the reader, invite them further.

First person is natural for a portfolio bio (I am a final-year CS student...). Third person (Jessel is a final-year CS student...) is conventional for publications, conference materials, and some formal portfolio formats. Either is acceptable — choose one and be consistent across all your platforms.

What a Bio Should Contain¶

A bio that works does four things in sequence:

Ⅰ — It locates you
Who are you, at this point, in one sentence? Your degree, your year, your institution if relevant, your field. This is the orientation sentence — its job is to place the reader. It should not be impressive. It should be accurate.

I am a final-year Information Technology student at [institution], with a focus on backend systems and API development.

Ⅱ — It states your focus or interest
What draws your attention professionally? Not a list of technologies — the type of problem or the area of practice you are developing in. This is where the narrative anchor becomes visible.

My work over the past three years has centred on building systems that are technically robust and genuinely usable — particularly in contexts where reliability under variable conditions matters.

Ⅲ — It points to something specific
A brief reference to a significant project, a direction of interest, or an aspect of your work that distinguishes you from a generic description. This is what makes a bio memorable rather than forgettable.

My final-year project — a full-stack task management system built for a real client — is the most complete expression of this direction so far.

Ⅳ — It gestures forward
One sentence about where you are heading, or what you are looking for. This makes the bio useful in professional contexts, not just descriptive.

I am currently seeking graduate roles in backend or full-stack development, particularly in environments where systems thinking and user-centred design work together.

Put together, those four elements produce a bio that locates, informs, distinguishes, and invites — in 120 words or less.

What a Bio Should Not Contain¶

Adjectives that require proof
Passionate. Driven. Dedicated. Motivated. Every student bio contains these words. They are not believed by readers because they are claimed by everyone. Replace them with specific evidence: not passionate about data science, but I have spent the past two years building projects that explore how machine learning models behave under distribution shift.

Technology lists as identity
Experienced in Python, Java, React, Node.js, PostgreSQL, Docker, and AWS. A list of technologies is a CV section, not a bio. In a bio, it reads as a claim to expertise that is often overstated and always indistinguishable from every other student bio in the same field. If a technology is central to your professional identity, name it in context — in a sentence that explains why it matters to the work you do.

Passive or apologetic framing
I am still learning, but... / I don't have much industry experience yet, but... These framings hand the reader a reason to discount you before they have seen the work. Acknowledge your stage honestly — I am a final-year student — but do not apologise for it.

Claims that belong in your CV
GPA, module grades, formal awards, and institutional recognitions belong in your CV. A bio that leads with these signals misunderstanding about what a portfolio is for.

Writing the Positioning Statement¶

The positioning statement is the most condensed expression of your professional identity. It is often what appears in a LinkedIn headline, a GitHub bio field, or the opening line of a cover letter.

Its job is to answer, in one or two sentences:

◆ what you do
◇ at what level of experience
◆ with what specific focus or approach
◇ for what kind of context or audience

The Formula — Use It Once, Then Discard¶

A positioning statement formula is a starting point, not a final form.

[Role or identity] focused on [specific area], currently [stage or context], with a particular interest in [distinctive angle or approach].

Examples by stage:

Stage Ⅰ — Starting fresh
Computer Science student developing a focus in data engineering and backend systems, currently in my second year, interested in how data pipelines behave at scale in real-world deployments.

Stage Ⅱ — Final year
Final-year IT graduate specialising in full-stack development, with a capstone project building a real-client application using Node.js and React Native.

Stage Ⅱ — Design
UX design student with three years of academic and project experience, focused on designing for accessibility and underserved user groups.

Stage Ⅳ — Postgraduate
Education researcher investigating the impact of structured literacy interventions on reading comprehension in early primary learners.

Stage Ⅲ — Early professional
Junior backend developer with two years of industry experience, specialising in API design and integration for financial services applications.

What Makes a Positioning Statement Work¶

The statements above work because they are:

◆ Specific — not software developer but backend developer focused on API design for financial services
◇ Honest about stage — not claiming senior expertise at junior level
◆ Anchored in something real — a project, a discipline, a context, an interest
◇ Written for a reader — not for SEO, not to impress algorithms, but to tell a human being something accurate and useful

Calibrating for Different Platforms¶

The same professional identity needs different expressions in different contexts. This is not inconsistency — it is appropriate calibration.

Same identity. Different register. Different length. Different emphasis.

The test of consistency is not that the words are the same — it is that a person who reads your LinkedIn and then opens your portfolio recognises the same professional across both.

Updating Your Bio and Positioning Statement¶

A bio written in first year and never updated is actively harmful by fourth year. It signals that you have not been paying attention to your own development.

Update your bio and positioning statement:

◆ at the start of each new academic year
◇ after completing a significant project
◆ when your professional focus shifts or clarifies
◇ when you begin applying for roles, placements, or postgraduate programmes
◆ when the work in your portfolio has changed enough that the framing no longer reflects it accurately

The bio is not an autobiography. It is a current professional signal. Keep it current.

Continue to Identity Across Platforms →