Architect Resume Format, with 3 Full Samples

The format that works for architect resumes in India

Reverse chronological is the layout to use. Put the most recent role first, work backwards, and let the dates sit in plain view. Functional resumes that group everything under Areas of Expertise and quietly drop the dates read as an attempt to hide a gap, and reviewers treat them that way. A gap is better explained in one honest line than buried. An architect's resume is not the portfolio, and confusing the two is the most common mistake in this field. The resume is a one or two page text document that gets you shortlisted; the portfolio is where the design work is judged. Keep the resume clean and text-first, and link the portfolio in plain text. Do not try to cram thumbnails into the resume, because they bloat the file, break the parser and still do the portfolio no justice. Length is decided by evidence. One page holds everything a fresher and most architects up to roughly six years have to say. Past that, a second page is fine when it carries real project delivery rather than a longer software list. Four things belong nowhere here: a photograph, date of birth, marital status and father's name. They survive from an older template that circulated through campus placement cells. Send a PDF unless the posting asks otherwise, name the file with your own name and the role, and use a single column so the parser reads it cleanly. The table below sets out the section order.

The portfolio link a resume cannot replace

No architect is hired on the resume alone. Design ability is judged from the portfolio, so the resume's job is to earn the click through to it and to prove the parts a portfolio does not show: delivery, coordination, approvals and the ability to get a drawing built. Treat the two as a pair. The resume is the argument for a shortlist; the portfolio is the evidence of taste and skill. Put the portfolio link in plain text near the top, on Behance, Issuu or your own site, and make sure it opens. A dead link or a request-access page is worse than no link, because it reads as carelessness on the one document meant to show your attention to detail. Keep the portfolio itself tight: ten to fifteen strong pages beat forty that dilute the good work. What the resume adds, and the portfolio cannot, is scope and delivery. A gorgeous render says nothing about whether the building was ever built, on time, within budget, and through its approvals. The bullets in the samples deliberately carry that: opened on the committed date, cleared sanction without a resubmission, cut RFIs by resolving clashes early. A practice hiring a project architect wants exactly this, because they already assume you can make a pretty image. Never paste low-resolution thumbnails into the resume PDF to double as a portfolio. They inflate the file past email limits, confuse the applicant tracking system, and represent your work at a size that flatters nothing. Link, do not embed.

Click your own portfolio link from a private browser window before you send the resume. If it asks for access or 404s, you have just failed the one test an architect's resume must pass.

Writing a summary a hiring manager actually reads

The block under your name is the part you can be reasonably sure gets read, so it should carry three facts: what you design and deliver, how long you have been doing it, and the strongest thing you have built or led. Three or four lines, no adjectives that cannot be checked. The old objective line, seeking a challenging position in a reputed firm to utilise your design skills, tells the reader nothing they did not assume from the application. Replace it with a summary. An objective describes what you want, a summary describes what you have already delivered, and only one is evidence. Freshers often believe they have nothing to summarise. Look at the fresher sample: it names the software, states the internship length, cites COA registration, and points at a thesis that reached construction detail. That is a genuine summary built from coursework, one internship and a thesis. What it avoids is "creative and passionate architect", a phrase so common it now carries no information. A practical test: read your summary and ask whether a classmate with the same B.Arch could paste it onto their resume unchanged. If they could, it describes the degree, not you. Add the specific project, the specific scale and the specific ownership until it stops being transferable.

Experience bullets: verb, project, consequence

Every strong bullet in the samples follows the same shape. It opens with an action verb, names the specific project or drawing scope you owned, and closes with what measurably moved. The verb establishes that you did it. The project tells a reviewer the scale and type. The number, or the delivery outcome, does the persuading. Start with the outcome and work backwards. Architects usually write the task first, then leave it vague, which produces bullets like "worked on design and drawings for various projects". Instead ask what actually happened: a building opened on date, a sanction cleared without resubmission, RFIs fell because clashes were caught early, an area was delivered within budget. Then write the sentence that ends in that fact. Architecture rewards a specific kind of metric: built-up area, project value, programme and budget adherence, RFI and clash counts, approval cycles. "Delivered a 4.5 lakh sq ft development within budget and programme" carries the scale and the delivery in one line. Vary the metric so the resume does not read as one number repeated. Where you genuinely lack a number, give scope: how many projects, how many drawing sets, how many site queries closed, how many approvals cleared. "Cleared a G-plus-8 project through sanction without a resubmission" is a real, checkable claim. Allocate bullets by recency. Current role gets five or six, the previous role four or five, anything older two or three.

If a bullet would read identically on a classmate's resume, it is describing the studio, not you. Rewrite it until it only fits the project you actually ran.

The software and skills section: grouped, honest, defendable

An architect's skills section has two audiences with opposite preferences. The parser wants literal terms it can match, Revit and AutoCAD and IGBC. A human wants a short, organised list that signals what kind of architect you are. Grouping satisfies both. Group by function rather than one long line. BIM and drafting, visualisation, documentation and codes is a grouping that works for most architects. The exact headings matter less than the fact that structure exists. Write software the way the vendor writes it: Revit not Rivit, SketchUp not Sketchup, AutoCAD not Autocad. A parser matches on strings. Name the software you actually work in daily and can be tested on. Revit is now the expectation for most practices doing serious documentation, so if you have it, lead with it. Rendering skill, Enscape, Lumion or V-Ray, matters for design-facing roles and less for documentation-heavy ones. Match the emphasis to the job. Twelve to sixteen skills is the working range. Below eight the section looks thin. Above twenty it stops being a signal. The list is a contract: every item is a question you have agreed to answer. Do not include a proficiency bar. Let the portfolio and the project bullets prove the depth instead.

