How to Write a Resume for Architecture Jobs

Architecture is one of those fields where your resume has to do two things at once. It needs to read well as a document. And it needs to point toward your visual work without becoming a portfolio itself.

Most architecture resumes fail at this balance. They either read like generic corporate documents or try too hard to be design pieces. Neither approach works well in today's hiring process.

Here's how to write an architecture resume that actually gets you interviews.

The Architecture Resume Is Not Your Portfolio

This is the most common mistake. Architects are visual thinkers. So naturally, they want their resume to showcase design skills through layout, typography, and graphics.

The problem is that most firms use applicant tracking systems to screen resumes before a human ever sees them. A heavily designed resume with columns, graphics, and unusual formatting often gets parsed incorrectly by these systems. Your carefully placed project descriptions end up as garbled text in a database.

Keep the resume clean and readable. Save the design work for your portfolio, which you should link to from the resume. Your resume's job is to get past the initial screen and communicate your qualifications clearly. Your portfolio's job is to show your design sensibility.

That said, architecture firms do notice good typography. Use a clean, professional typeface. Keep margins consistent. Make sure the hierarchy is clear. You can demonstrate taste without breaking ATS compatibility.

Lead With a Focused Summary

Skip the objective statement. Instead, write a two to three sentence summary that positions you for the specific type of role you're targeting.

A summary for someone applying to a large commercial firm looks different from one targeting a residential boutique practice. Tailor this section for each application, or at least for each category of firm you're applying to.

A strong summary might read: "Licensed architect with eight years of experience in mixed-use commercial projects from concept through construction administration. Led design on three projects exceeding 200,000 square feet in the greater Chicago market. Experienced in sustainable design with two LEED-certified projects completed."

Notice what this does. It states the license status, the experience level, the project type, the scale, the market, and a specialization. All in three sentences. A hiring manager can immediately tell if this person fits what they need.

How to Describe Architecture Projects

This is where most architecture resumes fall short. People list projects they worked on without explaining what they actually did. "Worked on the downtown mixed-use development" tells a hiring manager almost nothing.

Every project description should answer three questions. What was the project? What was your specific role? What was the outcome or scale?

Here's the difference:

Weak: Assisted with design development on a residential project.

Strong: Developed design development documents for a 48-unit residential complex. Coordinated structural and MEP integration across 120 drawing sheets. Project completed on schedule with construction cost within 3% of estimate.

The strong version tells the reader exactly what you contributed, the scale of the work, and the result. This matters because architecture is collaborative. Firms need to know what you personally did, not just what projects your previous employer completed.

When describing projects, include the project type, the square footage or unit count, your phase involvement (schematic design through construction administration), and any measurable outcomes. Did the project come in on budget? Win an award? Achieve a sustainability certification? Include it.

Software Skills Matter More Than You Think

Ten years ago, listing software on an architecture resume was almost an afterthought. Today it's often one of the first things hiring managers scan for.

The reason is simple. Training someone on a new software platform takes months and costs money. If a firm runs on Revit and you've only used ArchiCAD, that's a real consideration in the hiring decision.

List your software skills in a dedicated section near the top of the resume. Group them by category:

BIM and Drafting: Revit, AutoCAD, ArchiCAD, SketchUp

Rendering and Visualization: Enscape, Lumion, V-Ray, Twinmotion

Adobe Creative Suite: Photoshop, Illustrator, InDesign

Project Management: Bluebeam, Procore, Newforma

Other: Rhino, Grasshopper, GIS

Be honest about your proficiency. If you've only done a few tutorials in Grasshopper, don't list it alongside Revit, which you use daily. Some people add proficiency levels, but this can backfire. What does "intermediate" in Revit mean? It's better to let your project descriptions demonstrate your depth with key tools.

One important note: firms care about BIM coordination skills, not just modeling. If you have experience managing Revit models across disciplines, setting up worksharing, or building Revit families, mention that specifically. These are harder skills to find than basic modeling.

Licensure and Credentials

Architecture is a licensed profession. Where you stand in the licensure process matters to employers, so make this clear.

If you're a licensed architect, put it right after your name at the top of the resume. "Jane Smith, AIA, LEED AP" is standard formatting. Include your license number and state if you have room.

If you're in the process, state it clearly. "ARE: 4 of 6 divisions passed" or "Completing AXP hours, expected licensure Q3 2026" tells an employer exactly where you stand. This is much better than leaving them to wonder.

LEED credentials, WELL AP, Passive House certification, and similar designations belong here too. The sustainable design space is growing, and these credentials carry real weight with firms that do green building work.

Education Section for Architects

Architecture is one of the few fields where your education section stays relevant well into your career. The school you attended, the degree type, and your thesis topic can all matter.

List your degree, school, and graduation year. If you attended a well-regarded program, this works in your favor. If your thesis or final project is relevant to the type of work you're seeking, include a one-line description.

