What Hiring Managers Look For in Architects

Hiring managers are not only looking for a talented architect. They are looking for evidence that reduces uncertainty: can this person do the work, fit the role, communicate properly and help the team move forward?

For candidates, that means the CV, portfolio, email and interview all need to make the same case. Clear evidence beats vague confidence.

Watch: what employers look for when hiring architects

This Architecture Social episode is useful because it shows the other side of the hiring conversation: what practices are trying to understand before they commit.

Listen: hiring managers and architecture recruitment

Prefer audio? This episode gives the full Architecture Social conversation on employer expectations and how candidates can respond.

What hiring managers scan first

Most hiring managers start with fit. They want to know whether your level, experience, project background and software make sense for the role they need to fill.

• Role level and years of relevant experience.
• Project type, scale and stage.
• Software confidence, especially where the role requires it.
• Portfolio evidence that matches the CV.
• Communication style in the application and interview.

What stands out for the right reasons

Standing out is not about being loud. In architecture recruitment, it usually means making useful evidence easy to judge.

• A clean CV that follows the basics in the Architecture Social CV guide.
• A focused sample portfolio that follows the logic in the sample portfolio guide.
• A short application note that explains why the role and practice make sense.
• Interview examples that prove judgement, not only enthusiasm.

Examples that make a stronger impression

A hiring manager remembers evidence that feels specific. The difference is usually not fancy wording, but whether the example answers a real hiring question.

• Weak: I am good at Revit.
• Better: I used Revit to update drawing sheets and coordinate revisions on a residential planning package.
• Weak: I enjoy teamwork.
• Better: I worked with the project architect and consultants to resolve drawing comments before a submission deadline.
• Weak: I am interested in sustainability.
• Better: I researched retrofit precedents and used them to inform material and envelope decisions in my studio project.

What weakens an application

The weakest applications often make the hiring manager work too hard. The candidate may be good, but the evidence is hidden, confused or generic.

• CVs with no clear project stages or responsibility.
• Portfolios that look beautiful but do not explain role or process.
• Applications sent to every practice with no adjustment.
• Software claims without project evidence.
• Interview answers that describe the team but not personal contribution.

How to prepare for interviews

The interview should make your evidence easier to understand. Prepare a few project stories that explain the brief, your role, the challenge and what you learned.

• Use the Architecture Social interview questions guide to practise the common topics.
• Prepare one example about design judgement.
• Prepare one example about coordination or teamwork.
• Prepare one example about feedback, pressure or a project problem.

For employers, the lesson is clarity too

Good hiring is not only a candidate problem. Practices need clear briefs, realistic salary expectations, useful feedback and an honest view of what the role actually needs.

• If you are hiring, start with the Architecture Social employer recruitment support.
• Define the role before advertising it.
• Separate must-have skills from nice-to-have preferences.
• Give candidates enough context to self-select properly.

What employers should define before interviewing

A good interview process starts before the interview. If the practice cannot explain what good looks like, candidates will struggle to present the right evidence.

• What projects will this person actually work on?
• Which software is essential from day one?
• Which project stages matter most?
• What support, mentoring or leadership will be available?
• What salary, progression and flexibility can be discussed honestly?

Short application email for candidates

A stronger first message might say: I am interested in this role because my recent experience in [project type or stage] matches the work described. I have attached a CV and focused sample portfolio showing [software, sector or responsibility]. I would be happy to talk through the relevant projects if useful.

That kind of email helps the hiring manager because it points them towards the evidence instead of asking them to find it from scratch.

Common mistakes

• Candidates trying to impress without proving fit.
• Practices writing vague job adverts and expecting perfect applications.
• Using the portfolio as a visual dump rather than evidence.
• Avoiding salary and progression conversations until too late.
• Forgetting that recruitment is a two-way judgement call.

Architecture Social view

Stephen’s recruiter view is that hiring managers want clarity more than theatre. The best applications make it easy to say yes, easy to shortlist and easy to understand where the candidate can add value.

Next step

Before your next application, ask what a hiring manager would need to know in the first 60 seconds. Then tighten your CV, portfolio and interview examples around that evidence.