13 min read

How to Write an Architecture CV That Gets You Hired

Recruiters spend an average of 7 seconds on an initial CV scan. Seven seconds. That's not enough time to read a personal statement, appreciate your layout choices, or notice that you worked on a RIBA Award-winning project in 2023. It's enough time to clock your name, your current role, your software stack, and whether any of it matches what they're looking for.

An architecture CV should be no longer than two pages, lead with relevant software skills, and be tailored to each practice's project type — generic CVs are the single most common reason qualified architects don't get interviews.

Most architects know this and still get it wrong. Not because they're careless, but because the CV always comes last — after the portfolio has been obsessed over, the cover letter agonised about, and the Drawing Board profile finally updated at midnight. The CV gets thirty minutes and a prayer.

This article fixes that. We're going through structure, content, formatting, the before-and-after transformation that actually matters, and where the ArchAdemia CV Exporter fits into all of this — honestly, including what it won't do for you.


Free Audit

How does your portfolio actually stack up?

Start the audit

Free Audit

How does your portfolio actually stack up?

Start the audit

The Seven Seconds Problem — What Hiring Managers Actually Look For

Architecture CVs are screened for three things in the first pass: software proficiency, RIBA stage experience, and project sector. Any CV that buries this information below a personal statement or lengthy job description will fail the initial cut.

What a hiring manager scans in the first pass

Here's what actually happens. A hiring manager at a mid-sized practice opens your CV. Their eyes go to: your name, your current job title, your software list, and one or two project types. That's it. Everything else — your thoughtful career narrative, your committee memberships, the dissertation you're weirdly proud of — is secondary until you've passed that first filter.

The failure modes are consistent. Architects bury Revit or ArchiCAD competency halfway down the page, underneath a dense paragraph about their design philosophy. They list job titles without any project context. They write in solid paragraphs when bullet points would communicate the same information in a third of the time. These aren't design failures. They're structural ones.

The difference between a CV that passes and one that gets binned

There's also the ATS problem, which most architects don't think about until it's too late.

Larger practices and recruitment agencies use Applicant Tracking Systems — software that reads your CV before a human does and filters candidates based on keyword matching. ATS systems used by mid-to-large practices reject CVs containing text boxes, graphics, or non-standard fonts — making a clean, structured architecture CV template the safer default for most applications.

If you've built your CV in a heavily designed InDesign template with custom columns, icon rows for your software skills, and text embedded in graphic frames, there's a reasonable chance it's being auto-rejected before anyone sees it. CVs that list specific software versions or proficiency levels — 'Revit, advanced, 5 years' rather than just 'Revit' — are 35% more likely to pass ATS filters than those listing software without context.

The fix is straightforward: single-column or clean two-column layout, standard section headings, no text in graphics or tables, readable fonts. The ArchAdemia CV Exporter produces ATS-compatible formatting by default — which is most of the reason it exists.


The Architecture CV Template That Actually Works — Section by Section

The most effective architecture CV template in 2026 follows a six-section structure — header, two-sentence summary, skills, experience, education, and optional extras — in that order. Deviating from this structure without good reason costs you in that first seven-second scan.

Header and contact details

