Project Architect Resume Example

Centre your CV on end-to-end project delivery: At this level, employers expect evidence that you have taken projects through multiple RIBA stages (ideally 1-6) with accountability for programme, budget, and quality. Name specific projects, their values, and your delivery role.

Highlight design leadership and authorship: Distinguish between projects where you were the design lead versus a contributor. Use language that signals ownership - 'led design development', 'authored planning submission', 'directed technical package' - rather than generic participation.

Demonstrate consultant and contractor coordination: Reference your experience managing multidisciplinary consultant teams (structural, MEP, landscape) and contractor relationships during construction phases. Coordination competence is a primary concern for hiring firms at this stage.

Include licensure and professional membership status: State clearly if you are a registered architect (ARB, AIA, or equivalent) or a RIBA Chartered Member. If you are working toward registration, note expected completion date.

Show mentorship and team development activity: Mention any formal or informal responsibility for supervising Part I/II students or junior designers. Leadership of others, even at small scale, signals readiness for senior progression.

Burying project accountability under vague team language: Phrases like 'involved in delivery' or 'part of the project team' obscure your actual level of responsibility. At project architect level, you should be stating clearly that you held accountability for specific stages, consultant packages, or client relationships - not that you participated.

Failing to reference RIBA stages or equivalent delivery frameworks: Experienced hiring managers want to know exactly which stages you have led end-to-end. A CV that lists projects without stage breakdown leaves readers guessing about the depth of your delivery experience.

Omitting registration or licensure status: Many project architect candidates are partway through or have recently completed professional registration. Leaving this off the CV - especially if you are now fully registered - is a missed opportunity. Registration removes a barrier to managing regulated work independently.

Listing too many projects without enough depth: A CV that mentions twenty projects with one-line descriptions tells less than a CV that details six or seven projects with clear stage information, your role, and a headline outcome. Quality of evidence beats quantity of credits.

Not addressing technical coordination experience explicitly: Project architects who have managed complex multi-consultant coordination (IFC issue cycles, coordination models, contractor RFI management) should say so directly. This experience is highly valued and often assumed rather than stated on CVs.

Frame your experience around project delivery, not just design: Project architects are accountable for schedule, budget, and consultant coordination. Describe specific projects you delivered from schematic design through construction administration, noting the scale, budget, and your precise role at each phase.

List the building types and codes you know: Mention familiarity with IBC, ADA, NFPA 101, local zoning ordinances, or jurisdiction-specific requirements. Code literacy is a differentiator at this level and demonstrates that you can carry a project without constant supervision.

Include licensure status clearly: State whether you are a licensed architect (RA or AIA member), are in the AXP program, or hold a LEED or WELL credential. Place this near the top of your CV so it is immediately visible.

Describe how you managed consultants and subconsultants: Name the disciplines you coordinated, such as structural, MEP, civil, and landscape, and explain how you organized drawing sets, RFI responses, or submittal reviews. This is core to the project architect role.

Highlight construction administration experience: CA is often undersold on CVs. Note the number of site visits you conducted, the types of issues you resolved, and any change order or punch list management experience. Firms hiring project architects want someone who can close a project, not just design one.