Architect CV: show design, documentation and licensed practice

Open with a short summary that states the project types you know—housing, education, workplace, healthcare, civic, cultural or adaptive reuse—and your role, such as project architect, job captain, designer or design lead. Mention schematic design through construction documents, consultant coordination, permitting support or construction administration when those phases are accurate.

Place licensure where a reviewer can find it quickly: registered or licensed architect, NCARB or equivalent record, examination progress, or designer title used honestly in your jurisdiction. Mirror posting language only when it matches work you have done. Claiming stamp authority, a lead designer role or construction-administration ownership without examples invites a hard interview. Leave site civil design, earthwork, drainage modeling and structural calculation ownership to the civil engineer CV unless you truly coordinated those consultants rather than performing the engineering.

Strong architecture bullets name the building type, your scope and a result. Include program or area, design phases, drawing or specification packages, review or permit cycles, coordination with structural, MEP or civil consultants, cost or schedule constraints, and construction-phase duties such as submittals or site meetings. Prefer measured outcomes—a package that cleared a planning or building-department review, fewer coordination clashes, a value-engineering change that preserved the design intent—over vague claims that you “designed the building.”

The fictional examples below illustrate wording only. They are not Make.CV performance claims and should not be copied as your own. Replace every figure with results you can support from drawing sets, meeting notes or permit logs. If client or project names are restricted, describe typology, scope and outcome without identifying the client or exact address.

Group skills into readable categories such as design and documentation, BIM and drawing production, codes and accessibility, consultant coordination, and construction administration. Prioritize tools named in the posting when you have genuine experience. A short accurate list of Revit or the BIM platform you actually used, drawing and specification workflow, and familiarity with building codes, zoning and accessibility requirements beats a long inventory of every rendering plugin you opened once.

Tie important tools back to experience bullets. Saying you own a Revit model is more convincing when a bullet explains the package, the consultants you coordinated and what changed after review. Link a portfolio only when the work may be shared and the file or site is current; label unbuilt, academic or competition work honestly. Do not present site engineering, civil grading or structural analysis as your own design work if your role was architectural coordination.

Use a readable template with standard headings so licensure, typologies, project roles and tools stay easy to find. Keep dates consistent and leave room for quantified bullets and a single, clearly labeled portfolio link. Browse Make.CV templates if you want to compare layouts before writing.

Build your CV in the free maker with live preview, then download a PDF with no watermark. Check that project names, registration credentials and portfolio URLs wrap cleanly. Confirm the exported text remains selectable before you submit.