The One Interview Question Architecture and Design Candidates Should Always Ask
About the Author
Lee Stevens, Director
Lee has over 15 years’ experience across Architecture, Design, and Planning, working with boutique studios through to global consultancies. He’s built his network on straight-talking advice and long-term relationships, not sales tactics.
Originally from the UK, Lee moved to Melbourne in 2014 and now balances recruitment with family life, coaching football, and keeping up with his kids and their very energetic cocker spaniel.
Contact Lee
Want to discuss your next role?
Contact Lee Stevens, Principal Recruitment Consultant, Architecture & Design -
You can also connect with Lee on LinkedIn or follow the Vivid Recruitment LinkedIn page for more industry insights, news, jobs and general chit chat and tips!
If you’ve got an interview coming up and want a straight answer on how to approach it, reach out. No fluff. Just honest advice.
Most architecture and design candidates walk into interviews trying to impress. The smarter ones focus on understanding what success actually looks like in the role. There’s one simple question that flips the conversation, gives you a clear roadmap, and puts you ahead of the pack. If you’re interviewing in architecture or design, use this.
Why Most Architecture Interviews Miss the Mark
We see this all the time.
Candidates come in ready to talk through their portfolio, software skills, and project experience. And fair enough, that’s part of it.
But the whole conversation stays here:
“Can you do the job?”
At interview stage, that’s already been ticked off.
If you’re in front of a director or senior architect, they already know you can produce drawings, use Revit, coordinate consultants.
What they’re really trying to figure out is:
“What’s this person going to be like on our projects, with our clients, under pressure?”
The One Question That Changes Everything
Ask this:
“Say this interview goes well and I’m offered the role, what would I need to do over the next 12 months to be seen as a success?”
Simple question. Big impact.
Why This Works So Well in Architecture and Design
It moves the conversation onto real projects
You’re no longer talking in hypotheticals.
You’re talking about:
- Live projects
- Deadlines
- Clients
- Internal pressure points
They start picturing you in the team, not just reviewing your CV.
You get clarity on what actually matters
Job ads in architecture are notoriously vague.
- “Assist with design development.”
- “Support project delivery.”
- “Work across all stages.”
But what does that actually mean day-to-day?
When you ask this, you’ll hear things like:
- “We’ve got a project in documentation that needs tightening up”
- “Clients are pushing for quicker turnaround on changes”
- “We need someone who can run with packages without being chased”
That’s the real job.
It shows you understand how studios actually run
Good studios don’t just care about design ability.
They care about:
- Hitting deadlines
- Keeping documentation clean and accurate
- Managing client expectations
- Not slowing the rest of the team down
This question shows you get that side of the job, not just the design side.
It separates you without forcing it
Most candidates try to impress.
The better ones try to understand.
That’s usually enough.
What “Success” Actually Looks Like in an Architecture Role
When placements work well, it’s rarely just about talent.
It usually comes down to this:
In the first 3–6 months
- Getting across office standards and systems quickly
- Producing drawings that don’t need constant rework
- Picking up project context without hand-holding
By 6–12 months
- Running parts of a project with confidence
- Managing deadlines without being chased
- Communicating properly with consultants and clients
Longer term
- Becoming someone the team relies on
- Taking pressure off senior staff
- Contributing beyond just your own drawings
When you ask that question in an interview, this is the level of detail you start to uncover.
Real Example From the Market
We’ve placed candidates into architecture studios where the difference was minimal on paper.
Same software. Similar project experience.
One candidate answers questions and leaves it there.
The other asks this.
The director opens up about:
- A project that’s under pressure
- Documentation issues in the team
- Where they’ve been burned before
Now the candidate can respond directly to that.
Not generic answers. Actual relevance.
That’s usually what swings it.
When to Ask It
Don’t jump in too early.
Let the conversation build first.
Then when they ask:
“Any questions for us?”
That’s your window.
Ask it. Then listen.
Common Mistakes We See
Playing it too safe
- “What’s the culture like?”
- “What are the next steps?”
Fine, but they won’t set you apart.
Focusing too much on impressing
If you’re only trying to say the right things, you miss what actually matters to them.
Not using the answer
If they tell you what success looks like and you don’t respond to it, you’ve missed the point.
That’s your chance to connect your experience to their actual problems.
| Typical Candidate Approach | Strong Candidate Approach |
|---|---|
| Focus on portfolio and software | Focus on project delivery |
| Talk about past work | Link to future role expectations |
| Ask generic questions | Ask what success looks like |
| Wait for feedback | Shape the conversation |
Final Thought
There’s no secret to interviews.
But there are small shifts that make a difference.
This is one of them.
If you’re interviewing in architecture or design, try it next time and see how the conversation changes.
Frequently Asked Questions
Is this relevant for graduate architects?
Yes. If anything, it helps you stand out even more when experience is limited.
What if I’m more design-focused than technical?
Still ask it. Studios care about delivery just as much as design.
What if they give a vague answer?
Push a bit. Ask about projects, deadlines, or team structure. Most will open up.