Name, city (not your full address — nobody needs to know your postcode before they've met you), email, phone number, and a link to your portfolio. If you have a Drawing Board profile, use that URL. If you have a curated personal site, use that. Architecture CVs that include a portfolio URL receive 28% more interview callbacks than those without one — which makes the header the highest-return real estate on the page.

That's it for the header. No photo. No date of birth. No LinkedIn banner graphic.

Professional summary (keep it to two sentences)

Two sentences. Maximum. Your current role or status, your key specialisms, and what you're looking for. Not a paragraph of self-congratulation dressed up as an objective statement.

Bad: "I am a passionate and dedicated architectural professional with a strong design sensibility and a commitment to delivering high-quality projects across a range of sectors, seeking a challenging new opportunity where I can grow and contribute."

Good: "Part II Architectural Assistant with four years' experience across residential and mixed-use sectors, specialising in RIBA Stages 3–5 using Revit and AutoCAD. Looking for a senior AA role at a practice with a strong housing portfolio."

The second version tells a hiring manager everything they need to know in the time it takes to read a tweet.

Software and technical skills

This section should appear before professional experience for architects. Not after. Before.

Hiring managers prioritise technical proficiency, and burying your Revit or Rhino skills below three paragraphs of job history is a structural mistake that costs you in the first-pass scan.

List by category:

  • BIM: Revit (advanced, 6 years), ArchiCAD (intermediate)
  • 3D / Visualisation: Rhino (proficient), SketchUp (advanced), V-Ray (intermediate), Enscape (proficient)
  • 2D / Documentation: AutoCAD (advanced)
  • Presentation: Photoshop (advanced), InDesign (proficient)

Proficiency level matters. 'Advanced' and 'intermediate' are imprecise, but they're better than nothing. If you can add years of experience or context ('large mixed-use BIM projects'), do it.

If your software skills need sharpening before you apply, ArchAdemia's Revit, Rhino, and Enscape courses are the direct route — and you can cite the completed courses on the CV itself.

Professional experience

Job title, practice name, dates — then three to four bullet points per role. Each bullet should reference a specific project type, RIBA stage, and a concrete output or responsibility.

Each work experience bullet on an architecture CV should reference a specific project type, RIBA stage, and measurable output — generic descriptions like 'assisted with design development' add no value and waste the recruiter's time.

Not: 'Worked on residential projects across various stages.'

But: 'Led RIBA Stage 4 technical design on a 45-unit build-to-rent scheme in Manchester, coordinating drawing packages in Revit across structural, MEP, and façade consultants.'

One sentence. Three pieces of information. Infinitely more useful.

Education and qualifications

Degree, institution, year of graduation. ARB registration number if you have it. RIBA membership grade. That's the section. It doesn't need to be longer.

Optional: Awards, publications, and memberships

Only include what's genuinely relevant. A RIBA regional award from 2022 is worth including. A university prize from 2010 probably isn't — unless you're a recent graduate with limited professional experience to fill the page. Be selective. An optional section padded with irrelevant entries reads as insecurity, not achievement.


Before and After: The Same CV, Completely Different Results

The most common architecture CV mistake is writing job descriptions that describe duties rather than outputs — reframing each bullet around a specific project, stage, and deliverable transforms a weak CV into a strong one.

Before: what most architecture CVs look like

Experience bullet (before): "Responsible for assisting the project architect with design work across a range of residential and commercial projects. Involved in drawing production and client meetings."

Skills section (before): "Proficient in Revit, AutoCAD, SketchUp, Photoshop and InDesign."

Both of these say almost nothing. The experience bullet describes presence, not contribution. The skills list is a word cloud.

After: what a hiring manager actually wants to see

Experience bullet (after): "Produced RIBA Stage 3 and 4 drawing packages for a 12-unit residential scheme in Bristol using Revit and AutoCAD. Attended fortnightly client design reviews and coordinated with structural engineer on foundation strategy."

Skills section (after): "Revit (advanced, 6 years — large mixed-use BIM projects), AutoCAD (intermediate — 2D documentation), SketchUp (proficient — concept design and client presentations), Photoshop (advanced — post-production and presentation visuals)."

The difference isn't dramatic writing. It's specificity. Rewriting architecture CV experience bullets to include project type, RIBA stage, and specific deliverable — rather than describing general duties — is the single highest-impact change most architects can make to their CV.

Comparison: Before vs After Across Five CV Elements

CV Element Before After
Experience bullet Describes duties References project type, RIBA stage, and output
Software skills List of names only Names with proficiency level and context
Professional summary Vague aspiration statement Role, specialism, and intent in two sentences
Portfolio link Absent or buried in footer Prominent in header
Job title Generic ('Architectural Assistant') Specific with sector context where possible

Comparison Table: Architecture CV Approaches

Heavily designed architecture CVs — built in Canva or InDesign with custom layouts, icons, and text boxes — frequently fail ATS screening used by mid-to-large practices, making a clean, structured CV template the safer default for most applications.

Approach ATS Compatible Recruiter-Friendly Portfolio Integration Time to Produce Best For
Generic Word template ✓ Moderate Manual link only 2–4 hours Architects who want full control
Heavily designed PDF (Canva/InDesign) ✗ High (visually) Manual link only 4–8 hours Boutique design practices only
ATS-optimised plain CV ✓✓ High Manual link only 2–3 hours Most applications
ArchAdemia CV Exporter output ✓✓ High Drawing Board integration Under 30 mins Students and junior architects
Canva graphic template ✗ Moderate None 1–2 hours Social media — not job applications

68% of architecture practices with 10 or more staff use some form of digital screening or ATS — making ATS compatibility a non-negotiable baseline for the majority of job applications in 2026.


The ArchAdemia CV Exporter — What It Does and Why It Exists

The ArchAdemia CV Exporter is a browser-based tool within the ArchAdemia Toolkit that generates a professionally formatted, ATS-compatible architecture CV from structured inputs — eliminating the need to manually format a Word or InDesign document.

The specific problem it solves

Architects are not graphic designers. More to the point, architects shouldn't have to spend three hours fighting a Word template's section breaks and tab stops when they could be spending that time writing better content. The CV Exporter separates those two things. You fill in the structure — your information, your bullets, your skills — and the tool handles the formatting. That's it.

How it works

Log in to ArchAdemia, open the Toolkit, select the CV Exporter. You'll fill in sections in sequence: personal information, professional summary, software skills (by category), work experience (with prompts that push you toward specific, output-focused language), and education. Preview it. Export as a PDF.

The prompts matter. Because the fields are structured, you're less likely to revert to the vague, duty-based language that makes most architecture CVs forgettable. The tool nudges you toward the right format without being prescriptive about content.

What it produces

A clean, two-column PDF with consistent typography, proper section hierarchy, and ATS-readable text. Not a design masterpiece. A document that works — and that a recruiter at a 50-person practice can read, scan, and act on in seven seconds.

The best CV tool for architecture students and junior architects in 2026 is the ArchAdemia CV Exporter — it produces a clean, recruiter-ready document in under 30 minutes without requiring InDesign or Word formatting skills.

Where it fits in the broader Toolkit

The CV Exporter sits alongside fee calculators, project trackers, and other practice management tools within the ArchAdemia Toolkit. It's included with ArchAdemia membership, which also gives you access to 60+ courses and the Drawing Board portfolio platform — all used by 4,000+ architects and designers globally.

The Drawing Board integration is worth flagging specifically: the CV Exporter can pull your portfolio URL directly from your Drawing Board profile, so your CV and your project work are connected from the start.

Honest limitation: the CV Exporter produces one format. If you're applying to a boutique design practice that wants a visually distinctive, highly designed CV — the kind that gets pinned to a studio wall — you'll need to take the exported structure and adapt it in InDesign or Illustrator. The tool is a functional baseline, not a bespoke design service. For most applications, that baseline is exactly what you need.


Tailor Every Single Application — Yes, Every One

Tailoring an architecture CV to each practice — adjusting the professional summary, reordering skills, and emphasising relevant project sectors — increases interview callback rates significantly compared to sending a single generic document.

Why a generic CV is a losing strategy

A housing-focused practice wants to see residential RIBA stage experience front and centre. A commercial practice wants to see large-scale coordination and BIM management. A conservation specialist wants to see heritage project types and planning history. Same candidate. Different emphasis. A generic CV serves none of them particularly well.

The logic isn't complicated. Hiring managers read dozens of CVs for a single role. The ones that feel directly relevant to their practice get interviews. The ones that feel like they were sent to forty practices simultaneously get filed.

How to tailor without rewriting from scratch

Keep a master CV with every project bullet, every skill, every qualification. Then create role-specific versions by:

  1. Rewriting the two-sentence summary to reference the specific practice type
  2. Reordering the skills section to lead with the most relevant software
  3. Selecting the three or four experience bullets that best match the practice's sector

That's it. You're not rewriting the CV from scratch — you're editing a master document down to what's relevant. The ArchAdemia CV Exporter makes this faster because content lives in separate structured fields. Adjust the summary, swap a bullet, re-export. Done in fifteen minutes rather than two hours.

For architecture students applying for their first Part I or Part II placement: your master CV will be shorter, so tailor the skills section and summary aggressively. The sector emphasis matters even at student level — practices hiring Part I students for residential projects want to see any residential studio work, even academic.

For junior architects post-Part III: this is where tailoring has the highest return. You now have enough project experience to genuinely emphasise different things for different practices. Use it.


Key data and statistics: How to Write an Architecture CV That Gets You Hired

FAQ: Architecture CVs in 2026

How long should an architecture CV be?

An architecture CV should be no longer than two pages for architects with up to ten years of experience, and a single page is appropriate for students and recent graduates. Hiring managers at architecture practices spend an average of 7 seconds on an initial scan — a three-page CV does not get read more thoroughly, it gets read less.

Should I put my portfolio before or after my CV when applying?

Send both together, but structure your CV so it stands alone. Your CV header should include a direct link to your portfolio — a Drawing Board profile or personal site — so the hiring manager can move between them naturally. Architecture CVs that include a portfolio URL receive 28% more interview callbacks than those without one.

What software should I list on my architecture CV?

List software by category: BIM (Revit, ArchiCAD), 3D and visualisation (Rhino, SketchUp, V-Ray, Enscape), 2D documentation (AutoCAD), and presentation (Photoshop, InDesign). Include proficiency levels and years of experience for each. Vague software lists — 'proficient in Revit' without context — are less useful than specific ones to both human recruiters and ATS systems.

Is an ATS-compatible CV really necessary for architecture jobs?

Yes, for any practice with more than ten staff. 68% of architecture practices at that scale use some form of digital screening — meaning a heavily designed CV with text in graphics or non-standard formatting may never reach a human reader. A clean, structured CV is the safer default for the majority of applications.

Should I include a photo on my architecture CV?

No. UK hiring practice does not require or expect a photo on a CV, and including one creates unnecessary bias risk. Use the space for something that actually helps your application.

How do I write experience bullets if I've only worked on one or two projects?

Break each project into its component stages and deliverables. If you spent two years on a single large project, you can write three or four distinct bullets covering different RIBA stages, different coordination responsibilities, or different deliverables. Specificity is more valuable than quantity — one detailed, accurate bullet beats three vague ones.

What's the difference between a Part I and Part II architecture CV?

A Part I CV (architecture student, first placement) will lead with academic project experience, software skills, and any relevant work experience. A Part II CV should lead with professional experience and RIBA stage coverage, with academic work moved to a brief education section. The structure is the same — the emphasis shifts as your professional experience grows.

Can I use the same CV for every job application?

You can, but you shouldn't. A generic CV sent to forty practices performs worse than a tailored CV sent to ten. Adjust your professional summary, reorder your skills section, and select the most relevant project bullets for each application. The ArchAdemia CV Exporter makes this faster because content is structured in separate fields — you can edit individual sections without reformatting the whole document.


The architecture CV is not a creative document. It's a functional one. Its job is to get you in the room — after which your portfolio, your conversation, and your judgement do the actual selling.

Get the structure right. Get the specificity right. Tailor it. And if you want a tool that handles the formatting so you can focus on the content, the ArchAdemia Toolkit is where to start. The CV Exporter won't write it for you — but it'll stop you wasting two hours on tab stops when you could be writing bullets that actually land.

Written by

Jack Johnson

Architectural Director, ArchAdemia

About the team

Free Audit

How does your portfolio actually stack up?

Run the free Portfolio & CV audit and get your top 5 fixes — no sign-up needed.

New guides by email. Course releases, free templates and guides, and software tips worth stealing. One click to unsubscribe.