Crafting blueprints, but your CV doesn't stand out in the skyline? Elevate your credentials with this Architect CV example, created with Wozber free CV builder. Learn how to present your visionary skills to match job specifications, constructing a career as remarkable as your creations!

Architecture hiring usually turns on one practical question. Can you take a project from concept through documentation and coordination without losing the design intent, the schedule, or the client's trust? Your CV needs to make that visible through built work, drawing production, consultant coordination, and project outcomes, not through broad claims about creativity alone.
When the CV is tailored to the role, a hiring team can quickly see whether your background lines up with the studio's project flow, software stack, and level of client-facing responsibility. Wozber's free CV builder helps you shape that story into an ATS-compliant CV by aligning your wording with the job description, so your experience reads clearly as architectural design and project management experience rather than getting lost among generic design titles.
This section does more than identify you. For architects, it confirms practical details that affect hiring early, including location, portfolio access, and whether your title matches the level of work you are pursuing. Keep it clean and factual so the reader can move straight to your project record.
Use your full name in a clear, readable format. Architecture portfolios may carry more visual personality, but the CV header should stay straightforward so your name is easy to scan in a PDF, printout, or ATS-parsed profile.
Place "Architect" directly under your name if that is the role you are applying for. If your recent title was "Senior Architect" or "Architectural Designer," you can still use the target title when it accurately reflects your licensing level and scope of work. This helps position you for design, documentation, and project coordination work right away.
List a reliable phone number and a professional email address. Add your portfolio website when you have one, especially if it shows built projects, concept development, drawing sets, renderings, or client presentation work. For architecture roles, a portfolio link often carries as much weight as the CV itself.
If the employer asks for candidates in a specific city, include that city and state in your header. In the example, listing "New York City, New York" immediately answers a stated requirement and removes uncertainty about local availability for meetings, site visits, and office-based collaboration.
If you include a website or LinkedIn profile, make sure the project dates, titles, software, and credentials match your CV. A hiring manager reviewing an architect's application will notice inconsistencies in project scope, firm names, or licensure details very quickly.
Treat your contact block like a project title sheet. It should confirm who you are, where you work, and where your architectural work can be reviewed without creating friction.
Architect CVs are read for scope. Hiring teams want to know what kinds of projects you worked on, how far you carried them, what consultants or clients you coordinated with, and whether you improved schedule, budget, approvals, or documentation quality. Your bullets should answer those questions clearly.
Read the posting for the responsibilities that drive the role, then mirror that language where it reflects your real experience. Here, architectural design, project management, multidisciplinary coordination, client presentations, technical documents, and on-time delivery are the core themes. Those ideas should appear in your bullets through real project examples, not as a copied list.
Start with your most recent position and include firm name, title, and dates. This layout helps hiring managers track your progression from design support into project leadership, client communication, or senior technical responsibility. For architects, growth in project complexity matters as much as years of experience.
Each bullet should show what you produced or improved. Instead of saying you were responsible for design development, show what kind of projects you designed, how many, and what result followed. The example does this well by linking design work to a 95% approval rate and technical documentation to a 15% gain in construction efficiency.
Use numbers where they are natural to the profession: number of projects, approval rate, budget performance, drawing output, revision reduction, schedule improvement, or client engagement. Metrics help distinguish between someone who contributed to a project and someone who drove decisions. The sample's "20+ high-profile design projects" and "10% under budget" are strong models because they connect leadership to delivery.
Prioritise work that strengthens your case for design, documentation, coordination, construction-phase involvement, software proficiency, or client-facing communication. Older or unrelated jobs can be trimmed unless they explain a meaningful part of your architectural path. The section should read like a record of increasing responsibility in practice, not a full career history.
By the end of your experience section, the reader should understand the scale of your projects, the tools and teams you worked with, and the results you delivered from concept through construction documentation.
Education carries particular weight in architecture because accredited study is tied directly to professional qualification. This section should confirm the degree path that supports your practice and make it easy to see that you meet the posting's academic requirement.
If the posting requires a Bachelor's or Master's degree in Architecture, list that credential clearly and early. This role does exactly that, so your education section should not bury the degree title under extra information. Make the architecture qualification immediately visible.
Include degree, field of study, school, and graduation year. That is usually enough. For architecture, a clean format matters because hiring teams are often scanning quickly for accredited training before they move on to licensing, software, and project experience.
If you hold both a Bachelor of Architecture and a Master of Architecture, place the more advanced credential first. The example does this effectively by leading with a Master of Architecture, which reinforces seniority and academic depth without overexplaining.
Honors, thesis topics, study abroad work, or relevant coursework can be useful for early-career architects or specialised applications such as urban design, sustainability, or computational design. If you already have 5+ years of practice, keep this section tighter unless the extra detail directly supports the firm's work.
Additional training in sustainable design, BIM workflows, building codes, or construction administration can sit here or in certifications, depending on your CV structure. Mention it when it helps explain newer technical strengths or a shift in project specialization.
Your education section should confirm, at a glance, that your architectural training meets the role's baseline and supports the level of responsibility shown in your experience.
For architects, certifications are not filler. Licensure and recognized credentials can affect legal responsibility, project authority, and how quickly you can step into client-facing or documentation-heavy work. List the credentials that matter most to the role first.
When a posting names a license, lead with it. This role asks for an NCARB license or the ability to obtain one within 6 months, so that credential deserves top placement. If you are in progress, say so clearly and include the expected timeline where appropriate.
Architectural licensure, LEED accreditation, WELL, historic preservation, or code-related certifications can all be useful, depending on the firm's project mix. Prioritise the ones that speak to project delivery, compliance, sustainability, or the specialty area of the role rather than listing every course completion.
Add issue dates or active ranges for licenses and credentials that require maintenance. This helps the employer understand that your qualifications are current. In the sample, the NCARB license and LEED certification both show active date ranges, which strengthens credibility.
If your recent training reflects shifts in practice, such as BIM coordination, sustainable design standards, or advanced visualization tools, include it when it supports the job target. Architecture changes with regulations, software, and delivery methods, and your certifications can show that you have kept pace.
List credentials that change how you can contribute to a project team. For architecture roles, that usually means licensure, compliance knowledge, or specialised expertise that affects design and delivery.
This section should read like the toolset behind your project work. Hiring managers are looking for the software, coordination abilities, and communication strengths that support design development, drawing production, presentations, and team collaboration across project phases.
Start with the skills the employer names directly, then add closely related capabilities you genuinely use. In this case, AutoCAD, Revit, SketchUp, communication, presentation, collaboration, and project management all belong near the top because they map directly to the role's day-to-day work.
Software proficiency is often screened early, especially in firms with established BIM and documentation workflows. List tools such as AutoCAD, Revit, and SketchUp clearly, and add others only if they are relevant to the role you want. The example handles this well by pairing core software with related strengths like 3D visualization.
Architecture is collaborative work. A skills section that lists only software can make you look production-focused but not project-ready. Pair technical tools with abilities tied to real project flow, such as client presentations, multidisciplinary coordination, construction documentation, sustainable design, or project management.
Every skill should help explain how you design, coordinate, document, or present architectural work. If a skill does not strengthen one of those areas, it probably does not need space on the page.
Language ability matters in architecture when the work involves client meetings, consultant coordination, community engagement, or documentation in multilingual environments. Keep this section concise, but do include it when language proficiency supports communication on projects.
If the posting names English proficiency, list English clearly with an accurate level. That confirms you can handle meetings, presentations, specifications, and written coordination without ambiguity.
Choose straightforward labels such as Native, Fluent, Intermediate, or Basic. This gives hiring teams a realistic sense of how you can contribute in client conversations, consultant calls, or cross-cultural project work.
Additional languages can strengthen an application in cities and firms that work with diverse clients, consultants, and communities. In the example, Spanish adds practical value because it broadens communication range without distracting from the core architectural qualifications.
Do not overstate fluency. In architecture, small misunderstandings can affect client expectations, consultant coordination, and construction communication. Accurate language levels are more useful than ambitious ones.
For most architect CVs, languages are a supporting section rather than a headline section. Include them when they add real communication value, especially for public-facing, international, or community-oriented work, but keep the emphasis on design and project delivery.
List the languages that expand how you can communicate on projects. Done well, this section adds practical range without pulling focus from your architectural experience.
The summary should quickly establish what kind of architect you are, how much experience you bring, and where your strengths show up in practice. It works best when it connects design ability with delivery experience, software fluency, and the kinds of project results you have produced.
Start with your years of experience and your professional focus, such as architectural design, project management, technical documentation, residential work, commercial interiors, or large-scale mixed-use projects. Keep it specific enough that the reader can place you within the field.
Your first sentence should establish seniority and architectural identity in plain language. The sample's "Architect with over 9 years of experience" works because it sets the level immediately, then moves into design and team leadership rather than generic enthusiasm.
Choose two or three points that matter most for the opening you want, such as multidisciplinary coordination, client presentations, BIM software, sustainable design, or delivering projects on schedule and within budget. Pull these from the job description, but phrase them as strengths you have already demonstrated.
Aim for 3 to 5 lines. That gives you enough room to show experience, specialization, and one or two results without repeating the experience section. A concise summary helps the hiring manager quickly understand whether to expect a concept-focused designer, a technical architect, or a project lead.
After reading your summary, the employer should know your experience level, the kind of architectural work you handle, and why your background fits the demands of the role.
An effective architect CV makes your design judgment, technical documentation, software fluency, and project coordination easy to trace from section to section. Once those pieces line up with the job description, the application reads as someone who can contribute in studio reviews, client presentations, and live project delivery.
Use Wozber's free CV builder to tighten that alignment in an ATS-friendly CV format, and use the ATS CV scanner to check whether your language reflects the posting's requirements for licensure, software, and project management. The finished CV should make one thing clear. You can design well and deliver reliably.





