Meet your community.

This sample hiring discussion is not an active vacancy. Imagine a small team recruiting a product designer for a service-booking tool. Rather than asking for a complete redesign over a weekend, the team is considering a short fictional scenario: a user has submitted an incomplete request, and the interface needs to explain what is missing without losing the information already entered.

The candidate would receive the scenario, a simple existing screen and the evaluation criteria in advance. The discussion would focus on the questions they ask, the recovery flow and the clarity of the proposed wording. The team would not use the submission as unpaid work for a real customer. An alternative conversation format would be available if the task format creates an access barrier.

What makes a hiring exercise respectful while still useful for assessing the actual role? How do you prevent a preference for familiar visual style from overwhelming the evaluation? This is a fictional demo role scenario, not a job offer.