The Architecture CV Is Broken — Here's How to Build One That Actually Gets Read

The CV That Nobody Reads

Architecture CVs are rejected before a human being sees them — not because the candidate is underqualified, but because the document itself fails on two fronts simultaneously: it gets filtered out by automated screening software, and the rare ones that survive don't hold a hiring manager's attention for the ten seconds they actually get.

That's the problem. Not your experience. Not your portfolio. The document.

Architects are trained to communicate spatially and visually. Most of us can read a drawing, feel the weight of a section, and understand proportion intuitively. But somewhere between that training and the job application, that spatial intelligence either disappears entirely — producing a lifeless Word document that signals nothing — or it goes into overdrive, producing a beautifully typeset PDF that an applicant tracking system turns into scrambled gibberish before anyone's eyes land on it.

This article covers both the structural principles of a CV that actually works in 2026, and how ArchAdemia's CV Exporter takes the formatting decisions off your plate entirely. The goal isn't a perfect document. It's a document that gets read.

Why Architecture CVs Fail (And It's Not What You Think)

Architecture CVs fail for two distinct reasons: ATS rejection due to non-standard formatting and text embedded in graphics, and human rejection due to poor hierarchy and buried key information. These are separate problems that require separate fixes — and most candidates address neither.

The ATS Problem Nobody Warned You About

Applicant Tracking Systems are used by the majority of larger practices and every significant recruitment agency in the UK. They scan your CV before a human does. They are not sophisticated readers. They are looking for keywords in plain text, and they are remarkably bad at handling anything architects tend to do with documents.

Multi-column layouts confuse them. Text embedded in graphics is invisible to them. Custom fonts sometimes fail to parse. Tables with merged cells can cause the whole document to be read out of sequence. The result? Over 75% of CVs submitted to practices using ATS software are filtered out before a human reviewer ever sees them. That figure is widely cited across recruitment research and, anecdotally, consistent with what architecture recruiters report.

The brutal irony is that the more design work you put into your CV, the more likely it is to be rejected before anyone appreciates it.

The Over-Designed Trap

A beautifully crafted two-column CV with custom typography and a greyscale headshot might look extraordinary on screen. Feed it through an ATS and it comes out the other side as a block of nonsensical text with your name floating somewhere in the middle.

But the opposite problem is just as real. A plain Word document with no visual hierarchy, no clear sections, and a wall of text in Times New Roman signals something equally damaging: here is someone who cannot communicate visually. Which is, again, literally the job.

The sweet spot is a single-column layout with clear typographic hierarchy, legible section headings, and enough visual structure to hold attention — but built on a foundation that survives automated parsing. Clean, not clever.

(The same problem applies to portfolio PDFs, by the way — but that's a separate conversation.)

What Hiring Managers Actually Want to See

Architecture hiring managers prioritise software proficiency, RIBA stage experience, and project scale in the first ten seconds of reading — not personal statements, not objectives, and certainly not a paragraph about your passion for the built environment.

The 10-Second Scan Test

Here's what actually happens when a hiring manager picks up your CV for the first time: they scan the top third of the first page. They're looking for three things, in roughly this order — does this person do the kind of work we do, can they use the software we use, and have they operated at the right RIBA stages?

If none of those answers are immediately visible, the CV goes in the maybe pile. Maybe means no.

Software Skills: Stop Burying the Lede

Software skills should appear near the top of your CV. Not in a footnote. Not in a list at the bottom under 'Additional Skills'. Near the top.

In 2026 UK architecture job postings, the most commonly required software skills are Revit, Rhino, AutoCAD, Enscape, and V-Ray — roughly in that order for practices doing BIM-led work, with Rhino and Grasshopper climbing fast in design-led studios. If you have these, they need to be visible within the first glance. If a hiring manager has to hunt for your Revit proficiency, they won't.

What RIBA Stage Experience Actually Signals

RIBA stage experience is shorthand that tells an experienced reader exactly where you've operated without you having to explain it. 'Stages 1–4' tells a practice you've been through design development and planning but haven't run a project through construction. 'Stages 4–6' tells them you're comfortable on site. Include it explicitly, per project if possible — not implied, not buried in a project description.

Project scale matters too. Residential, commercial, mixed-use, infrastructure — these signal fit for specific practice types. A practice specialising in large-scale commercial work wants to know you've worked at that scale. Don't make them infer it.

ARB registration and RIBA membership should appear in the header or first section of your CV — not buried in a credentials list at the bottom. These are binary qualifications that directly affect shortlisting. Make them impossible to miss.

Part III candidates: flag your status clearly and prominently. Practices hiring at that level need to know immediately whether you're registered or in progress.

Before and After: What a Broken CV Looks Like vs. One That Works

The most effective architecture CV in 2026 leads with software skills and RIBA stage experience, uses a single-column ATS-compatible layout, and runs to no more than two pages. The table below shows exactly what separates a CV that gets filtered out from one that gets shortlisted.

The pattern across every row is the same: architects default to design decisions that serve their own aesthetic preferences rather than the reader's practical needs. A CV is not a portfolio piece. It is a functional document. The moment you treat it like one, it starts working.

The ArchAdemia CV Exporter: Built for Architects, Not Generic Job Seekers

ArchAdemia's CV Exporter generates ATS-compatible architecture CVs using input fields designed around RIBA stage conventions, software proficiency, and UK practice hiring expectations. It's part of the Toolkit suite — and unlike every generic CV builder you've ever abandoned halfway through, it actually speaks the language of architecture practice.

What It Actually Does

The CV Exporter works through guided input fields that prompt for the things an architecture CV specifically needs: software proficiency with context fields, RIBA stage experience per project, project type and scale, ARB registration status, RIBA membership, and qualifications mapped to Part I, II, and III. You fill in the fields. It handles the structure, hierarchy, and formatting. What comes out is a clean, single-column document that survives ATS parsing and reads clearly to a human.

No agonising over column widths. No deciding whether your name should be 18pt or 24pt. No rebuilding the whole thing from scratch when you want to tailor it for a different practice type.

The output formats are exportable in formats that survive automated screening — which means the work you put into the content actually reaches a human being.

The Concrete Use Case: From Blank Page to Shortlist-Ready in Under an Hour

Here's a realistic scenario. A Part II Architectural Assistant has spent three years at a small residential practice. They're applying to a mid-sized commercial firm for the first time. The problem: their CV is built around residential projects, their Revit skills are buried in a list at the bottom, and their RIBA stage experience isn't explicitly stated anywhere.

Using the CV Exporter, they work through the input fields in sequence. Software skills go in with context — 'Revit (BIM coordination, residential new-build, linked models up to 150MB)' rather than 'Revit (intermediate)'. RIBA stages are attached to each project. The commercial firm can now see, immediately, that this candidate has operated from Stage 1 through to Stage 5 on multiple projects, even if those projects were smaller in scale.

The whole process takes under an hour. The output is a document ready to submit.

What It Doesn't Do (Honest Bit)

The CV Exporter produces structure and format. It doesn't write your project descriptions for you. It doesn't guarantee a shortlist. And it won't compensate for a thin portfolio — because the CV gets you the interview, and the portfolio closes it. If your portfolio needs the same treatment your CV just got, The Drawing Board is the platform built for that.

If you're genuinely stuck on how to describe a project — what language to use, how to frame your contribution — Corb, ArchAdemia's AI assistant, can help you draft that language. It's a brief mention here because it's a brief use case. But it's worth knowing it exists.

ArchAdemia's Toolkit is used by over 4,000 architects and designers globally. The CV Exporter sits alongside fee calculators and project trackers — all built for architecture practice contexts, not generic professional use.

The Architecture-Specific CV Rules Nobody Tells You

UK architecture practices expect a maximum two-page CV regardless of experience level — a longer CV signals poor editorial judgement rather than comprehensive experience, and editorial judgement is a design skill.

Two Pages. Non-Negotiable.

Students and Part I candidates: one page is fine, and probably appropriate. Part II and above: two pages. Post-Part III with fifteen years of experience: still two pages. Edit with the same ruthlessness you'd apply to a drawing that's trying to say too much. If it's on the CV, it needs to earn its place.

The instinct to include everything — every project, every software tool you've touched, every committee you sat on — is understandable. Resist it. A CV that's trying to be comprehensive is a CV that's failing to communicate.

Your Software List Is Your First Portfolio

The specific tools you list and the proficiency level you claim tell a practice what projects you can walk onto on day one. Vague proficiency claims are worse than useless — they're actively suspicious.

'Revit (BIM coordination, large-scale mixed-use, linked models)' tells a hiring manager something real. 'Revit (advanced)' tells them nothing except that you think you're good at Revit. Be specific. Be honest. If you want to strengthen your actual Revit skills before applying, ArchAdemia's Revit BIM Collaboration course covers exactly the coordination workflows that larger practices want to see.

The same logic applies to every tool. 'Rhino + Grasshopper (parametric facade studies, competition work)' signals something specific about the kind of projects you've worked on and the kind of practice you'd fit into.

The Covering Letter Is Not Dead — It's Just Misused

Most architects write a generic covering letter and send it to every practice. The ones that work are specific. Name the practice. Reference a project they've built — not their general ethos, an actual project. Explain in one sentence why your experience is relevant to that project type. Three paragraphs maximum. That's it.

A few other things worth stating plainly:

LinkedIn alignment. Your CV and LinkedIn profile should tell the same story. Recruiters cross-reference them. Inconsistency is a red flag.

File naming. 'CV.pdf' is not a file name. 'FirstnameLastname_CV_2026.pdf' is. It takes five seconds and it signals attention to detail — which is, again, literally the job.

Tailoring. One CV does not fit all practices. A heritage specialist practice wants different signals than a parametric design studio. The CV Exporter makes it fast to produce tailored versions without rebuilding from scratch each time.

Where the CV Fits in the Bigger Picture

The CV is a door. It gets you into the room. What happens in the room — and whether you get the job — depends on what comes next.

For students, the CV is often the weakest part of an application because it's the least taught. Architecture schools spend years teaching you to design and almost no time teaching you to present yourself professionally. The result is graduates with strong work and broken documents. ArchAdemia's employment-focused resources exist specifically to close that gap.

The CV is also a living document. Update it after every project completion. After every new software skill. After every RIBA stage crossed. Don't leave it until you're desperate — a CV written under pressure, when you need a job immediately, is never as good as one maintained steadily over time.

If your portfolio needs the same structural thinking your CV just got, The Drawing Board is built for exactly that — a platform designed for architects to present work in a way that's both visually coherent and professionally credible.

And if you want to make the software skills on your CV genuinely reflect what you can do — rather than aspirationally listing tools you've barely touched — ArchAdemia's 60+ courses cover everything from Revit for beginners to Enscape to Grasshopper. The CV gets you the interview. The skills get you the job. Make sure you actually have both.

Start with the ArchAdemia Toolkit. Get the CV right. Then make sure everything behind it is worth the attention you've just earned.

Frequently Asked Questions