Writing an architecture job post that gets the right applications
8 Nov
A good job post saves you hours of sorting through applications that were never a fit. Architects and designers read posts quickly and decide in seconds whether a role is for them. These are the things that help them decide.
Start with the title they would search for
Use the title candidates actually look for: Junior Architect, Interior Designer, BIM Modeller, Project Architect. Avoid internal titles like “Design Associate II” unless you add the common equivalent.
Say what the work is
In two or three short paragraphs, cover:
- The projects — residential, hospitality, institutional, interiors, competitions. Mention scale if you can (“villas and small housing”, “a 40-key resort”).
- The stage — concept, working drawings, site coordination, or all of them.
- Who they work with — the principal directly, a project lead, a team of five.
A candidate who can picture a normal week will apply with confidence. One who can’t will move on.
Be clear about requirements — and keep the list short
List what is genuinely needed: years of experience, the software you use every day, whether COA registration is required. Put nice-to-haves in a separate sentence. Long lists of requirements put off good candidates who meet most of them.
Show the salary
Posts with a salary range get more relevant applications, because candidates who would not accept the range don’t apply. If you can’t publish a number, say what the range depends on.
Make applying simple
Choose one way to apply — email, WhatsApp or your website — and say what to send: a CV, a portfolio link or PDF (with a size limit), and anything specific such as two projects they are proud of. On ArchCareers every application method is tracked, so you can see how many people clicked to apply.
Before you post
- Read it on your phone: most candidates will.
- Check spellings of software and place names.
- Make sure the contact email or number is one someone checks daily.
Every listing on ArchCareers is reviewed by our team before it goes live. If something is unclear we’ll get in touch rather than reject it.