Beautiful projects can make a difficult job look irresistible. An architecture job offer needs a closer look: the interview room, website and competition awards show what a practice produces; they reveal less about how it plans work, reviews drawings or treats a late client change. If you are deciding between firms, use the offer stage to test your actual working conditions. You need evidence you can compare, not a perfect answer to every question.
What should you check before accepting an architecture job offer?
Check six things: the work you will do, who reviews it, how time is planned, what happens at deadlines, what the pay and conditions include, and how the role can develop. Get material terms in writing. Ask for examples from recent projects, not promises about the firm’s culture.
The RIBA guide to practising architecture well identifies predictable hours, training, autonomy with support and fair pay among useful signs of job quality. Those are measurable questions for a candidate, whether the employer is in London, Mumbai or Copenhagen.
1. Establish what you would actually be hired to do
Job titles travel badly across borders and even between neighbouring firms. “Architectural designer” may mean concept work in one office and documentation in another. Ask which project and phase would fill your first three months. Then ask what proportion of the job is design, documentation, coordination, site work or business development.
Do not treat variety as automatically good. A junior professional may need repeated technical work to build competence; an experienced hire may need broader ownership. The question is whether the assignment matches the career step you are trying to make.
Try: “Could you walk me through the first package I would own, who reviews it and how success would be judged?” A concrete answer gives you more than a list of software or sectors.
2. Test workload with a recent example
“We work hard” can mean different things. Ask what happened during the last deadline that required overtime. Who made the call? Was additional time tracked, paid or returned as time off where applicable? Did the team change the schedule or simply ask everyone to absorb the problem?
Ask a future teammate, if the firm allows it: “What time did you leave during the last ordinary week and the last difficult week?” You are seeking a pattern, not a guarantee. A single unusually busy project is different from a permanent operating model built on late nights.
Be precise about your own boundary. If regular evening work is impossible because of care responsibilities or health, say so before accepting. The response will tell you more than an employer’s values statement. For related context, jobs.archi’s work–life balance article looks at the profession-wide issue; here the decision is about one offer.
3. Find out how work is reviewed and mistakes are handled
Quality depends on review time. Ask who checks drawings before issue and how far in advance they need the set. A firm can expect independence while still assigning a named reviewer. If a junior candidate hears “you will figure it out,” ask what support arrives when a code question, site issue or consultant conflict exceeds their experience.
Try a scenario: “If I find a clash two days before issue, who decides whether the package moves or the drawing changes?” A strong answer describes escalation and a decision owner. An answer that praises resilience without describing a process is less useful.
If licensure or registration matters to you, ask whether your intended work and supervision count toward the local route. The jobs.archi overview of mentorship in architecture explores why that support matters.
4. Compare the whole offer, not only salary
Write down the base pay, expected hours, overtime policy, leave, insurance, pension or retirement terms, probation, notice, location, travel and equipment. A higher salary paired with unpredictable unpaid hours may be a worse fit. Benefits and legal entitlements vary by country, so use local documentation rather than a global checklist as your final authority.
Here is a simple comparison. Offer A pays more but expects frequent evening coordination across time zones. Offer B pays less, gives a defined training budget and puts a senior reviewer on your projects. Neither is universally better. If your immediate goal is qualification and technical depth, B may have more career value. If you need income now and can accommodate the schedule, A may still be rational. Put your priorities in order before negotiating.
Ask for a written offer or contract containing material terms. When the job advert and offer differ, request a corrected version. Do not rely on “we will sort that out later” for something that would change your decision.
5. Use the interview to check career progression
Ask what happened to someone who joined in a role similar to yours a year ago. What responsibility did they gain? Which project stages did they see? How often were performance conversations held? Examples are stronger than a claim that there is “room to grow.”
Also find out why the role exists. Growth, replacement and a single temporary commission imply different levels of stability. Ask politely: “Is this position linked to one project or part of a continuing team?” If the answer is one project, discuss what happens when that phase ends.
The Architizer guide to choosing a practice rightly asks about sectors, salary and culture. Add a question about the firm’s decision process: who can adjust scope, resources or deadlines when the original plan no longer fits? Culture is visible in that moment.
A decision sheet you can fill in after the call
Score each line clear, unclear or concern, and attach the evidence you heard:
- First project and phase: what was named?
- Manager and reviewer: who are they?
- Ordinary and deadline hours: what recent example was given?
- Scope and change control: who can change a deadline or fee?
- Compensation and conditions: what is in writing?
- Learning and progression: who advanced and how?
- Stability: why is the role open?
Do not turn the sheet into an artificial numerical ranking. One serious concern, such as no safe route for technical review, can outweigh several attractive answers. Follow up once on every unclear item, then decide whether the remaining uncertainty is acceptable to you.
When an answer sounds good but proves little
“We are like a family” says nothing about leave approval. “You will work on amazing projects” says nothing about your tasks. “Everyone here mentors juniors” says nothing about who reviews next Tuesday’s drawing issue. Translate each phrase into a request for a recent example or a named process.
There is also a difference between discretion and evasion. A firm need not disclose confidential fees or an employee’s personal history. It can still explain its review process, normal schedule and what a new hire would do. Our architecture job-search red flags guide covers earlier warning signs; use this checklist at the offer stage.
FAQ
Can I ask about overtime before accepting an architecture job?
Yes. Ask how the practice planned and handled its last demanding deadline and what its written policy says. Timing and tone matter less than getting a usable answer before you commit.
Should I ask to meet my future team?
If practical, yes. A short conversation with the person who will review your work can clarify the actual role. Ask the same concrete question you asked the hiring manager and compare the answers.
What if the firm will not put an important promise in writing?
Treat it as uncertain. You can explain why the term matters and ask whether the offer can state it. Then decide using the written terms you actually have, not an assumption that a verbal promise will survive a project deadline.
The best next step is to take this decision sheet into your next offer call. Leave with three verified facts: your first assignment, your reviewer and the way deadlines are managed. If those remain vague, you have a useful answer already.
1 thought on “Before You Accept That Architecture Job: Test the Offer, Not the Studio’s Image”