The Device Check
Before an assessment starts, Ducker checks that your device can run the workspace. It takes a minute or two, and your timer does not start until it passes.
What it checks
- Your browser and operating system version
- Support for WebAssembly, Web Workers, SharedArrayBuffer, cross-origin isolation, and OPFS
- Roughly how much memory and how many processor cores you have
- Available browser storage
- A short runtime and filesystem benchmark
- Your download speed and latency to our servers
It then downloads and caches the workspace runtime so it is ready locally when you start.
This is a capability check. It is not a fingerprint, and it is not used for advertising.
If it fails
"Browser not supported" — use a recent Chrome or Edge. Safari and Firefox do not currently support everything the workspace needs.
"Not enough memory" — close other tabs and applications and run the check again. If you have less than 8 GB of RAM, use a different machine.
"Mobile device detected" — the workspace needs a laptop or desktop. There is no way around this one.
"Required browser features unavailable" — usually a locked-down work laptop, a browser extension, or a strict privacy setting. Try a normal (non-incognito) window with extensions disabled, or a personal machine.
Slow download — the runtime is a few hundred megabytes on first run. On a weak connection this takes a while, but it is cached afterwards. It costs you no assessment time.
Run it early
You can run the device check as soon as you get the invitation, days before you intend to start. Nothing is revealed and no clock begins — you just find out now rather than at the moment you sit down to work.
If it will not pass and you have tried the above, contact the employer who invited you.