Example: Master of Architecture, Rice University, 2018 Thesis: Adaptive reuse strategies for post-industrial waterfronts

The thesis line adds context and shows a specialization that certain firms would find valuable.

If you're early in your career, include relevant coursework or studio focuses. "Advanced digital fabrication studio" or "Urban housing studio" tells employers about your training in ways the degree alone doesn't.

Once you have seven or more years of experience, you can trim the education section to just the degree, school, and year. Your project experience speaks louder at that point.

Experience Structure

Architecture careers don't always follow a linear path. You might have worked at a large firm, then a small studio, then gone independent for a few years, then returned to firm life. This is normal in the profession and not something you need to hide or explain.

List your positions in reverse chronological order. For each firm, include the firm name, your title, the location, and the dates. Then describe your work in terms of projects and responsibilities.

If you held multiple roles at the same firm, list them separately to show progression. Going from Architectural Designer to Project Architect to Associate within one firm demonstrates growth.

For firm descriptions, a brief context line helps if the firm isn't well known. "A 30-person firm specializing in higher education and institutional projects" helps the reader understand the scale and focus of your experience.

What About Freelance and Independent Work?

Many architects do freelance or independent work at some point in their careers. This is legitimate experience and should be included.

List it as you would any other position. Give it a clear heading like "Independent Practice" or "Freelance Architectural Consultant" with the date range. Then describe the projects just as you would firm projects.

The key is to be specific about scope. "Provided freelance design services" is vague. "Designed and permitted three single-family residential projects ranging from 2,400 to 4,100 square feet" is concrete and credible.

If you did freelance rendering or BIM work for other firms, that's worth including too. It shows both technical skill and the ability to work independently.

The Portfolio Link

Every architecture resume should include a link to an online portfolio. This is non-negotiable in 2026.

Place the link in your contact information section at the top of the resume. Make sure it works, loads quickly, and is mobile-friendly. Hiring managers often check portfolio links from their phones during commutes.

If you're using Behance, Archinect, or a personal website, make sure the URL is clean and professional. "janesmitharchitect.com/portfolio" is better than a link with random strings of characters.

One thing to avoid: don't put portfolio images directly in your resume file. This bloats the file size, breaks ATS parsing, and usually doesn't look as good as you think it does on screen. A clickable link is the right approach.

Competitions, Publications, and Teaching

Architecture values intellectual engagement in ways that many other professions don't. If you've entered design competitions, published writing, or taught at a university, include these in dedicated sections.

For competitions, list the competition name, year, and result if notable. "AIA Small Projects Award, 2024" or "Finalist, Chicago Lakefront Ideas Competition, 2023" adds credibility.

Publications in architectural journals, guest lectures, and teaching positions show thought leadership. A hiring manager at a design-focused firm will notice these. A hiring manager at a production-focused firm may care less, so adjust based on where you're applying.

Keep these sections concise. Three to five items each is plenty. If you have an extensive publication list, include the highlights and note "Selected publications" as the section header.

Tailoring for Different Firm Types

A resume for a 200-person corporate firm should look different from one targeting a 10-person design studio.

Large firms want to see that you can work within systems. Emphasize BIM coordination, large team collaboration, client-facing experience, and project management skills. Mention experience with construction administration and consultant coordination.

Small studios want to see range and design sensibility. Emphasize your involvement across project phases, your ability to handle multiple projects at once, and any awards or recognition for design quality. These firms often want people who can do a bit of everything.

Developer clients want efficiency and cost awareness. If you're applying to work on the client side, emphasize your understanding of budgets, schedules, and the business side of building.

Read the job posting carefully and adjust your emphasis accordingly. You don't need a completely different resume for each application, but the summary and the ordering of bullet points should shift based on what each firm values.

Common Mistakes to Avoid

Listing every software you've ever opened. Stick to tools you can actually use productively on day one.

Using architecture jargon without context. "Developed parti for the scheme" makes sense to architects but not to every HR person who might screen your resume first.

Forgetting to mention project scale. Square footage, unit counts, and construction budgets give concrete context that generic descriptions lack.

Overdesigning the resume. Clean and professional beats clever and artistic when it comes to getting past screening software.

Not including your license status. Whether you're licensed, in progress, or not pursuing licensure, make it clear. Ambiguity here raises questions.

Make Your Resume Work Harder

Writing a good architecture resume takes time. You need to dig into your project history, quantify your contributions, and present them in a format that works for both software systems and human readers.

If you want to check how well your resume handles ATS parsing, Sira can analyze your resume against job descriptions and show you where the gaps are. It's particularly useful for catching formatting issues that might cause problems with applicant tracking systems.

The architecture job market rewards people who can communicate clearly about their work. Your resume is the first test of that skill. Make it count.