An architecture salary negotiation should start with evidence, not nerves. Before asking for more money, understand your role level, project responsibility, software skills, location, market demand and what comparable jobs are offering.
The aim is not to make an emotional speech. It is to show that your contribution, responsibility and the market have moved, then ask for a fair review.
Watch: are you on the right architecture salary?
This Architecture Social video explains how to think about salary, value and the next conversation with your employer or a future practice.
Listen: architecture salary and value
Prefer audio? This episode gives the longer Architecture Social discussion around pay, negotiation and understanding your value.
You can also open the related Architecture Social podcast page.
Check whether the salary is actually off
Salary depends on more than job title. A Part II assistant running packages in London is not the same as a newly qualified architect in a smaller regional practice, and a BIM-heavy technical role may sit differently again.
- Compare live job adverts for similar role levels.
- Look at location, sector and practice size.
- Check whether the role asks for Revit, BIM, delivery, site or client responsibility.
- Separate base salary from bonus, overtime, benefits and flexibility.
- Ask whether your current responsibilities have moved beyond your job title.
Prepare the case before the meeting
The strongest salary conversations are calm and specific. Bring examples of responsibility, not just a number you saw online.
- List projects where your responsibility increased.
- Note delivery, coordination, client, planning or technical outcomes.
- Show where you saved time, reduced risk or helped the team.
- Bring market examples, but do not use them as a threat.
- Suggest a review date if the practice cannot move immediately.
What to say
Keep the wording plain: I have been taking on more responsibility across these projects, and I would like to review whether my salary still reflects the role I am now doing. I have also looked at comparable architecture roles in the market, and I would like to understand what would be needed to move towards that level here.
Salary research before you ask
Use live Architecture Social pages to compare the market before making a pay request or deciding whether to move.
Common mistakes
- Waiting until frustration has already built up.
- Using another job offer as the first move.
- Comparing yourself to someone with a different role level or location.
- Forgetting to include benefits, flexibility and progression.
- Not asking what evidence the practice needs to approve a rise.
Architecture Social view
Stephen’s view is that salary confidence comes from clarity. If you know what the market is doing and can explain your value in practice language, the conversation becomes less awkward and more professional.
Build your salary evidence first
Before you ask for more money or accept a new role, compare the market and write down the responsibility you can prove.
- Check current jobs at your level.
- Write down three examples of increased responsibility.
- Decide your ideal number and your acceptable range.



Add a comment