Start with a hiring brief that describes an actual problem, relevant environment, and acceptance tests. Present a product with scaling problems and inconsistent data across services. Ask candidates to identify measurable quality attributes, propose options, and explain tradeoffs and migration stages. The strongest candidates can challenge an unnecessary microservices proposal, explain failure modes, and identify which questions require experimental evidence.
Use a combination of professional networks, targeted communities, referrals, specialist recruiting partners, and appropriate portfolio reviews. Evaluate applied judgment through a small practical exercise or discussion of a comparable project. Where the role involves access to sensitive systems or data, require clear security and confidentiality arrangements before giving candidates production access.
Avoid two common screening failures: Designing for fashionable patterns — Complexity should follow demonstrated requirements rather than technology trends. Architecture without delivery feedback — Decisions remain untested when architects do not review implementation and operations.