“We have a mentoring culture” sounds reassuring in a job interview. It is also easy to say. A good architecture firm can show how a junior designer gets feedback, sees more than one project phase and finds help when a difficult decision arrives. If mentorship matters to your next job, ask for examples of the routine—not a promise of access to a famous principal.
What good mentorship looks like in practice
Mentorship is not one inspiring conversation a year. It is a combination of project exposure, timely feedback and a person willing to explain the reasoning behind decisions. You should know who reviews your work, how often reviews happen, whether you can ask questions early and what skills you are expected to build.
In the United States, candidates pursuing licensure have additional requirements. NCARB’s guide to finding a supportive employer recommends checking supervision, varied experience, exam support and mentorship. In another country, use the equivalent local qualification route as your checklist.
Seven questions to ask in an interview
- “Who would review my work in the first three months?” Look for a named role and a realistic review rhythm.
- “Can you describe how a junior team member received feedback on a recent project?” A concrete example is more useful than a slogan.
- “Which project phases could I experience here?” If all junior staff are confined to one repetitive task, ask how people broaden their exposure.
- “How do you support qualification or licensure?” Ask about supervisor access, eligible work, study time and any financial support relevant to your jurisdiction.
- “What happens when someone makes a mistake or spots a risk?” The answer reveals whether learning and quality control can coexist.
- “How are project reviews scheduled when deadlines are tight?” Mentorship that vanishes during every busy period may be hard to rely on.
- “What did a recent junior colleague learn or take ownership of over the last year?” Progress should be visible in responsibilities, not just time served.
Ask different people the same question when possible: the hiring manager, a potential teammate and someone who joined recently. Their answers need not be identical, but they should describe the same working reality.
Look beyond the interview script
Review the firm’s projects and ask what part of the work is done in-house. A practice focused on one type of deliverable can still be an excellent place to learn, provided its scope matches your goals. If you want site experience, ask whether your role would include site visits. If you want technical coordination, ask who leads consultant reviews and whether you can observe them.
Look at how the firm describes career development in the job ad. A clear manager, onboarding plan and review process are stronger signals than “work closely with leadership.” During an offer discussion, ask for the support you consider essential to be documented where appropriate. Our overview of mentorship in architecture explains why the relationship matters; this guide is designed to help you evaluate a specific employer.
Red flags that deserve a follow-up question
- No one owns feedback. “Everyone mentors everyone” may mean nobody has time to review your development.
- Questions are treated as weakness. Architecture depends on checking assumptions before they become built errors.
- Hours are praised, learning is vague. A demanding project can teach a lot, but long hours alone are not a training plan.
- Qualification support is promised without a supervisor or relevant work. Check the actual route and who can sign or verify experience.
- Recent junior staff leave without a clear explanation. Turnover can have many causes; ask what the firm learned and changed.
A red flag is a reason to investigate, not automatic proof that the firm is poor. A small office may lack a formal programme yet provide excellent daily teaching. A large firm may have a polished programme but assign you narrow work. Evaluate the specific team you would join.
Compare offers with a simple scorecard
Write your three most important development goals: perhaps licensure, technical design or client communication. For each firm, record evidence of project exposure, review time, supervisor access and support for those goals. Add salary, workload, flexibility and the nature of the projects. Do not let one appealing project image outweigh the day-to-day conditions under which you would learn.
If you accept, agree on an early check-in. Ask your manager what you should be able to do after three and six months, and what feedback you will receive along the way. Mentorship becomes easier to deliver when the goal is visible to both people.
Frequently asked questions
How can I tell if a firm really supports licensure?
Ask who supervises eligible experience, what types of work junior staff can access, how reports are reviewed and whether exam time or costs are supported. Verify the requirements with your licensing body.
Is a formal mentoring programme necessary?
No. What matters is reliable access to relevant work, review and guidance. Ask how that happens in the team you would actually join.
What if my current firm does not offer enough project exposure?
Explain the specific experience you need and ask whether assignments can change. If the firm cannot provide it, use your qualification body’s guidance to understand alternative ways to gain experience or assess another role.