The useful question is not whether someone has seen the platform. It is whether their skills match the workstream, project stage, and operating reality the team needs to move.
A strong profile connects configuration details to workforce practices, integrations, testing, stakeholder decisions, and what the team must sustain after go-live.
Ask for the workstream, role, project stage, and kind of ownership—not only a platform keyword.
Clarify the decisions, artifacts, scenarios, issues, or handoffs that define success.
Plan for documentation, coaching, and the support rhythm the internal team will inherit.
Tell us whether the need is implementation, configuration, time and attendance, integration delivery, optimization, or support. Then add the timing and the result the person must protect.
Share the workstream, project stage, and skills the team is missing.