Why Your Dissertation Deserves More Than One Line on Your CV

Sit on a UK hiring panel for long enough and you’ll start noticing the same frustrating pattern, CV after CV.

Candidates who’ve just spent three or four years at genuinely good universities writing complex code, running tight lab protocols, wrangling enormous datasets somehow flatten all of that into one lifeless line near the bottom of page two.

It usually reads something like this:

“Third Year Dissertation: Investigated sustainable energy trends. Grade: 2:1.”

That sentence tells a recruiter almost nothing. It says you sat through lectures, handed something in, and passed. It hides everything that actually matters the late nights debugging a script that refused to run, the workaround you invented when a lab sample went wrong, how you kept a chaotic group project on track and over the line.

If you want your academic work to land interviews in research, tech, or any analytical role, you need to stop describing what your course was about and start explaining how you actually did the work.

Universities and Employers Are Speaking Two Different Languages

Here’s the root of the problem: academia and employers judge your work through completely different lenses.

Your university tests theoretical understanding and correct process, because your lecturers already know the subject inside out. A hiring manager doesn’t care about your syllabus at all. They’re asking a much narrower question:

Can this person handle a messy, unstructured problem under real constraints, without making expensive mistakes?

That means your CV’s job isn’t to summarise your lecture notes or paste in the module description. It’s to extract the operational mechanics:

• What was the actual problem?
• What tools or languages did you choose, and why?
• What constraints were you working under?
• What was the tangible outcome?

Strip away the academic language, and what’s left is genuine engineering or analytical work not “coursework,” but experience.

Stop Burying Your Best Work Under a Part-Time Job

One of the most common mistakes early-career applicants make is prioritising a part-time weekend job over a genuinely technical project purely because the weekend job was paid.

Pulling pints or working a till does show reliability and punctuality. But if you’re applying for a software engineering, data science, or research role, four lines about cash handling should never outrank a six-month project where you built a working machine-learning pipeline or ran serious statistical modelling in R.

Your technical projects belong near the top of your CV, directly beneath your degree summary treated with exactly the same structural respect as a full-time job.

The other frequent misstep is passive, syllabus-style phrasing. Something like “involved studying machine learning techniques” describes something that happened to you, not something you drove. To a hiring manager, that reads as passivity even if the work behind it was genuinely impressive.

A Sharper Framework Than STAR: The Technical Scope Breakdown

Most students have heard of STAR (Situation, Task, Action, Result). It’s fine for general interview prep, but technical and analytical roles need something sharper a framework built around execution, not narrative.

1. Boundary definition (context and constraints) What was the exact technical scope? Incomplete datasets, strict memory limits, tight hardware tolerances, a fixed delivery deadline?
2. Methodological justification (action and choice) Which exact tools, languages, frameworks or instruments did you use, and why did you choose them over the alternatives?
3. Validated output (result) What was the concrete deliverable? In technical projects, impact rarely means profit it means statistical significance, code optimisation, a working deployment, a reduced error rate, or findings you presented to a panel.

Choosing Which Projects to Feature

One deeply relevant project, described with precise technical detail, outweighs a generic list of every module you took across three years.

A few things to get right:

• Match the stack. If the job spec asks for SQL and Python, lead with the exact database work and analytical scripts you built during your degree not a general “studied programming” line.
• Sense-check the language. University shorthand rarely translates outside the department. Getting a second pair of eyes on your draft a careers advisor, a mentor, or even a local specialist like a resume writing service in Cambridge is often the fastest way to spot internal jargon a recruiter won’t recognise.
• Own your slice of group work. State the team context briefly, then immediately claim the exact part you built, so a recruiter knows precisely what was yours.

Turning Flat Academic Phrasing Into Active Evidence

This is where most of the impact gets won or lost in your verbs, and in your specifics.

Weak academic phrasing: “Responsible for studying machine learning techniques and applying them to financial data for my final-year module.”

Active professional framing: “Engineered a random forest classification model in Python (Scikit-Learn, Pandas) to analyse 80,000 credit transactions; optimised feature selection to achieve 89% accuracy in anomaly detection.”

Notice what changed: scale (80,000 transactions), an exact toolstack, and proof the project actually reached a functioning, evaluated endpoint.

For group work, isolate your contribution clearly:

“Co-developed a full-stack web application in a four-person team; designed the relational PostgreSQL database architecture and integrated the backend API endpoints.”

Academic Habits That Quietly Kill Your CV’s Impact

A few traps worth avoiding deliberately:

• Hyper-specialised jargon. Unless you’re applying to niche postdoctoral research, industry-standard terms should replace internal module codes or lab-specific shorthand.
• Listing every module. Nobody needs fifteen module titles everyone on your course took similar classes. Spend your limited space on two or three projects where you actually built, coded, or researched something real.
• Hiding failure. If a project hit a bottleneck or didn’t go to plan, say so. Explaining how you pivoted your methodology or refactored a pipeline shows far more engineering maturity than pretending everything worked first time.
• Ignoring workflow habits. Mentioning Git version control, two-week sprints, or managing a lab budget proves you can walk into a professional team without needing basic training from scratch.

The Real Shift: From Hurdle to Evidence

You don’t need ten years of commercial experience to build a convincing CV. You need to stop treating your university work as a series of hurdles cleared to satisfy an examiner, and start treating it as what it actually is: a track record of real, supervised, high-level work.

Strip out the passive course summaries. Lead with concrete methodology, specific tools, and validated results. Do that, and your academic work stops looking like coursework and starts looking exactly like what it is: your strongest professional asset.