It is 11pm, your studio project is finally pinned up, and you have just opened a blank CV document. Weeks of site visits, sketch models and late-night revisions somehow need to fit into a few lines. Suddenly, the task feels harder than the project itself.

If that sounds familiar, you are in good company. Architecture is about decisions on space, movement, materials and context, and none of that shrinks neatly onto one page. This guide shows you how to share the thinking behind your work without turning your CV into a second portfolio.

1. What Your CV Actually Needs to Do

Your portfolio carries the visuals. Your CV gives the reader a quick sense of the person behind them: what you have studied, what you have done and where you are heading. It is a guide, not a catalogue.

Picture two students applying for the same placement. Both have used AutoCAD and finished a studio project. One simply lists them. The other adds a line on the brief, the decisions explored and the drawings produced. The second student is not necessarily more talented; they have just made their contribution easier to see.

So aim to answer three questions clearly:

• What have you studied or worked on?
• Which skills have you genuinely used?
• How does this connect to the role you want?

You do not need years in practice. University projects, group work, part-time jobs and volunteering all count when described honestly.

2. Why Writing It Feels So Difficult

Most students struggle with the same thing: deciding what deserves space. You may have produced dozens of drawings across several projects. Listing everything crowds the page, yet leaving too much out makes you look less experienced than you are.

Software is another trap. Typing “Revit, AutoCAD, SketchUp and Photoshop” takes seconds. Explaining how those tools helped you develop an idea takes thought, so many people skip it.

Group work adds a third problem. If your team designed a community library, do not imply you drew every part of it. Perhaps you researched the site, developed circulation diagrams or prepared presentation boards. Those tasks are worth naming in their own right.

3. Getting Outside Help Without Losing Your Voice

Sometimes a fresh pair of eyes helps. A tutor, a careers adviser or a graduate working in practice can spot gaps you have stopped noticing after your tenth edit.

You may also come across what people describe as UK Best Architecture CV Writing Services while searching for support. Whatever you read or consider, the sensible test is simple: does the guidance help you describe your real experience accurately, and does the finished CV still sound like you? A polished page means little if you cannot talk through every line at interview.

Treat any feedback as a second opinion, not a replacement for your own judgement. You know which decisions you made in your own projects. Nobody else does.

4. Linking Design Thinking With Technical Skills

Architecture needs creative judgement and technical communication together. A drawing can look beautiful yet fail to explain how a building responds to its site. A precise model may not reveal why the decisions make sense.

Take a university project on a sloping site. You might have explored orientation, access routes, changes in level and the link between indoor and outdoor space. The software helped you test and present those ideas, but the reasoning gave the work its purpose.

That is why you should explain what you used a tool to achieve, rather than presenting the tool as the achievement. Group your skills under three headings:

• Design and analysis: site research, spatial planning, precedent studies and environmental considerations.
• Technical communication: plans, sections, elevations, physical and digital models.
• Professional skills: collaboration, deadlines, handling feedback and explaining decisions.

Only include what you can discuss confidently. If you touched a package in one module, say so honestly. Interviewers value a real example far more than an impressive-sounding list.

5. Turning Your Experience Into Stronger Lines

Start with what you already have. Choose two or three projects that show different strengths: perhaps site analysis, technical drawing and teamwork. For each one, jot down the brief, your contribution, the skills used and one decision you made.

Here is a quick before-and-after. Before: “Completed a residential project using Revit.” That tells the reader very little. After:

• Developed a residential concept in Revit, using digital modelling to test spatial arrangements and communicate the proposed layout.

Use wording like that only if it is true. If you mainly produced drawings from an existing design, say exactly that. Specific, honest lines are easier to defend in an interview.

Try the Two-Line Test, a simple shortcut worth borrowing. For every project, write one line on what you did and one on what you decided. If either line is missing, you probably need more notes before writing the CV entry.

Then tidy your skills section. Group related tools, remove anything you have barely used and avoid calling yourself an expert without evidence. Make your course, institution and dates easy to find.

6. Mistakes That Weaken an Architecture CV

A good-looking layout cannot rescue vague descriptions. Watch for these common slips:

• Software without context: name your tools, then show what they helped you do.
• Identical project descriptions: avoid repeating “developed a concept” everywhere.
• Overstated responsibility: separate individual work, group contributions and professional experience.
• Crowded pages: cut anything that does not support your application.
• Decoration over clarity: clear headings and readable text beat elaborate graphics.
• One CV for everything: your experience stays the same, but its relevance changes with each role.

Be especially careful with sustainability, building regulations, detailing and construction knowledge. Studying a subject is not the same as applying it in practice. Describe what you investigated, produced or learned, and be clear about the level.

7. One Final Check Before You Submit

Before you send anything, check the practical details. Follow the employer’s requested file format, page limit and instructions, because expectations differ between practices. Then read your CV beside the job description. Can the reader quickly find your most relevant experience?

Imagine a second-year student, Priya, who sent a generic CV to several practices and heard nothing. She rewrote it around two projects, named her role in each and matched her portfolio pages to them. Her next application led to an interview. Her experience was identical; only the clarity changed.

Building a CV is mostly an exercise in editing. Show what you studied, what you contributed, which tools you used and how your judgement is developing. Let the portfolio provide visual depth while the CV offers a clear route through it.

Ask yourself one last question: could someone unfamiliar with my projects understand what I did and what I learned?

If the answer is yes, you are on the right track. Your CV does not need to make you look more experienced. It needs to make the experience you already have easier to recognise.