Why Are Architects Paid So Little? Follow the Money Before You Negotiate

Architecture asks for years of education, technical judgment and responsibility. So why can a capable architect still feel that the salary does not reflect the work? The question is all over a discussion about the profession’s pay scale. The responses disagree about whether the profession is universally underpaid, but many describe the same mismatch: responsibility expands faster than compensation.

There is no single global architect salary. Country, city, registration, sector, firm size and actual role matter. The useful question is narrower: what creates your firm’s ability and willingness to pay for your contribution, and how can you test the market before you make a career decision?

Why architect pay can lag behind responsibility

An employee’s salary is paid from a practice’s income, not directly from a building’s construction budget. Fees must cover staff time, benefits, insurance, software, business development, office costs, leadership and periods when projects pause. A prestigious commission is not necessarily a profitable one. If a practice wins work on a thin fee, long hours can conceal a pricing problem rather than prove that its staff lack value.

That explanation should never be used to excuse poor pay. It does explain why asking only “How complex is my work?” may not predict the offer. Ask what projects the firm sells, how fees are set, whether additional services are billed and who manages scope changes. A well-run technical or specialist practice may have more room to reward a valuable employee than a famous studio that relies on prestige to attract applicants.

The AIA’s 2025 compensation research collected data from US firms across many roles and locations. Its public summary says average architect compensation grew by less than 3% annually between 2023 and 2025. That is a US survey result, not a global pay rate or a personal raise target. It is also a reminder to separate the profession-wide trend from your own market value.

The five numbers to compare before calling an offer good

Create a one-page comparison for your current role and two real alternatives. Use the same currency and period for every row.

  1. Base pay: annual salary or your expected paid hours, with bonus separated.
  2. Hours actually worked: include regular late evenings, not just contract hours. A higher salary can produce a lower effective hourly rate.
  3. Benefits and costs: health cover, pension, paid leave, exams, professional fees, commuting and relocation.
  4. Role scope: what decisions and risks you own, who checks your work and whether the title matches the responsibility.
  5. Future options: mentorship, project exposure, promotion criteria and the ability to move to better-paid roles.

For example, compare a hypothetical 40-hour role paying 60 units with a 50-hour role paying 70 units. On a simple salary-per-hour calculation, the second role pays less for each hour of work. The units are illustrative, not market data; taxes, benefits and local employment rules still matter. The exercise makes a hidden trade-off visible.

Use a role-specific source such as the AIA benchmark in the US, a relevant local professional body’s survey elsewhere, and current job advertisements with disclosed ranges. Record the survey year, region, sample and job definition. Do not treat a national median, a Reddit comment or an advertised top-of-range figure as your exact entitlement.

Why “architect” is a poor salary comparison category

Two people with the same title can produce different value in different businesses. One may lead technical delivery on a healthcare project; another may primarily model competition images. One may bring clients; another may have no commercial responsibility. Conversely, an unlicensed project lead may carry more daily responsibility than a newly licensed employee.

Compare the job, not just the label. The AIA position definitions distinguish a range of roles for compensation reporting. For your own benchmark, write down project stage, team size, client contact, technical sign-off, construction exposure and software ownership. Then compare positions with similar duties in the same geographic market.

If your role has expanded, list what changed since your last review: a project you now coordinate, a process you improved, a junior you train, a specialist task you own. Keep client-confidential information out of this record. You need enough detail to discuss the role, not disclose the project.

Where bargaining power comes from

An employer can value you more when replacing your contribution would be difficult. That does not mean hoarding knowledge. It means being reliable at work that matters to the practice: coordinating a hard project stage, reducing recurring drawing errors, keeping a client informed, developing a sector specialty or mentoring others to deliver better work.

Document outcomes without inventing percentages. “Coordinated the consultant review and closed the outstanding interface issues before tender” is stronger than “excellent team player.” A before-and-after drawing, issue register or process note can support that statement where sharing is allowed.

External options matter too. You cannot know your market by looking at one annual review. Compare live roles on jobs.archi and other specialist boards, speak to recruiters who place architects in your region and interview selectively. An interview can reveal that your skills command more, or that you need a missing credential. Neither result requires an immediate resignation.

How to ask for a raise without making it a referendum on passion

Book a dedicated conversation. Send a short agenda: current scope, evidence of contribution, role benchmark and the change you seek. State a specific request grounded in a comparable range, but be clear about the source and date. Then stop talking long enough to hear the answer.

Try this structure: “Since our last review, I have taken responsibility for X and Y. Comparable roles in this market appear to sit in [sourced range]. I would like to discuss a base salary of [your number] and what responsibility the firm expects at that level.”

If the answer is “not now,” ask for a decision date and written criteria. “When revenue improves” is too vague to plan around. Ask what measurable change would justify the raise, who approves it and whether an interim change in title, paid exam support or reduced overtime is possible. These alternatives are not substitutes for fair pay if the base salary remains unworkable.

For a broader negotiation checklist, see our existing guide to strategically increasing an architect salary. This article focuses on the economics and comparison behind the ask.

When changing firms may be the rational move

If the firm is consistently understaffed, avoids discussing fees, offers no promotion criteria and depends on unpaid overtime, your salary may be constrained by its business model. You cannot negotiate a healthy career out of a system that cannot deliver one. Look for firms that can explain how they scope projects, develop staff and decide pay.

Changing sectors or employer type can also matter. Owner-side teams, contractors, specialist consultancies and public bodies value different combinations of design, coordination and technical knowledge. Do not assume that every adjacent role pays more. Compare real offers, qualifications and working hours before moving.

There is another possibility: you may value a smaller, calmer practice and accept a lower salary knowingly. The key is an informed choice rather than discovering the trade-off after years of unpaid hours.

A 30-minute pay audit

Take your latest contract, three months of real working hours, a list of responsibilities and three relevant job advertisements. Write down:

  • Your effective hourly rate, including routine overtime.
  • The duties you perform that are absent from your title or job description.
  • The market evidence and its limits: location, year and role.
  • The minimum change that would make staying worthwhile.
  • The date when you will revisit the decision if nothing changes.

Do not add colleagues’ unverified salaries or anonymous claims as facts. Use them as questions to investigate. The Reddit pay discussion is valuable because it surfaces frustration and possible explanations; it cannot establish what every architect earns.

FAQ: Are architects underpaid everywhere?

No reliable single measure answers that. Pay varies sharply by market, role and employer. A more defensible statement is that some architects experience a gap between responsibility, hours and compensation. Test your own situation with comparable roles and actual hours.

FAQ: Should I wait for licensure before negotiating?

Not automatically. Registration may expand the work you can legally take on, depending on jurisdiction, but your present responsibilities and results can justify a conversation now. If licensure is near, ask how the firm will change your role and compensation when you achieve it; do not rely on an unstated promise.

The takeaway

Poor pay is not a character verdict on architects, and passion is not a pay policy. Understand the firm’s economics, compare the whole offer with genuinely similar roles, document what you contribute and ask for a concrete decision. If the answer has no credible path or date, use the market evidence to plan your next move.

The post Why Are Architects Paid So Little? Follow the Money Before You Negotiate first appeared on jobs.archi.

Scroll to Top