Candidates
CoC Messages to Candidates
Why Woven Enforces Unique Candidate Links
ADA Accommodations for Candidates
Getting Started with Woven
How to Create a Support Ticket
How To See/Change Available Languages For A Scenario
Candidates who have previously take a Woven Assessment
Candidate Feedback FAQ
Tips for Maximizing Candidate Completion Rate
Scoring Quality Assurance
Pair programming with a candidate's solution
Downloading a candidate's code from a recommendation
Locating rejected, withdrawn or hired candidates in Woven
Free Trial
Integrations
How to Export Candidate Data from Ashby
Woven customer email address: security and access controls
One Click Candidate Invites to Woven
MacOS: Open generated candidate invite emails by configuring gmail as your email client for mailto
Integrating Greenhouse with Woven
Internal
Roles & Work Simulations
Scenario Timeboxing and Time Limits FAQ
How to Create a Role
Woven and ChatGPT resistance
NEW Role Creation UI
Woven Scoring System and Philosophy
What does a score of 100 mean in Woven?
Increasing Scenario Time Limits
How to Clone a Role
Rubric Change Logs
Data Architecture - Schema/Model
Hard SQL: Two Lawyers Who Worked in the Most Trials Together
Architecture Debugging - Brainstorm
Security & Privacy
- All Categories
- Integrations
- How to Export Candidate Data from Ashby
How to Export Candidate Data from Ashby
Updated
by Shayna Pittman
How do I export data from Ashby to see if the scenarios are predictive?
In Ashby, you can do a custom report for all candidates on your roles with a report close to what is in this screenshot and will need the following:
- Email address
- Candidate job name
- farthest stage reached
- archived reason
- status

Then we can use that to see how well scenario scores are predicting interview success. If we don't have more than 3 folks who have completed their subsequent interview, then we can skip this. Need at least that many datapoints to be very relevant