Use this Architect job description template to attract candidates who can develop coordinated building designs, translate client requirements into clear documents, and resolve design issues through construction. Adapt project stages, building types, and professional authority to your practice’s commissions and local registration rules.

An Architect develops building designs that connect client needs, site conditions, technical requirements, and construction information. The role coordinates architectural decisions with specialist consultants and project stakeholders. This template concerns building architecture, not software architecture, and should be adapted to the professional title and practice rules in the relevant jurisdiction.

An Architect turns the client brief and site constraints into coordinated design information that supports informed project decisions. Their key responsibilities include:

• Developing architectural design options that respond to the approved client brief and site constraints.

• Preparing coordinated drawings, models, and specifications for assigned project stages.

• Reviewing building requirements and raising unresolved code or approval questions for specialist input.

• Coordinating architectural information with structural, building-services, and other consultants.

• Communicating design decisions, outstanding issues, and changes to clients and project colleagues.

Architect Job Description Template

We are looking for an Architect to carry design intent from an agreed brief into coordinated project information. The ideal candidate can explain design trade-offs, coordinate drawings and specifications, and identify questions requiring specialist or approval input.

In this role, you will examine constraints, develop options, explain trade-offs, and keep drawings and specifications aligned as decisions evolve. The position requires clear communication about what has been agreed, what still needs specialist input, and how a proposed change affects the wider project. You will coordinate architectural information with clients, consultants, and project colleagues, maintaining a clear record of design decisions and outstanding issues.

Architect Roles and Responsibilities

Architectural work moves between design exploration and disciplined coordination. The architect needs to preserve the rationale behind a decision while ensuring that later drawings, schedules, and consultant information reflect it consistently.

The role includes the following duties:

• Develop architectural design options that respond to the approved client brief and site constraints.

• Prepare coordinated drawings, models, and specifications for assigned project stages.

• Review building requirements and raise unresolved code or approval questions for specialist input.

• Coordinate architectural information with structural, building-services, and other consultants.

• Communicate design decisions, outstanding issues, and changes to clients and project colleagues.

• Maintain clear drawing revisions and document the basis of significant design changes.

• Review material and assembly choices against agreed performance, budget, and project objectives.

• Support planning or permit submissions within the role’s authorized professional scope.

• Respond to construction queries and review submittals where included in the appointment.

• Attend agreed site visits and record observations without implying continuous construction supervision.

• Track design deliverables and flag dependencies that threaten the agreed issue dates.

• Support internal design reviews and resolve assigned coordination comments before documents are issued.

Architect Requirements and Qualifications

Balance design capability with evidence of technical coordination and document control. Educational and experience pathways vary, but an equivalent-experience statement must never be used to bypass professional registration where the title or work is regulated.

Look for evidence of these qualifications:

• Architectural education and professional experience appropriate to the jurisdiction and assigned responsibilities.

• Current registration or license where necessary to use the title or perform the specified professional work.

• A portfolio showing personal contribution to relevant building projects and design stages.

• Proficiency in the practice’s drawing or building-information-modeling workflow, with transferable software skills.

• Experience coordinating architectural information with engineering and specialist consultant inputs.

• Knowledge of relevant building requirements and the ability to identify questions needing expert review.

• Clear written and visual communication for client presentations, technical queries, and design records.

• Understanding of how materials, assemblies, and building services affect architectural decisions.

• Organized document control and the ability to trace revisions through drawings and schedules.

• Commercial awareness of project scope, deliverable deadlines, and the limits of the professional appointment.

Who Does an Architect Report To?

The reporting relationship should give the Architect a clear route for architectural design reviews, consultant coordination, and project decision authority. Common reporting options include:

• Project Architect

• Studio Director

• Design Director

• Principal Architect

A project-focused architect may report to a Project Architect, while a senior role may report directly to a studio director or principal. Consultant coordination does not necessarily mean line management. State who owns client commitments and professional sign-off, especially when the role develops documents that another registered architect will review and issue.

How to Assess Architect Skills Effectively

