Most sales hiring teams run assessments and ATS workflows as two separate systems. Recruiters copy links between tabs, hiring managers chase score updates over Slack, and RevOps spends Friday afternoons reconciling candidate data across platforms. The result: delayed decisions, inconsistent evaluation, and a pipeline that moves slower than it should.
A native assessment-ATS integration eliminates that friction. When your sales assessment tool talks directly to Greenhouse, every candidate gets evaluated the same way, scores land on the scorecard automatically, and advancement logic runs without manual intervention.
This guide walks through exactly how to set up and launch a Greenhouse assessment integration for sales hiring — using Miki as the implementation example. Whether you're the RevOps person configuring the workflow or the VP Sales approving the rollout, you'll leave with a step-by-step plan and a downloadable checklist.
Why assessment-ATS integration matters for sales hiring
Sales hiring moves fast. The average time-to-fill for a quota-carrying AE role is 48 days, and every day a territory sits empty costs revenue. Assessment tools that live outside your ATS add friction at exactly the wrong moment — when a strong candidate is deciding between your offer and a competitor's.
Here's what breaks without integration:
- Manual trigger delays. A recruiter forgets to send the assessment link. The candidate waits two days. They accept another offer.
- Score visibility gaps. The hiring manager asks "how did they score?" and the recruiter has to log into a separate platform, screenshot the results, and paste them into Slack.
- Inconsistent evaluation. Some candidates get assessed, others don't. There's no audit trail for who was evaluated or why someone advanced without a score.
- Data reconciliation overhead. RevOps spends hours matching assessment records to Greenhouse candidates for quality-of-hire reporting.
A native integration solves all four. The assessment triggers automatically from your Greenhouse interview stage. Scores write back to the candidate scorecard. Advancement rules run based on score thresholds. And every data point lives in one system of record.
For sales teams hiring 10+ reps per quarter, this isn't a nice-to-have — it's the difference between a structured hiring process and a chaotic one.
How the Greenhouse assessment partner workflow works
Greenhouse supports a standardized assessment partner integration model. Here's how the data flows when a tool like Miki is connected as an assessment partner:
The core loop:
- A candidate reaches the assessment stage in your Greenhouse interview plan.
- The recruiter (or an automated rule) clicks Send Test on the candidate's profile.
- Greenhouse sends a webhook to Miki with the candidate's details and the job context.
- Miki creates the assessment session and emails the candidate a personalized assessment link.
- The candidate completes the assessment — chat simulation, voice simulation, or video roleplay depending on your configuration.
- Miki scores the assessment and sends a webhook back to Greenhouse with the results.
- Scores, trait breakdowns, and a link to the full report appear on the candidate's scorecard in Greenhouse.
- The hiring team reviews results directly in Greenhouse and makes an advancement decision.
What gets written back to the scorecard:
- Overall score (0–100) calibrated to your sales role benchmarks
- Trait breakdown scores — objection handling, discovery depth, closing instinct, coachability, product knowledge application
- Report link via
partner_profile_url— one click opens the full Miki assessment report with conversation transcripts, AI analysis, and coaching notes - Status updates via webhook — assessment sent, started, completed, scored
The recruiter never leaves Greenhouse. The hiring manager never asks "where do I find the results?" Everything lives on the scorecard.
Setting up the send-test flow in Greenhouse
Setup takes about 30 minutes with admin access to both Greenhouse and Miki. Here's the step-by-step.
On the Miki side:
- Navigate to Settings → Integrations → Greenhouse in your Miki dashboard.
- Generate your API credentials (partner API key and webhook secret).
- Configure your default assessment type for Greenhouse-triggered candidates — most sales teams start with the chat simulation for speed, then add voice or video for later stages.
- Set your score delivery preferences: full trait breakdown or summary score only.
On the Greenhouse side:
- Go to Integrations → Assessment Partners in your Greenhouse admin settings.
- Add Miki as an assessment partner using the API key from step 2 above.
- Open the job's Interview Plan and add an assessment stage where you want the evaluation to occur.
- Assign Miki as the assessment partner for that stage.
- Configure the trigger: manual (recruiter clicks Send Test) or automatic (triggered when the candidate enters the stage).
Two primary use cases to configure:
UC1 — ATS-primary flow (most common): The candidate applies through Greenhouse. The recruiter reviews the application and advances the candidate to the assessment stage. Greenhouse triggers Miki via the send-test flow. Miki sends the assessment, scores it, and writes results back to the Greenhouse scorecard. The hiring team reviews and decides — all inside Greenhouse.
UC2 — Miki-primary flow (for high-volume top-of-funnel): The candidate starts in Miki — perhaps via a job posting link or a direct outreach campaign. Miki runs the assessment first. When the candidate scores above your threshold, Miki pushes the candidate into Greenhouse with the scorecard data already attached. The recruiter picks up a pre-qualified, pre-scored candidate.
You can run both flows simultaneously. UC1 handles inbound applicants through your careers page. UC2 handles outbound sourced candidates or assessment-first hiring campaigns.
Auto-push trigger options for UC2:
on_complete— push every assessed candidate to Greenhouse regardless of score (useful when you want the full picture in your ATS)on_threshold— push only candidates who score above a threshold you define (e.g., 65/100), keeping Greenhouse clean and focused on qualified candidates
Configure these in Miki's integration settings under Push Rules.
Score routing and candidate advancement logic
Raw scores are useful. Score-based routing is powerful. Here's how to configure automatic advancement logic so your pipeline moves without manual bottlenecks.
In Miki's integration dashboard, set your routing rules:
- Auto-advance threshold: Candidates scoring above X (e.g., 75/100) automatically move to the next interview stage in Greenhouse. No recruiter action required.
- Review band: Candidates scoring between X and Y (e.g., 55–74) stay at the assessment stage with a flag for manual review. The recruiter decides.
- Auto-reject threshold: Candidates scoring below Y (e.g., below 55) receive an automated rejection from Greenhouse, with the assessment data logged for compliance.
What appears on the Greenhouse scorecard:
The scorecard entry includes the numeric score, each trait score as a separate attribute, and a direct link to the full Miki report. Hiring managers click the partner_profile_url link to see the full conversation transcript, AI analysis, trait-by-trait breakdown, and specific moments from the simulation that influenced the score.
The bidirectional sync dashboard in Miki shows you real-time status for every candidate:
- Assessment sent (pending candidate action)
- Assessment started (candidate is in-progress)
- Assessment completed and scored
- Score synced to Greenhouse
- Candidate advanced / held / rejected in Greenhouse
This gives RevOps a single view of pipeline health without switching between platforms.
What the hiring manager sees vs. what RevOps configures
This distinction matters for rollout buy-in. The hiring manager's experience should be simple. RevOps handles the complexity behind the scenes.
What the hiring manager sees:
- A new section on the candidate's Greenhouse scorecard with the Miki assessment results
- An overall score with a clear benchmark (e.g., "82/100 — above your team's 75th percentile")
- Trait scores for the competencies that matter for the specific role
- A "View Full Report" link that opens the detailed Miki assessment page — conversation transcript, AI coaching notes, specific strengths and development areas
- A green/yellow/red indicator based on the thresholds RevOps configured
What RevOps configures (and the hiring manager never touches):
- Which assessment type triggers at which interview stage
- Score thresholds for auto-advance, review, and auto-reject
- Which traits appear on the scorecard vs. which are available only in the full report
- Push rules for UC2 (Miki-primary) flows
- Webhook retry and error handling settings
- Role-specific benchmarking calibration
- The bidirectional sync dashboard monitoring
The goal: the hiring manager's workflow doesn't change. They review candidates in Greenhouse like they always have. The assessment data is just there — accurate, current, and actionable. For the VP approving this rollout, that's the pitch: better data with zero workflow disruption for your team.
Stakeholder ownership: who owns what in the rollout
A clean integration requires clear ownership. Here's the RACI for a Greenhouse + Miki rollout:
| Stakeholder | Owns | Timeline |
|---|---|---|
| RevOps / Recruiting Ops | Integration setup, score routing configuration, testing, ongoing monitoring | Weeks 1–3 (setup), ongoing (monitoring) |
| VP Sales / Hiring Manager | Define success criteria, approve score thresholds, review pilot results | Week 1 (input), Week 4 (review) |
| Talent Acquisition Lead | Recruiter training, candidate communication templates, workflow documentation | Weeks 2–3 |
| IT / Systems Admin | Greenhouse admin access, API credential management, security review | Week 1 |
| Miki Customer Success | Integration configuration support, benchmark calibration, troubleshooting | Weeks 1–4 |
Critical handoff: RevOps proposes the score thresholds. VP Sales approves them. This prevents the scenario where operations sets arbitrary cutoffs that hiring managers override constantly, undermining the entire system.
Common integration mistakes and how to avoid them
After hundreds of Greenhouse integration deployments, these are the mistakes that cause the most pain:
1. Skipping the pilot. Rolling out to all open roles simultaneously means every edge case hits at once. Start with one role, one recruiter, one hiring manager. Fix the workflow issues before scaling.
2. Setting thresholds without baseline data. Don't pick "70 as the auto-advance score" because it feels right. Run assessments on 20–30 candidates first with all results in the review band. Analyze which scores correlate with interview performance, then set thresholds based on data.
3. Not training recruiters on the candidate experience. Recruiters need to know what the candidate sees — the assessment invitation email, the simulation experience, the timeline. When a candidate asks "what's this Miki assessment?" the recruiter should have a confident, enthusiastic answer.
4. Ignoring webhook error handling. Webhooks fail. Networks timeout. APIs have maintenance windows. Configure retry logic and monitor the sync dashboard for stuck candidates. A candidate who completed the assessment but whose score never reached Greenhouse is a silent pipeline killer.
5. Over-automating too early. Auto-advance and auto-reject are powerful, but premature. Use them only after you've validated that your thresholds accurately predict hiring outcomes. Start with manual review for all candidates and graduate to automation as confidence builds.
6. Forgetting the rejection experience. If you auto-reject below a threshold, make sure the rejection message is thoughtful. "Thank you for your time" is the minimum. Consider offering brief feedback or suggesting they reapply after developing specific skills.
7. Not connecting assessment data to quality-of-hire metrics. The whole point of structured assessment is to improve hiring outcomes. If you're not tracking how assessment scores correlate with 90-day ramp, quota attainment, and retention, you're leaving the most valuable insight on the table.
Launch checklist: from pilot to full rollout
Week 1 — Foundation:
- Miki account configured with Greenhouse API credentials
- Assessment type selected and customized for your sales role
- Greenhouse interview plan updated with assessment stage
- Send-test flow verified with a test candidate
- Score delivery confirmed on Greenhouse scorecard
- Stakeholder alignment meeting completed (VP Sales, RevOps, TA Lead)
Week 2 — Pilot prep:
- Pilot role and recruiter identified
- Score thresholds set to "review band" only (no auto-advance/reject yet)
- Recruiter trained on candidate-facing experience
- Hiring manager briefed on scorecard format and report access
- Candidate communication templates updated to mention assessment step
Weeks 3–4 — Pilot execution:
- 20–30 candidates assessed through the integration
- Sync dashboard monitored daily for errors or stuck candidates
- Recruiter and hiring manager feedback collected
- Score distribution analyzed against interview outcomes
- Threshold recommendations prepared based on pilot data
Week 5 — Review and calibrate:
- Pilot results reviewed with VP Sales and hiring managers
- Score thresholds adjusted based on data
- Auto-advance and auto-reject rules configured (if validated)
- Workflow documentation finalized
- Decision made: expand to additional roles or iterate
Weeks 6–8 — Scale:
- Integration rolled out to all target sales roles
- All recruiters trained
- Monitoring cadence established (weekly sync dashboard review)
- Quality-of-hire tracking connected to assessment scores
- 30-day post-launch review scheduled
For a detailed version of this checklist with templates and configuration guides, download the full rollout document below.
Download the Greenhouse rollout checklist
We built a Greenhouse + Miki rollout checklist that covers everything above — pre-launch stakeholder alignment, workflow setup on both sides, score routing configuration, a testing plan template, hiring manager communication templates, and a post-launch review cadence.
It's the same document our customer success team uses when onboarding new Greenhouse customers.
Download the Greenhouse Rollout Checklist →
Ready to connect Miki to your Greenhouse instance? View the full integration details → or book a demo to see the send-test flow, scorecard sync, and bidirectional dashboard in action.
If you're earlier in the evaluation process, start with our VP Sales guide to ATS integration for the strategic case, or explore Miki's pricing — $500/month for unlimited candidates, unlimited assessments, and full Greenhouse integration included.
Frequently Asked Questions
Does Miki integrate with Greenhouse?
Yes. Miki is a Greenhouse assessment partner with native send-test support, score sync, and candidate advancement automation. The integration uses Greenhouse's standard assessment partner API, which means it works within your existing Greenhouse workflow — no custom development required.
How do assessment scores appear in Greenhouse?
Scores, trait breakdowns, and report links are written to the candidate's scorecard automatically after the assessment completes. The hiring manager sees the overall score, individual trait scores (objection handling, discovery, closing instinct, etc.), and a direct link to the full Miki report — all without leaving Greenhouse.
Can you trigger assessments automatically from Greenhouse?
Yes. Configure the send-test trigger at any interview stage, and Miki sends the assessment link to the candidate automatically when they enter that stage. You can also keep it manual — the recruiter clicks Send Test when they're ready. Most teams start manual and switch to automatic after validating the workflow.
What if we use Miki as the primary entry point instead of Greenhouse?
Miki supports a push-to-Greenhouse flow where assessed candidates are created in Greenhouse with their scorecard and assessment data attached. This is ideal for high-volume top-of-funnel hiring or assessment-first campaigns where you want to pre-qualify candidates before they enter your ATS. Configure auto-push to trigger on_complete (every candidate) or on_threshold (only above a score you set).