Some take-home assessments are AI-assisted — you solve the problem using a coding assistant we provide instead of entirely on your own. Your recruiter will tell you if this applies to you. If it does, see the AI-Assisted Coding guide for setup and what’s different; everything on this page still applies to you too.
What to Expect
- Deadline: you have 5 days from your invitation to submit your work
- Format: a written problem statement you solve at your own pace, then upload as a ZIP file
- Environment: your own editor and machine
What’s Being Evaluated
Every candidate applying to the same job gets a uniquely written problem scenario, so answers can’t be shared or looked up — but the difficulty and what’s expected of you stay the same for everyone applying to that job.
How to Prepare
Before You Start
- Read the whole problem statement first. Note anything it asks you to submit — specific files, a README, run instructions, and so on.
- Check your deadline on the assignment page, not your email. If your recruiter resends your invitation, your deadline resets to a fresh 5-day window from the resend.
- Plan your packaging. Your final ZIP has a 50MB total limit and a 5MB per-file limit. If a file is too large, the upload simply won’t go through — you’ll get an error naming the file, so you can shrink or remove it and re-upload.
Packaging Your ZIP File
Technical/coding assessment: remove dependency and build folders before zipping —node_modules, dist, build, venv, .git, and similar. Include only your source, config, and any requested README.
Supported File Formats
Most common file types are fine to include:- Source code, text files, PDFs, Word/Excel documents, and images are all read directly as part of your submission. Very long individual files may only be partially read, so keep source files reasonably sized rather than dumping everything into one giant file.
- PowerPoint slides (
.ppt/.pptx) aren’t read directly today — convert them to PDF before zipping if your assessment involves slides. - Audio and video are fine to include (for example, a recorded pitch or a walkthrough), but they’re stored and viewable rather than analyzed for content. Don’t rely on one to convey something you need to be scored on — put the substance in writing too.