How to Build an Architecture CV That Makes Your Experience Easy to See

There is a particular kind of frustration that comes from reviewing an architecture CV and realising the person behind it is probably much stronger than the document suggests.

You can see the degree. You can see Revit, AutoCAD and SketchUp listed neatly down the page. You can see a placement, a few university projects and perhaps a portfolio link. But after reading it, you still do not know what the candidate can actually do. That is where many otherwise good architecture CVs lose their impact.

The problem is rarely a lack of experience. More often, the experience has been described too vaguely.

A student may have spent an entire semester resolving a difficult site, developing a housing proposal, testing structure, producing technical drawings and presenting the final scheme. Yet the CV may reduce that work to: “Housing project designed plans, elevations and 3D model.”

Technically, that is true. It is also telling the reader almost nothing.

A strong architecture CV should make the reader think, I can see what this person has done.

1. Decide What You Want the Reader to Notice

Before changing fonts, rearranging headings or searching for another CV template, stop and ask a simpler question:

If someone reads my CV for 30 seconds, what should they understand about me?

That question changes everything.

A Part 1 graduate might want the reader to recognise strong design development, drawing skills, digital modelling and the ability to take a project from research through to presentation.

Someone applying for Part 2 roles may need to bring technical development, professional experience, coordination and knowledge of project stages further forward.

An experienced architectural assistant may have a very different story. Their strongest evidence could involve planning submissions, drawing packages, consultant coordination, client communication or working within live projects.

There is no reason all three CVs should look or read the same.

Think of the CV as a selection of evidence, not a complete autobiography. You are deciding which parts of your experience deserve the reader’s attention.

Your qualification tells them what you studied. Your experience needs to show what you can actually do.

2. Treat Strong University Projects as Real Evidence

One of the worst habits among architecture students is apologising for university work by barely describing it.

Until you have substantial practice experience, your academic projects may be some of the best evidence you have.

The trick is to stop writing about them like entries in a university submission list.

Instead of:

“Mixed-use development concept design, plans and elevations.”

Think about what actually happened.

Perhaps the site had difficult pedestrian access. You studied movement through the area, tested different massing options, developed a circulation strategy and used Revit to produce the final drawings.

Now the reader has something to work with.

For each major project, ask yourself:

• What was the design problem?
• What did I personally do?
• What skill does that work demonstrate?
• What part of the process can I confidently explain in an interview?

You do not need to turn the CV into a design essay. A few precise details are usually more convincing than a paragraph of architectural terminology.

And be particularly careful with group projects. If six students worked on a scheme, do not accidentally make it sound as though you designed the entire building yourself. Explain your contribution.

That does not make the project sound smaller. It makes your involvement believable.

3. Make Your Software List Prove Something

Most architecture CVs have a software section. Far fewer use it well.

A list such as:

Revit – Advanced
AutoCAD – Advanced
Rhino – Intermediate
Photoshop – Advanced

looks tidy, but “advanced” means very little without context.

One person may call themselves advanced in Revit because they can model confidently. Another may have used it for coordinated drawing packages on live projects. Those are not necessarily the same level of experience.

You can make the section more useful by briefly connecting software to actual work.

For example:

Revit: developed housing models and produced drawing information for academic and placement projects.

AutoCAD: prepared and revised architectural drawings during practice experience.

Rhino: explored early-stage form and complex geometry for university design work.

Now the reader knows what the software actually enabled you to do.

This is also where honesty matters. If you are researching a uk online architecture cv writing service, you will find plenty of advice about making software skills stand out, but no amount of clever wording can replace genuine familiarity with the tools.

If you have only opened a programme twice, do not present yourself as highly proficient.

A shorter list of software you can confidently discuss is far stronger than an impressive-looking list that falls apart when someone asks you about it.

4. Show That You Understand More Than the Final Image

Beautiful renders can make a portfolio memorable, but architecture is not only about producing attractive images.

A practice also wants to know whether you understand what happens between an idea and a building.

Think about the technical work you have genuinely been involved in.

It might include:

• developing construction details
• preparing planning drawings
• researching materials
• revising drawings after feedback
• producing technical information
• coordinating drawings
• considering environmental performance
• working with existing building information
• responding to comments from tutors, consultants or colleagues

You do not need to exaggerate your responsibility.

If you assisted with a drawing package, say so. If you developed a detail for a university project, explain that. If you helped revise drawings after feedback, mention the change.

There is something quite professional about being precise about where your responsibility began and ended.

It also prevents a common mistake: assuming that a strong design project automatically proves strong technical ability.

It does not.

Your CV should make the distinction clear.

5. Turn Job Titles Into Evidence of Responsibility

“Architectural Assistant” is useful information, but it is only a starting point.

A recruiter still needs to know what you actually did.

Look through each role and identify the work you were trusted with.

Perhaps you started by updating drawings and organising information. Later, you contributed to planning work, joined project discussions, developed drawing packages or communicated with other members of the team.

That progression tells a much better story than a paragraph saying you are a “hard-working team player with excellent communication skills”.

Generic claims are easy to write because they require no evidence.

Specific responsibilities are harder to write, but they carry much more weight.

The same applies to experience outside architecture.

A hospitality job does not need to be disguised as architectural experience. If it taught you to deal with difficult customers, manage pressure or coordinate with colleagues, say what you actually learnt.

The question is not:

“Can I make this sound architectural?”

It is:

“What does this experience prove about me?”

6. Make the CV and Portfolio Tell the Same Story

One of the best checks you can make before sending an application costs nothing.

Put your CV and portfolio next to each other.

Then read both as if you have never met the candidate.

Does the CV say you have strong technical experience, while the portfolio shows only finished renders?

Does it mention a collaborative project without explaining what you contributed?

Does Revit appear near the top of your skills, but none of the work shown demonstrates how you used it?

Does your CV emphasise residential architecture while the portfolio gives most of its space to something completely different?

These inconsistencies create unnecessary doubt.

Before sending the application, ask yourself:

• Can I find evidence for every important claim I have made?
• Is my personal contribution clear in group projects?
• Do my strongest projects support the type of role I want?
• Could I comfortably answer questions about every software skill listed?
• Does my CV add useful information rather than simply repeat my portfolio?

Do not spend an entire evening changing the typeface while ignoring these questions.

Content usually needs more attention than decoration.

7. Let the CV Grow With Your Career

Your architecture CV should change as you do.

For a recent graduate, university projects may take up a meaningful part of the document because they provide evidence of design thinking, software use and project development.

After a few years in practice, professional work should naturally become more prominent.

You may have gained experience across different project stages, worked with consultants, prepared technical information, attended meetings or taken ownership of particular tasks. Those details become more useful than projects from university that once occupied half the CV.

That is why there is no single architecture CV that you can write once and leave untouched for five years.

Review it whenever your responsibilities change.

Remove weaker evidence. Expand stronger evidence. Update software skills honestly. Replace old projects when newer work gives a better picture of your abilities.

Most importantly, resist the urge to make yourself sound more experienced than you are.

“Assisted with planning drawing packages for residential projects” is clear.

“Experienced in planning and project management” sounds bigger, but unless you can explain exactly what you managed, it creates more questions than it answers.

A good architecture CV does not need to make you sound like the finished article.

It needs to make your real experience visible.

Your degree shows where your training began. Your projects show how you approach design. Your software skills show what you can produce. Your technical work shows how far you can take an idea. Your employment history shows what other people have trusted you to do.

Put those pieces together properly, and the CV stops being a list of qualifications.

It becomes a clear account of what you have learnt, what you have done and what you are ready to take on next.