Alternatives to Woven
Other Recruiting assessment vendors we measure, sorted by how much they publish that Woven does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 25 that differ from Woven on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Woven has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Woven does not” is the one that closes them.
| Vendor | Score | Publishes, and Woven does not | Woven publishes, and they do not | |
|---|---|---|---|---|
| HireVuehirevue.com | 57/100 | 5 Data processing agreement, Data location stated, Uptime SLA with a figure, +2 | 1 Public pricing | Compare |
| Adafaceadaface.com | 48/100 | 4 Data processing agreement, Data location stated, Uptime SLA with a figure, +1 | 2 Status page with history, Certifications named | Compare |
| CodeSignalcodesignal.com | 48/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 Certifications named | Compare |
| Predictive Indexpredictiveindex.com | 48/100 | 4 Subprocessor list, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 Certifications named | Compare |
| Criteriacriteriacorp.com | 43/100 | 4 Data processing agreement, Data location stated, Notice before subprocessors change, +1 | 2 Status page with history, Public pricing | Compare |
| Harverharver.com | 35/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 2 Status page with history, Public pricing | Compare |
| CoderPadcoderpad.io | 48/100 | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | nothing | Compare |
| HackerRankhackerrank.com | 39/100 | 3 Data location stated, Uptime SLA with a figure, HTTPS enforced with HSTS | 1 Status page with history | Compare |
| Traitifytraitify.com | 39/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Public pricing, Certifications named | Compare |
| Coderbytecoderbyte.com | 36/100 | 3 Subprocessor list, Data location stated, HTTPS enforced with HSTS | 3 Status page with history, Public pricing, Certifications named | Compare |
| Codilitycodility.com | 35/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 2 Status page with history, Certifications named | Compare |
| iMochaimocha.io | 30/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 2 Status page with history, Public pricing | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.