You studied architecture because you wanted to design buildings. Then the first job advert says “design opportunity,” while employees spend the week on consultant comments, drawing revisions and meeting notes. In a frank discussion about practice, some architects called this a bait and switch; others argued that resolving technical constraints is itself design. Both reactions reveal a useful question for job seekers: what decisions will you actually make in this role?
There is no universal percentage of an architect’s day spent “designing.” Work varies by project stage, firm, seniority and business model. Instead of asking whether the entire profession is creative, find out how one team divides its work and where you can gain authorship.
What architects do after the concept image
A building project moves through briefing, concept, coordination, technical development, construction and use. The RIBA Plan of Work is one way to describe those stages, especially in the UK; other markets use different contracts and labels. In every system, later decisions test whether early ambitions survive budget, regulation, structure, services, procurement and the site.
A typical project week might involve revising plans after a client’s operational change, checking a consultant model against a section, explaining a material substitution, reviewing an RFI, preparing drawings for approval and joining a site meeting. Some tasks are administrative. Others require design judgment even when no one calls them “creative.” Moving a riser can change a plan; resolving a facade detail can change daylight, cost and appearance.
Still, it is reasonable to want more time on concept development. The solution is to find the right role and project exposure, not to pretend every task is equally satisfying.
Four role patterns hidden behind similar titles
Concept and competition design. You may research precedents, develop massing and prepare presentations. Ask whether the same team follows projects into delivery. A role can offer strong early-stage work but little experience seeing decisions built.
Project architect or project lead. You may coordinate people, decisions, drawings, programme and client communication. There can be substantial authorship, though much of it takes the form of choosing trade-offs rather than sketching from scratch. Licensing expectations vary by jurisdiction.
Technical or production specialist. You may develop details, specifications, BIM content or coordinated sets. The work can be deeply design-oriented for someone who enjoys making ideas work. It can also become repetitive if the firm gives no feedback or ownership.
Construction-stage and site-focused role. You may answer questions, review substitutions and protect the design intent through construction. Some people love the tangible problem solving; others miss the front end. Clarify the role’s authority and who makes final decisions.
These categories overlap. A small firm may ask one person to do all four. A large practice may divide them among teams. Neither structure guarantees better experience; each creates different learning and promotion paths.
Questions that reveal the real job before you accept
Ask for examples rather than adjectives. “We are a design-led firm” reveals little. Try:
- Which project and stage would I join first?
- What would I produce in the first four weeks?
- Who develops the initial concept, and who carries it into technical design?
- How often does this team visit sites or review built work?
- What decisions could someone at my level make independently?
- How does the firm handle a conflict between concept, cost and buildability?
- Can you show an example of a project this team carried from one stage to the next?
- Who gives design and technical feedback, and how often?
Do not demand confidential drawings. The interviewer can describe a process or show published material. Listen for specific answers with stages, team roles and examples. “Everyone does everything” can mean useful breadth or a lack of staffing; follow up by asking what happened on the last project.
The first-job choice: breadth, depth and supervision
At the start of a career, you need exposure to decisions and feedback. A tiny office may offer direct client contact and whole-project visibility, but limited structured training. A large office may provide specialists and standards, but a junior can remain on one narrow task. Ask who checks your work and whether you will see the result of your revisions.
If you want to design, consider whether the role allows you to connect an early proposal with later constraints. A year making only presentation images may build visual skill but leave a gap in documentation. A year doing only redlines may build drafting speed but leave little authorship. The best first role does not have to deliver perfect balance; it should give a path to the missing side.
Read our existing guide to bridging architecture school and practice for the wider education gap. Here, use that gap to screen a specific offer.
Keep a decision diary, not just a project diary
For four weeks, privately record one important decision you saw each day. Note the original question, options, constraint, who decided and what changed. Protect client confidentiality. This reveals where design actually happens in your team. It also gives you better stories for interviews and reviews than “I worked on a mixed-use project.”
Example: “The client wanted a larger meeting room. The structural grid and accessible route limited two options. I tested a third layout, and the project lead selected it after a consultant review.” That is a design contribution, even if the final output was a revised plan and meeting note.
If your diary contains no decisions you can influence, ask your manager for a specific exposure: join one design review, take responsibility for a small detail or present an option with its trade-offs. State what you can handle and request feedback. If the answer is consistently no, the role may be too narrow for your goal.
You can also classify the decisions in your diary: spatial, technical, commercial or procedural. If you only see procedural decisions, ask to observe a meeting in another category. If you repeatedly make technical choices that shape the building, recognise them as design evidence even when your office gives them a different label. This distinction helps you describe your real experience to a future employer.
What to do when your current job is mostly production
First, identify whether the work is temporary because of a project stage. A technical issue period can be valuable if you understand why revisions are made. Ask to attend the decision meetings that generate your drawing changes. This turns anonymous markups into learning.
Second, build relationships across the team. A project architect is more likely to offer design responsibility when they trust your accuracy, responsiveness and ability to explain a choice. Show that you can bring two checked options, not just ask for more creative work.
Third, set a review date. If six months pass with no new exposure despite a clear request, compare roles elsewhere. Look at current architecture jobs by stage and employer type; read responsibilities closely rather than relying on the title.
Do not assume a move to a “design studio” automatically solves the problem. Ask how many projects reach construction and who owns later-stage changes. The Reddit discussion contains both disappointment and pushback because “design” means different things to different practitioners.
A quick interview exercise for the candidate
Bring one portfolio project and describe it twice. First, explain the concept in one minute. Then explain one decision you made when a constraint challenged that concept. An employer interested in your growth should engage with both. If the conversation stays only on images, ask about technical and construction exposure. If it stays only on software speed, ask where team members contribute to design direction.
This exercise also clarifies what you want. Some candidates discover they enjoy translating ideas into buildable detail more than producing initial concepts. That is a valid design career. Others confirm that early-stage work is essential for them and can target it more deliberately.
FAQ: Do architects spend most of their time designing?
No defensible universal percentage exists. Concept work, technical development, coordination and construction-stage decisions all take different shares by role and project stage. Ask a prospective team what a recent week looked like.
FAQ: Is technical work a dead end for a designer?
No. Technical knowledge can make design proposals more credible and give you authority in later decisions. It becomes limiting when you never gain feedback, authorship or exposure to other stages.
The takeaway
Choose a job by the decisions you can see, make and learn from. Ask for the first project’s stage, real deliverables and supervision. A beautiful portfolio on the firm’s website is a starting clue; the team’s answer about your next four weeks is stronger evidence.
The post Want to Design Buildings? Find Out What Your Architecture Job Actually Includes first appeared on jobs.archi.