Lift outcomes
From the posting, not from a competency wheel.
Broad prompts can invite very different stories. Job-specific questions kindly name the work: the release, the customer, the tradeoff - so every candidate can show how they would approach it.
From the posting, not from a competency wheel.
Week six, first mess, first conversation.
If it is good in the room, it is good on a link.
Take the three outcomes in the posting. Turn each into a situation the person would actually face in week six. Ask how they would approach the first hour - not whether they are a “self-starter.”
Engineering: a release causes intermittent failures for a small group. What do you do in the first hour? Product: sales wants a custom feature; engineering is on reliability. What happens next? Support: a customer says the rollout failed and they may leave. What does the first conversation sound like?
If the question is good enough for the room, it is good enough for a link. Honrly drafts these from the job and scores the answer against traits you can edit.
Finance: the forecast is wrong and the board meeting is Friday. What do you do tonight? Ops: a vendor misses the only ship date that matters. Design: the stakeholder fell in love with the wrong flow. Legal: sales already promised a clause you cannot give.
Honrly drafts in this spirit from the job you pasted. You can gently edit anything that feels too broad.
A question about the actual work invites a real answer, and a fairer comparison.
A short set is enough to see the work, and kind enough to finish. Skill Rank stays focused.
You can, and it works beautifully when the work is truly the same.
Reuse when the work is the same. Otherwise you are back to a catalog.
Keep a compiler for code. Use Honrly for the hour after the code breaks.
The next candidate is going to apply anyway.
Write the job. Send the assessment. Read the answers before you interview.