Projects and thesis: what to include and how to describe it

For a fresher, projects and the thesis are the resume alongside the portfolio link. They sit above experience, they get real space, and they are where a reviewer decides whether you can take an idea to a buildable proposal. For an experienced architect, key projects move below experience and become the built work you led, described by scale, type and your role. The common failure is describing the software or the style instead of the architecture. "Designed a residential project using Revit and SketchUp with a modern aesthetic" tells a reviewer nothing. Describe the site, the design problem, and what your resolution achieved. The thesis in the fresher sample is a strong entry because it names a real constraint, incremental affordability, and shows the idea was taken to construction detail and costing, not left at the pretty stage. Pick projects that show range: one design-led studio project, one thesis or research project taken to depth, and one documentation or measured-drawing exercise that proves technical ability. A studio that hires a junior wants to see both the idea and the drawing behind it. For experienced architects, name your role on each project explicitly. "Project architect" versus "part of the design team" tells a reviewer whether you ran the drawing set or contributed to it, and inflating that is the fastest way to lose credibility in an interview where the project is discussed in detail.

Where education, registration and certifications belong

Education goes at the bottom for anyone with a job, and near the top for a fresher. B.Arch, institution, years, and the M.Arch above it if you have one. That is the core entry. The Council of Architecture registration is not an ordinary certification: in India, only a COA-registered person may legally use the title Architect and offer architectural services. So the registration line matters more than any software certificate, and for a fresher it belongs high, near education or the header. If you are registered, say so. If you are not yet, do not call yourself an Architect on the resume; use a title like Architectural Designer until you are. CGPA or percentage is worth keeping while you are a fresher and it is good. Once you have your first job, drop it. Coursework lines are rarely needed in architecture, where the portfolio carries the evidence. Green-building accreditation, IGBC AP or LEED AP, is genuinely useful and increasingly expected on sustainability-conscious projects, so it earns a place near your certifications. Autodesk Revit certification is a reasonable signal early on, less so once your project bullets show heavy Revit use. Write the full name and the year, and never list a lapsed registration or accreditation as current.

Getting through the applicant tracking system

Larger practices and firms that recruit through job portals run an applicant tracking system, so the same parsing rules apply to architects as to any other field. The system reads your file, tries to break it into name, dates, employers, titles and skills, and stores the result for search. Almost every ATS problem is a parsing problem, and parsing problems come from layout, not wording. The layout rules are short. One column. Standard section headings, so use Work Experience rather than My Design Journey, and Software rather than My Creative Tools. Crucially for architects, no embedded images or thumbnails in the resume, because they break the parser and bloat the file. Keep the visuals in the linked portfolio. No critical information in the header or footer region, which some parsers drop. On wording, mirror the language of the job description where it is honest. If the posting says BIM, write BIM and Revit. If it says working drawings, write working drawings rather than only GFC. Include the expansion alongside an acronym at least once, for example "GFC (good for construction)", so both searches find you. Keyword stuffing does not work. A hidden block of software names helps nothing, because an architect is judged on the portfolio a stuffed resume never reaches. Write real bullets that naturally contain the right terms. Save as PDF from a tool that embeds real text, then open the file and confirm you can select and copy a sentence. If you cannot select the text, neither can the parser.

Keep every image in the linked portfolio, not the resume PDF. Embedded thumbnails break the parser, blow past email size limits, and show your work at a size that flatters nothing.

What gets architect resumes rejected

Most rejections at the resume stage are not close calls. They come from a small set of recurring problems, and all of them are fixable in an afternoon. The list below covers what reviewers of Indian architect resumes see most often, in rough order of how much damage each one does.

• A dead or access-restricted portfolio link. For an architect this is the single most damaging error, because the resume exists to earn that click.
• Embedded thumbnails that bloat the file and break the parser, in place of a clean link to a proper portfolio.
• Using the title Architect without COA registration, which is a legal and credibility problem in India.
• Renders described as achievements with no word on whether anything was built, on time or through its approvals.
• Job duties copied from the brief instead of what you delivered. "Responsible for design and drawings" is the tell.
• A software wall of twenty tools, half of them opened once, plus soft skills listed as software.
• A photo, date of birth, marital status or father's name. None of it belongs on a professional resume here.
• A generic objective line. Replace it with a summary that states focus, years and one built result.
• Inflating your role from team member to project architect on a specific building, which collapses the moment that project is discussed.
• Typos in the software or codes you claim. Writing "Revit" as "Rivet" or "IGBC" as "IGBS" undoes an otherwise strong page.

Read your resume aloud once before sending it, and open your portfolio link. Anything you would be embarrassed to defend in an interview, on the page or in the portfolio, is a line to cut or fix.

Skills to put on a architect resume

Certifications worth listing as a architect

Keywords an ATS scans for in a architect resume

These are the literal terms a parser matches against the job description. Use the ones that are true of you, in the sentences where you did the work, not as a list at the bottom.

• architect
• project architect
• b.arch
• COA registered
• Revit
• BIM
• AutoCAD
• working drawings
• GFC
• sanction drawings
• municipal approvals
• consultant coordination
• clash detection
• National Building Code
• green building
• IGBC
• LEED
• site supervision
• space planning
• design development

Architect resume FAQ

Related resume examples and guides