Candidates
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
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
- Rubric Change Logs
- Data Architecture - Schema/Model
Data Architecture - Schema/Model
4/18/22
We recently rolled out some changes on the Data Architecture - Schema/Model scenario. We have allowed more flexibility on how a correct solution is reached:
- We have reduced the weight given to arriving at a solution that utilizes a single join table
- We have increased the weight given to ensuring there is a field added to track the onboarding task’s completion status
We have already re-scored recent candidates and your benchmarkers against the new rubric, so you’re comparing apples-to-apples when you evaluate new candidates. We believe these changes make measurable improvements to recognizing stronger candidates. Please let us know if you have any questions!
