Start with a hiring brief that describes an actual problem, relevant environment, and acceptance tests. Ask candidates to examine conflicting stakeholder requests and produce measurable acceptance criteria. Good analysts identify assumptions, clarify ownership, and explain how they would test whether a change improved outcomes. For system projects, inspect prior process diagrams, user-story quality, and handling of edge cases rather than counting how many workshops the candidate ran.
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: Confusing outputs with outcomes — A polished document does not prove that users can execute a better process. Skipping exception paths — Happy-path requirements leave the most expensive handoffs unresolved.