An architectural technician supports the technical side of architectural projects, often working on drawings, information, coordination, regulations, software and the practical detail that helps a design move forward.
The exact role varies by practice, but the hiring signal is usually the same: can you produce clear information, understand construction logic and communicate properly with the wider team?
Watch: Architecture Social video
This Architecture Social video adds useful context before the practical guidance below.
What an architectural technician does
Architectural technicians often work across drawing packages, technical information, design development, planning support, building regulations, consultant coordination and project documentation. Some roles are more junior and production-focused. Others carry more responsibility.
- Preparing or updating drawings and technical information.
- Using software such as Revit, AutoCAD, SketchUp, Rhino or BIM tools.
- Supporting planning, building regulations or tender-stage work.
- Coordinating information with architects, technologists, engineers and consultants.
- Helping projects become clearer, buildable and properly documented.
Technician, technologist and architect are not the same
The job market can use titles inconsistently, so read each advert carefully. Architectural technician and architectural technologist roles can overlap, but technologist roles may ask for broader technical leadership, CIAT alignment or deeper construction knowledge.
In the UK, architect is a protected title. Do not use it for yourself unless you are ARB registered. You can still build a strong technical career without mislabelling your role.
Skills employers look for
Search demand suggests useful UK demand around architectural technician, architectural technician jobs and architectural technician salary. That tells us readers need both role clarity and next-step career information.
- Clear technical drawing and documentation.
- Honest software ability connected to real outputs.
- Understanding of building regulations and construction basics.
- Attention to detail without losing the project purpose.
- Communication with project teams, consultants and clients where relevant.
How to present the CV and portfolio
A technical CV should connect software, project stage and responsibility. A portfolio should include examples that show drawings, details, coordination, BIM evidence or technical problem-solving where you can share them.
If confidentiality limits what you can show, explain the project type, your role and the kind of information you produced. Do not leave the reader guessing.
Salary and progression
Salary depends on location, experience, software, sector and responsibility. The strongest progression usually comes from combining production ability with technical judgement, communication and project reliability.
Go deeper with Architecture Social
These related Architecture Social episodes add more context once you have the practical framework.
Related audio: construction and architectural technology careers
The podcast version adds more context on construction, architectural technology and how technical careers can develop inside and around practice.
You can also open the related Architecture Social podcast page.
Example CV bullets for an architectural technician
The CV should make technical responsibility obvious. Use project context and outputs rather than a flat list of duties.
- Supported planning and technical drawing packages for residential retrofit projects using AutoCAD and Revit.
- Produced drawing updates, schedules and consultant issue sets under senior technician review.
- Coordinated information with structural and MEP consultants, tracking comments and drawing revisions.
- Assisted with building regulations information, detail development and project documentation.
What to show in a technical portfolio
Where confidentiality allows, show enough technical evidence for a practice to understand your level. That might include plans, sections, details, drawing extracts, BIM screenshots, schedules or before-and-after coordination examples.
If you cannot show the full project, explain the type of information you produced and your role in the team. Redacted or cropped evidence can still be useful if it is honest and clear.
Interview preparation
Prepare to talk through how you produce information, check work and handle changes. Good technician interviews often come down to reliability, software honesty and whether the practice trusts your attention to detail.
Bring examples of where you solved a technical problem, spotted an issue or improved a drawing package. Those examples are more convincing than saying you are detail-oriented.
Common mistakes
- Listing software without showing project outputs.
- Applying for technical roles with a purely visual portfolio.
- Using role titles loosely without checking what they mean.
- Hiding building regulations, technical drawing or coordination experience.
- Ignoring salary evidence before interviews or reviews.
Architecture Social view
Stephen’s recruiter view is that technician candidates can be hugely valuable when their evidence is clear. Practices need people who can turn design intent into usable information.
Next step
Compare your CV against live architectural technician jobs, then check the architectural technologist career guide, architecture salary guides and architecture CV guide to tighten your evidence.
Add a comment