Hiring decision evidence

Task-Based Hiring: Compare How Candidates Reason About Shop Work

Use fictional shop tasks and consistent criteria to compare hiring evidence. Assess record identification, uncertainty, authority and clear handoff.

DROPS.ST

Web + Telegram. One catalogue.

Run the same catalogue on your website and connected Telegram shop.

Explore DROPS See the shop demo

Written by DROPS.ST.

When hiring for a cannabis shop, use fictional job-related cases and the same criteria to compare how candidates identify records, handle uncertainty and recognize their authority. Record the evidence behind the decision rather than relying on familiarity with software names or an impressive general answer.

DROPS connects products, Customer Accounts, orders and items. Those relationships give you concrete tasks to discuss: interpreting a package quantity, finding the relevant order context or handing off an unresolved decision. The interview can assess that reasoning without giving anyone production access or real work to perform.

Choose tasks from the actual job

Identify a small set of responsibilities the successful applicant will need. Separate essential judgment from interface details that can be taught later.

A support role might need to recognize that a reported payment is not a verified fact. A catalogue role might need to check a package unit before proposing a correction. Explain the case context so a candidate unfamiliar with DROPS can still demonstrate the relevant reasoning.

OPM describes structured interviews using job-related competencies and hypothetical situations. Use that practical format, not its US federal context as Canadian hiring law or a guarantee of future performance. OPM structured-interview guidance.

Use an evidence-based scorecard

Decide the criteria before meeting candidates. The following is an original discussion aid, not a validated assessment or native DROPS HR feature.

Criterion Fictional prompt Evidence to record
Record identification Which item or order reference matters? Candidate identifies relevant facts rather than guessing
Quantity meaning Two packages differ in unit size Candidate checks the unit before calculating
Uncertainty A required fact is missing Candidate separates known information from assumptions
Authority Requested action exceeds the stated role Candidate identifies the decision-maker and stop point
Information handling A case includes unrelated personal background Candidate keeps necessary task facts and routes sensitive questions appropriately
Communication Next worker needs to continue the task Candidate gives a clear question, next step and owner

Use consistent descriptions such as demonstrated, demonstrated with clarification or not demonstrated. Keep the supporting observation. A score without that evidence makes comparison harder to explain.

Keep the exercise fictional and proportionate

Use written case cards with invented references. Do not ask candidates to handle actual customer records, correct the live catalogue, complete orders or send messages. This is an interview exercise, not real unpaid work.

Give candidates the same relevant facts and a consistent opportunity to clarify the task. Arrange appropriate accommodations and check applicable employment and privacy requirements with the responsible person.

Collect only assessment information relevant to the selection purpose. Do not turn the discussion into a personal background dossier. OPC employer guidance notes that workplace privacy obligations vary by province and workplace. OPC workplace privacy guidance.

The fictional training-data guide helps prepare case material without starting from customer exports.

Hypothetical example: a quantity mismatch

Two candidates receive a card showing two similarly named packages with different unit counts. A fictional customer asks whether the second matches an earlier selection.

One candidate checks the unit definition and asks which package the reference identifies. Another confidently treats the names as equivalent. The interviewer records the difference against the predetermined quantity and uncertainty criteria, then uses the same follow-up prompt.

These invented response summaries illustrate evidence recording. They do not establish that one answer predicts success, replace the full hiring review or describe actual applicants.

Compare observations before making the selection

Review each criterion across candidates. Separate what was demonstrated from what the interviewer inferred. If reviewers disagree, compare the recorded response and rubric rather than averaging impressions without explanation.

Do not change the scoring rule because a preferred candidate gave a different answer. Record unresolved evidence and any further appropriate assessment needed. The final hiring decision includes the actual job requirements and employer obligations beyond this exercise.

Treat hiring and access as different decisions

A selected applicant still needs training and an approved permission scope. DROPS has separate order-action controls and administrator-only shop settings. Catalogue editing also includes customer-account edits and wallet adjustments; an interview score does not narrow those grants.

Use the training sign-off checklist after hiring to assess readiness for the defined work and actual access.

DROPS gives the interview concrete shop relationships to discuss. Pair that context with consistent fictional tasks and recorded reasoning so the selection rests on relevant evidence.

Explore DROPS.ST and the shop demos. Define one job task, build its fictional case and agree the evidence you will compare before the interview.

Move from research to a working shop

See how DROPS fits your shop.

Explore the platform and try the demo. Bring your catalogue, ordering and team requirements to a setup conversation.

Explore DROPS See the shop demo Discuss your setup