A starting point for
your pay conversation.
Benchmarks are a guide, not guaranteed offers. Compare the range with your responsibilities, experience, benefits and current job adverts.
Compare the scope of the computational work.
Computational Designer can mean developing project geometry, testing design options, analysing performance or building tools for other people to use. Compare the benchmark with the actual brief, the technical responsibility and the time available to maintain what you create.
Understand what the studio expects you to deliver.
- Is the priority project design, automation, analysis or internal tool development?
- Which tools and programming languages are essential, and where will you use them?
- Who checks the assumptions, inputs and outputs before a result informs a project decision?
- Will other people use your scripts, and who owns documentation, support and maintenance?
- What technical review, training and progression are available?
Explain the result as well as the script.
Take one example from problem to output. Explain the input, your method, how you checked it and how the project team used the result. If you claim a time saving, be ready to show how you measured it. A clear limitation or validation step is more useful than an unsupported efficiency claim.
A practical pay question is: “Does this offer cover project delivery only, or also the support and maintenance of tools used across the studio?” Compare the answer with the responsibilities, working pattern and development support.
Use the computational designer role guide to prepare, then compare the scope described in current vacancies.
About these figures
Architecture Social salary guide
Benchmarks: June 2026
Source recorded: 21 July 2026
Compare roles in the salary guide 