Build · Create · Ops & Automation
Reference-check call script and scorecard
A structured reference-check script with a confidentiality preamble, probing questions, and a numeric endorsement scorecard.
You receive: A JSON object: { candidate_label, role_title, confidentiality_preamble_field, relationship_question_field, questions[] (each {prompt, probes_for enum: strengths-weaknesses|reliability|open-mindedness|collaboration|other, followup_field}), endorsement_capture {scale_min, scale_max, why_required bool}, scorecard_fields {summary, recommendation enum: strong-yes|yes|reservations|no} }.
Part of Lead Team
Opens soon
This play is verified and ready. It opens soon, once sign-in and payments are live.
Example
A sample of what this play produces. Your result is generated for your inputs.
Candidate label
Jordan Ellis
Role title
Senior Backend Engineer
Confidentiality preamble field
Thanks for making time today. This call is confidential: nothing you say will be shared with Jordan, and your name will not be attached to any notes that leave this conversation. I want to ask some direct questions about working with Jordan, and I would rather hear a candid, mixed picture than a polished one. Are you comfortable with that?
Relationship question field
Before we get into specifics, tell me how you worked with Jordan: your role at the time, how long you overlapped, and whether you were their manager, peer, or direct report.
Questions
| Prompt | Probes for | Followup field |
|---|---|---|
| Walk me through a project where Jordan owned a backend system end to end. What was strong about their approach, and what would you have wanted done differently? | strengths-weaknesses | If they only mention strengths: what is one thing Jordan themselves would admit they need to work on? |
| Describe a time Jordan committed to a deadline or an on-call responsibility. Did they follow through, and how did they communicate if something slipped? | reliability | Was there ever a time they missed a commitment without flagging it early? What happened next? |
| Tell me about a time someone challenged one of Jordan's technical decisions or code review comments. How did they respond in the moment? | open-mindedness | Did their position change, or did they hold firm? Looking back, was that the right call? |
| How did Jordan work with people outside engineering, like product managers or support? Give me one specific example. | collaboration | Was there ever friction with a non-engineering partner, and how did it get resolved? |
| Among engineers at Jordan's level that you have worked with, where would you rank them, and why? | other | What would move them up a notch from where they are today? |
| If Jordan asked you directly what they should improve before starting a new role, what would you tell them? | strengths-weaknesses | Is that a coaching gap they can close quickly, or something more fundamental? |
Endorsement capture
Scorecard fields
Closing field
That covers everything I needed to ask. Thank you for the candid answers, this is genuinely useful for our decision. Is there anything else about working with Jordan that you think I should know before we wrap up?
Get early access to STUD the day it goes live.