Just went through a technical interview for a Solutions Architect position at a certain consulting and audit firm. Let's call it a firm that starts with K. I'll let you figure out the rest.
Honestly, the experience was rather frustrating.
The technical interview focused heavily on extremely niche technical knowledge, obscure edge cases and very granular implementation details. It felt much more like a grilling session than an attempt to understand how I approach architectural problems.
I have absolutely no problem being technically challenged. That's part of the job. But there's a difference between challenging someone's engineering judgement and trying to catch them out on implementation details they probably haven't needed to think about in years.
What I would have expected instead was an exploration of how I:
Break down an unfamiliar problem.
Identify technical and business constraints.
Evaluate competing architectural approaches.
Understand the trade-offs across a chain of services.
Make decisions with incomplete information.
Identify what needs further investigation before committing to a design.
Because that's what being a Solutions Architect actually involves.
You don't walk into a customer meeting, get a five-minute description of their infrastructure and magically produce a validated architecture. You ask questions, challenge assumptions, investigate constraints and progressively build a solution.
And sometimes the most architecturally sound answer is simply: I don't know yet. I need more information before making that decision.
I'm curious how common this experience is.
Have technical interviews for senior architecture roles increasingly become exercises in testing how much obscure technical trivia candidates can recall, rather than how they actually think and operate as architects?
Or did I just have a particularly entertaining encounter with the consulting industry?