Use a small fictional building brief and a limited drawing pack. Evaluate design reasoning, coordination, and scope awareness rather than asking for unpaid production design. Give candidates enough context to explain constraints and distinguish personal decisions from specialist responsibilities.

• Brief interpretation: Provide a fictional client brief with competing priorities; ask the candidate to identify questions and propose evaluation criteria for options.

• Coordination review: Show a simplified plan and consultant overlay with a conflict; ask how the issue should be resolved and recorded.

• Portfolio discussion: Ask the candidate to explain their specific contribution to a permitted example, including a decision that changed during the project.

• Change impact: Describe a fictional late layout change; ask which drawings, disciplines, approvals, and client decisions may be affected.

• Construction query: Present a short fictional contractor question; ask what information is needed before issuing an authorized response.

• Design communication: Ask for a concise explanation of two options to a nontechnical client, including uncertainty and trade-offs.

How to Detect AI Cheating When Hiring an Architect

Candidates must independently explain architectural decisions, coordinate consultant information, and distinguish personal contribution from team work. AI answering tools or real-time outside help can supply terminology without showing the reasoning behind it. Ask candidates to explain assumptions and respond when one detail changes.

Sherlock AI helps recruiters detect AI-assisted cheating during Architect interviews. It can flag potential AI answering tools, deepfakes, impersonation, or suspicious screen activity. These signals need human review, not automatic verdicts. Explain permitted resources and interview monitoring beforehand.

Use role-specific exercises, such as reviewing fictional coordination issues, comparing design options, or explaining a documented project decision. The exercise evaluates professional judgment, while Sherlock identifies potential cheating signals during the interview. Verify credentials separately; interview integrity does not prove practical competence.

Screen Architect Interviews for AI-Assisted Cheating

Independent design judgment appears when an Architect explains constraints, alternatives, and the consequences of a decision rather than reciting design language. Probe the candidate’s own contribution to portfolio work. Sherlock does not validate professional registration, establish authorship of every project document, or replace technical review.

Explore Sherlock AI to support interview integrity alongside your role-specific hiring process.

Frequently Asked Questions

What does an Architect do across a project?

An Architect translates the brief into building design and coordinated information, then may support approvals and construction-stage services. The appointment determines the actual scope. Some roles concentrate on concept work, while others focus on technical delivery, so the job description should state the project stages explicitly.

Does an Architect need professional registration?

Where the title or practice is regulated, the applicable registration rules must be followed. U.S. licensing requirements apply. Employers hiring elsewhere should check the local professional regulator and distinguish registered architect roles from architectural assistant or designer positions.

What should an architectural portfolio demonstrate?

It should show relevant project work and clearly identify the candidate’s own contribution. Ask about the brief, constraints, design choices, coordination, and what changed after review. Attractive images alone do not establish responsibility for technical documentation, approvals, or the successful resolution of construction questions.

Is an Architect responsible for every engineering decision?

No. Architects coordinate with structural, mechanical, electrical, and other specialists, but each discipline retains its own professional responsibilities. The architect should identify interfaces and unresolved conflicts without claiming expertise or authority outside the appointment. Clear coordination is different from independently redesigning another consultant’s system.

How much site work should the role include?

That depends on the appointment and project stage. Some roles involve periodic observations, meetings, and query resolution; others are mainly studio-based. State the expected attendance and reporting duties. Do not describe periodic site visits as continuous supervision or imply that the architect controls the contractor’s construction methods.

Which software skills should be listed?

List the tools actually used for drawing, modeling, coordination, and document production, but distinguish essential workflow competence from software that can be learned. A candidate’s ability to maintain consistent project information and understand model limitations may matter more than familiarity with every application named in a long list.

How should employers evaluate design judgment?

Use a bounded fictional brief or coordination problem and ask for the reasoning behind choices. Evaluate clarity, feasibility, responsiveness to constraints, and recognition of specialist input. Avoid requesting substantial unpaid project work, and verify any professional credential separately from the interview or portfolio discussion.