Orchestrating designs, but feel your CV's blueprint is out of sync? Scroll through this Architect Project Manager CV example, created with Wozber free CV builder. Learn how to present your project leadership and architectural acumen to align with job criteria, building a career as visionary and structurally sound as your constructions!

Architect Project Managers are expected to carry two kinds of responsibility at once: design quality and project delivery. Hiring teams want to see that you can move a project from concept through construction documents without losing control of budget, schedule, consultant coordination, or code compliance. Your CV should make that operating range visible quickly, with concrete examples of projects led, teams coordinated, and outcomes delivered.
Screening for this role often gets crowded by adjacent profiles, especially candidates who are strong in design but lighter on project leadership. A tailored CV, built in Wozber's free CV builder with solid ATS optimisation, helps separate architectural design experience from true project management scope by showing where you owned phases, approvals, budgets, client communication, and multidisciplinary coordination. That distinction is what hiring teams need to grasp early.
This section is brief, but it still does real work. For an Architect Project Manager, it should confirm professional identity, make contact easy, and address any practical requirement that could affect availability, such as location.
Lead with your full name, then place "Architect Project Manager" directly underneath. That immediately frames your background around both architecture and project ownership, which matters for roles that sit between design leadership, client communication, and delivery control.
Use a professional email address, a reliable phone number, and links that are active. If you include a portfolio or LinkedIn profile, make sure the work shown supports the role you want, especially project types, drawing packages, BIM-based coordination, or leadership on real delivery milestones rather than only conceptual design images.
Some postings include a firm location filter before anyone gets to your experience. Here, the New York City requirement is explicit, so listing New York City, New York in your header removes uncertainty right away. Treat location like a tailoring point, not a universal rule for every Architect Project Manager CV.
A digital portfolio can help if it shows the kind of work the employer is hiring for, such as mixed-use, commercial, residential, or institutional projects, along with your role in design development, consultant coordination, or documentation. If the link is thin, outdated, or hard to navigate, leave it out until it supports the story your CV tells.
You do not need to include a full street address, photo, age, or other nonessential details. For this profession, the useful basics are your name, title, contact information, and any practical requirement the employer named, such as location. Keep the header efficient and professional.
Your header should confirm who you are, how to reach you, and whether you meet any stated logistical requirement. Once that is clear, the reader can focus on your project record.
This is the section that usually decides whether an Architect Project Manager CV holds attention. The hiring question is straightforward: have you led architectural work through real project phases while managing the operational side well enough to deliver?
Prioritise positions where you owned both design progress and project execution. Hiring teams want to see involvement in conceptual, schematic, and detailed design, but also budget oversight, schedule control, consultant coordination, and client-facing decision-making. If your earlier work was more design-heavy, show how it built toward project leadership rather than listing it as isolated production work.
Use bullet points that reflect how the work is actually done. For this role, that means phrases tied to design phase leadership, resource planning, consultant integration, code review, drawing approval, and stakeholder communication. The example CV does this well by showing ownership across more than 40 projects and linking that scope to design standards, compliance, and delivery results.
Architect Project Managers are evaluated on scope and control, so numbers matter. Include project counts, portfolio value, budget variance, on-time delivery, client satisfaction, team size, or cost savings from better coordination. Metrics like a $20 million annual portfolio, 98% client satisfaction, or 20% project cost savings give hiring teams a fast read on scale and performance.
This role rarely succeeds through architectural skill alone. Your bullets should show collaboration with structural, MEP, civil, interiors, contractors, and client teams, especially where you resolved conflicts, aligned documents, or kept the project moving through reviews and approvals. That is a stronger signal than simply saying you are a good communicator.
Be precise about what you led, approved, reviewed, or directed. "Supported design development" reads very differently from "led schematic design and approved construction document sets." In the sample, reviewing and approving more than 100 designs and specifications clearly communicates authority, which is exactly the distinction employers look for in project management architecture roles.
Your experience section should make it easy to see project phase ownership, delivery discipline, and coordination range. If the reader can picture you running workstreams, guiding teams, and keeping projects compliant and on track, this section is doing its job.
For architecture roles, education is not a formality. It confirms the academic base behind your design training and often helps establish credibility before the reader gets into project leadership and technical depth.
List your Bachelor's or Master's degree in Architecture clearly, since that is a stated requirement here and a common baseline across many architecture positions. If you hold both, present them in reverse chronological order so the highest or most recent degree appears first.
Include the degree, field, school, and graduation year. There is no need to overbuild this section unless you are early in your career. For an experienced Architect Project Manager, clarity matters more than detail.
A Master's degree in Architecture can reinforce depth in design training, research, or technical development, especially for senior project roles. In the example, the Master's degree helps support a progression into higher-level design and management responsibility, though it is the experience section that carries most of the hiring weight.
Most mid-career candidates can skip coursework unless it directly supports the job, such as building systems, construction documentation, urban design, sustainability, or project delivery methods. If you do include it, make sure it adds context that your experience section does not already cover better.
Academic distinctions can be useful if they are notable and still relevant to your professional story. That is especially true for candidates with fewer years of project management experience. For seasoned applicants, keep honors concise so the section stays focused on the credential itself.
Your education should confirm that you meet the architectural baseline without distracting from your delivery record. Once that is established, the rest of the CV can concentrate on how you lead projects in practice.
Certifications are not always mandatory for Architect Project Manager roles, but they can sharpen the profile, especially when they reinforce documentation, delivery discipline, or formal project management training.
Start with certifications that support the responsibilities in the posting. PMP and CDT are strong examples because they connect directly to scheduling, coordination, documentation, and project controls. If you hold licensure or other architecture-related credentials relevant to the role, include those too.
A short, role-matched certifications section is stronger than a long list of marginal coursework badges. Choose items that help explain why you can manage scope, documentation quality, consultant coordination, and delivery risk in an architectural setting.
If a certification is active, include the date or status in a clean format. Current credentials signal that your knowledge is maintained, which is particularly useful when the role touches code compliance, construction documentation, or formal project management standards.
A credential supports your case, but it will not compensate for vague project history. The sample CV works because the PMP and CDT sit alongside measurable delivery results, not in place of them. That is the right balance.
Relevant certifications can add weight to your project leadership story, especially when they align with how you manage schedules, documentation, and multidisciplinary execution.
The right skills section helps hiring teams scan for technical and managerial coverage fast. For an Architect Project Manager, that usually means BIM proficiency, drawing tools, coordination ability, and the communication skills needed to guide clients, consultants, and internal teams.
Start with the skills the employer named explicitly, then add closely related ones you genuinely use. Here, BIM software, Revit, AutoCAD, communication, leadership, and multidisciplinary collaboration all deserve space because they connect directly to the work described.
Do not let the section read like a design software inventory only. Pair technical tools with project management capabilities such as budgeting, scheduling, consultant coordination, code review, construction documentation, and client presentations. That combination reflects the role more accurately than either category alone.
Group or trim skills that do not support the target job. In the example, Revit, AutoCAD, BIM, leadership, and communication are highly relevant, while broader design tools matter only if they contribute to project delivery or presentation in the jobs you are targeting. Every skill listed should help explain how you run architectural work.
This section should read like the toolkit of someone who can lead design teams, coordinate technical work, and keep projects moving. If it looks balanced between architecture and delivery, it is aligned.
Language skills matter most when they affect communication on projects. In architecture and project management, that can include client meetings, consultant coordination, presentations, documentation review, and collaboration across diverse teams.
If the posting specifies English competence, list English at the top with an honest proficiency level. For a role that involves client communication, contractor coordination, and approval workflows, that requirement is practical, not decorative.
Additional languages can be useful if you work with multilingual clients, consultants, communities, or project teams. Spanish, for example, may strengthen communication on certain projects, but it should remain a supporting asset rather than the focal point of the section unless the role specifically requires it.
Use clear levels such as Native, Fluent, Advanced, or Conversational, and avoid overstating your ability. Language claims can be tested quickly in interviews or client-facing settings, so precision matters.
If a second language has helped with stakeholder meetings, site coordination, or cross-border project work, that context can be useful elsewhere on the CV or in a cover letter. Here, the section itself should stay concise and factual.
For most Architect Project Manager CVs, languages are a secondary section. Include them if they add practical value, but keep the emphasis on project leadership, technical tools, and delivery outcomes.
List the languages you can truly use in professional settings, with English clearly established where required. That is enough to support the rest of your application.
Your summary should quickly answer the question behind the role: what kind of architectural projects have you led, and how much project management responsibility have you carried? This is where you frame your seniority before the reader reaches the details.
Start with your professional identity and years of experience in architecture and project management. For this kind of role, a line such as "Architect Project Manager with 11+ years in architectural design and delivery" gives immediate context and aligns with the requirement for deep experience.
Reference the phases or scope you handle, such as conceptual design through construction documents, consultant coordination, client management, or code-compliant drawing review. That tells the reader where you operate in the project lifecycle.
Include concrete outcomes that fit the profession, such as on-time delivery, budget control, client satisfaction, project volume, or multidisciplinary coordination. The sample summary is effective because it combines experience length with project leadership, budget and timeline control, and client-facing collaboration.
Aim for three to five lines with direct language. Avoid broad claims about passion or vision if they are not tied to actual project work. The summary should feel like a concise executive snapshot of your design leadership and delivery capability.
A focused summary helps the reader place your experience at the right level from the start. By the time they move into your bullets, they should already understand that you can lead architectural work and manage the project realities around it.
An effective Architect Project Manager CV shows more than design talent. It connects project phases, budget ownership, consultant coordination, client communication, and code-aware documentation into a clear record of delivery.
Use Wozber's free CV builder to organise that story in an ATS-friendly CV format, then refine it with the ATS CV scanner so the language of your CV matches the role you want. When the tailoring is done well, hiring teams can quickly see whether you are ready to lead architectural projects from concept to completion.





