Recruiter Submissions Guide
Last updated: September 2, 2026
Submission is your highest-leverage decision on Paraform. Make the right call at the outset to set yourself up for success on the role.
This framework assumes you already have the candidate's consent to submit them for the role.
Step-by-step guide to submission
Every step assumes you already know the role's real must-haves (3–5 non-negotiables) and traits to avoid, from the JD and intake call.
A Quick Disclaimer
If a candidate is missing a must-have or the required work experience, expect more rejections than interviews here. You can still submit and make your case—defend the gap and explain why you think they warrant an interview—just go in expecting a rejection rather than an interview.
Step 1 Do you know this role's real must-haves—the 3–5 non-negotiables and traits to avoid—from the JD and intake call?
Job posts are often vague or aspirational. Ask Parabot to check must-haves vs. nice-to-haves and traits to avoid, then confirm them against the intake call. Still unclear? Post in the role's activity chat.
✓Yes.I have the real non-negotiables, not just the job post.
Step 2 For every must-have, can you point to hard evidence this candidate clears it—a specific story, a shipped example, a number?
“They seem sharp” or “strong background” is not evidence. A specific story is.
✓Yes, all of them.I can back up every must-have with something concrete.
Step 3 Is everything else clean—genuine interest, a story consistent with their resume, and realistic on comp, location, and timing?
These are the green flags from the screen: not lukewarm, not vague on scope, no comp/location mismatch with the role.
✓Yes, clean.No red flags from the screening call.
Every must-have is backed by hard evidence, and the rest checks out. Now make the match obvious on paper.
- Write it as bullets, not prose: map every must-have to the specific evidence.
- Quantify at least one thing (scale, scope, or outcome).
- Never pad it or sell a vibe—the match already works.
✕No, something's off.Lukewarm interest, vague answers, or a comp/location mismatch.
Step 4 Can you resolve that with one more conversation—confirm comp, get clarity on a gap, gauge real interest?
Don't guess. A five-minute follow-up beats submitting on a shaky read.
✓Yes, and it checked out.The follow-up resolved the concern.
The concern resolved, so treat it like any clean match: map every must-have to hard evidence, quantify one thing, and keep the write-up scannable.
✕No, it's still shaky.The concern remains after following up.
The must-haves are covered, but something in the screen didn't resolve—interest, comp, location, or a story that didn't add up. Submitting anyway spends your credibility on a shaky bet.
- Get clarity before you submit, if there's time.
- If not, don't force it—keep the candidate warm for a better-timed match.
✕No, one or more is shaky.I'm inferring, hoping, or unsure on at least one.
Step 3 Is the thing they're missing actually a true non-negotiable, or could it be JD language inflation—a “nice to have” dressed up as required?
Ask Parabot to double-check. If it's JD inflation, make sure you can fill that gap in your write-up. If it's a true non-negotiable, don't submit for this role—if you're the Primary recruiter, message the hiring manager for clarification before you rule it out.
→It's a real non-negotiable.Confirmed via the JD and intake call.
Step 4 Do you have specific, hard evidence of an equivalent or transferable skill—enough to defend the match in one sentence to the hiring manager?
This is the bar for an exception, and it should be rare. “Smart,” “a hustler,” or “a great engineer generally” doesn't count. A different language with clearly comparable, production-grade depth might. If you're building a paragraph to make the case, that's usually a sign it's a pass.
✓Yes, and I can defend it in one line.Concrete, transferable evidence, not a vibe.
You have specific, defensible evidence of an equivalent skill. That's different from hoping the hiring manager won't notice—say it directly in the write-up, don't bury or write around it.
- Name the gap and the transferable evidence in the same breath.
- If you need more than a sentence to make the case, re-run this test—you may be talking yourself into it.
✕No, I'd be writing around the gap.I can't point to specific equivalent evidence.
Final check Is there a different open role (Recommended Roles or AI Calibration) where this candidate would clear the must-haves?
A great candidate is an asset across the platform, not a dead end for this one role.
✓Yes, a better-fit role exists.They clear the bar somewhere else.
This candidate is strong, just not for this opening. Every unique candidate you've screened is an asset across the whole platform.
- Use Recommended Roles or AI Calibration to confirm the new match.
- Screen once, submit where it fits—you don't need to re-run the whole intake.
✕No, nothing fits right now.No open role is a match today.
No hard evidence on a true non-negotiable, and no better-fit role exists today. Submitting here would be hoping the hiring manager overlooks a gap you can already see.
- Don't write around it, pad the write-up, or paste a general bio to sell a vibe.
- Keep the candidate on file—ParaAI re-matches unique candidates against every new role that opens.
- Revisit them when a relevant role opens or your match view flags one.
→It's actually a nice-to-have.The JD overstated it; the true bar doesn't require it.
Then treat the candidate like a normal submission and run the clean-screen check:
Step 4 Is everything else clean—genuine interest, a story consistent with their resume, and realistic on comp, location, and timing?
These are the green flags from the screen: not lukewarm, not vague on scope, no comp/location mismatch with the role.
✓Yes, clean.No red flags from the screening call.
The gap was JD inflation, not a real bar, and the rest checks out. Make the match obvious on paper.
- Map every real must-have to specific evidence, as bullets.
- Note briefly why the “missing” item isn't actually required.
- Quantify at least one thing; don't pad it.
✕No, something's off.Lukewarm interest, vague answers, or a comp/location mismatch.
The must-have bar is fine, but interest, comp, location, or timing didn't add up. Get clarity in one short follow-up before you submit; if it stays shaky, keep the candidate warm rather than spending this shot.
✕Not yet.I'm going off the JD alone.
You can't make this call on a guess. Pull the 3–5 real non-negotiables and traits to avoid from the JD and your intake notes before you evaluate anyone against this role.
- Ask Parabot to check: stack, seniority band, must-haves vs. nice-to-haves, traits to avoid, what the team actually values.
- If it's still unclear, post in the role's activity chat.
- Once you have it, come back and start at Step 1.
End of decision tree. Everything below is reference material, not additional decision steps. Use it to calibrate the calls you just made above: what "must-have" means for your role type, how to read the rejections you'll see, and what to do with a strong candidate who doesn't fit right now.
If it's a Recommended role or ParaAI match, skip the tree above and submit—provided you get clear candidate consent.
Role types
What "must-have" means, by role type.
The bar that actually sinks a submission depends on what you're recruiting for. Know the one that matters for your role.
They need the exact stack at the right level. A strong engineer in a different language often gets passed; show shipped, in-production work in the stack the role names.
Selling or building into the same buyer and market matters more than pedigree.
The portfolio is the must-have. Polished, relevant work in a comparable product beats titles and tenure.
If you cannot point to hard evidence the candidate clears the role's specific must-have, it's a pass—not a "make the case" write-up.
Marketplace dynamics
You'll see more rejections than you're used to.
More roles and more volume means more rejections in raw numbers. It's calibration, not a verdict, and the platform is built for it. Here's how to use it.
Calibrate who you submit. Read the rejection for what it says about fit. Tighten who you submit to this role and similar ones going forward, and update your Role Recap so the bar carries over.
Sharpen their interview prep. Read the same rejection for what it says about performance. Case study judged too shallow? Coach the next candidate to lean into technical depth. Lost on comp? Pre-align comp before you submit.
Reroute the candidate. Someone who interviewed well but lost on fit is proven placeable. Use Recommended Roles and AI Calibration to find a better-matched opening, then resubmit.
Keep them warm. A candidate who moved forward is your warmest lead: tell them what you learned, line up the next role, and the rejection becomes a head start.
Recommended roles
Strong candidate, wrong role (for now).
You sourced this candidate against a role you're working as Primary. A second look at the JD, or a scan of the platform, tells you they're not a fit for it. That's not wasted work—it's the point to shift out of Primary-role thinking and into candidate-first: widen the search past the one role in front of you, and let the platform surface where they actually belong.
Re-run the must-have check. Hold this candidate to the same bar as any submission. If they're missing a true non-negotiable for this specific role, don't submit here just because the sourcing is already done.
Check the rest of the platform. Use Recommended Roles and AI Calibration to see where this candidate actually ranks: Recommended roles, Possible fits, or Other roles. A single submission lets you place them on a role you're not working as the Primary recruiter.
Nothing fits yet? Keep them warm. Don't force a submission just to use the sourcing effort. Log the candidate and revisit them as new roles open. The platform keeps matching unique candidates against new roles automatically.
AI Calibration
Evaluates one specific opportunity in greater depth by weighing the candidate's resume and preferences against the role requirements, hiring-team behavior, pipeline conditions, previous decisions, and rejection patterns.
This is the candidate-first approach Paraform's matching is built around: start with a strong candidate, not an open role, and let the platform help find where they fit.