Add reference checks to the hiring process #4205
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ZJvandeWeg
force-pushed
the
zj-ref-checks
branch
from
d3a7d0d to
da590ce
Compare
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
allthedoll
requested changes
Dec 16, 2025
Contributor
allthedoll
left a comment
allthedoll
left a comment
There was a problem hiding this comment.
This is a strong v1 addition to the handbook! ✨
Changes in this review focus on clarifying intent and improving usability so reference checks are lightweight, humane, and used as context rather than a gate. ❤️
Key updates:
- Reframed reference checks as a late-stage input that validates interview signals and informs onboarding, not a hiring veto
- Added flexibility around number and source of references (especially for currently employed candidates)
- Clarified preference for live conversations over async forms
- Tightened and humanized reference questions so they can be read aloud verbatim, using the candidate’s name
- Removed overly evaluative language (rankings/percentiles) in favor of comparative, example-driven prompts
- Added guardrails around optional "backdoor" references
- Explicitly tied reference insights to onboarding and early manager check-ins
Overall, this keeps reference checks high-signal and low-burden while reinforcing manager judgment and onboarding responsibility. 💪🏼
Contributor
|
This PR has been left hanging so I went ahead and committed my suggestions and we can iterate. 💅🏼 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I've come around to reference checks, let's start doing them.
Related Issue(s)
Checklist