Databricks' online assessment for interns and new graduates is consistently reported on CodeSignal: four coding problems in 70 minutes, rising from easy to hard, in a proctored session with camera, microphone and screen sharing. Candidates often describe it as harder than most company tests, because the later problems are long implementations rather than short algorithms. This page covers what the Databricks online assessment is, its format and timings, how it is scored, the rules to know before you start, how to prepare and a two-week practice plan.
What the Databricks online assessment is
Databricks publishes no OA specification, so this page reflects candidate reports from 2020 to 2025 and guides checked on November 12, 2026. The four-question, 70-minute shape matches CodeSignal's General Coding Assessment, which CodeSignal describes as four questions of varying difficulty in 70 minutes that you may split however you like. Reports agree on that shape but not on difficulty: one 2025 candidate described an easy first problem and the rest medium to hard, from matrix problems to hard tree problems; a 2024 intern called it three or four hard problems; and a Summer 2025 machine-learning intern report included matrix partitioning and binary search. One Glassdoor review reported 90 minutes instead of 70, so check your invitation.
For the platform's scoring and rules, see the CodeSignal assessment guide; Databricks' later rounds lean on data systems, covered in Spark interview questions.
Format and timings
| Part | What it involves | Time and questions |
|---|---|---|
| Question 1 (easiest) | A short implementation task | Guides suggest about 10 minutes |
| Question 2 | Data manipulation over arrays or strings | About 15 minutes |
| Question 3 | A longer implementation with many edge cases, such as a grid or matrix simulation | About 20 minutes |
| Question 4 (hardest) | An efficient algorithm: trees, binary search on the answer or graphs | About 25 to 30 minutes |
Total: 70 minutes for four questions in most reports; one review reported 90 minutes. The per-question pacing comes from guides to CodeSignal's general format, not from Databricks.
How it is scored
- CodeSignal scores each question on hidden tests and gives partial credit for the tests you pass.
- Databricks publishes no cut-off; reports include candidates who advanced and candidates rejected after strong scores, so treat solving all four as the safe target.
- Older reports quote scores near 850 and newer guides a 200 to 600 range, because CodeSignal changed its scale, so compare like with like.
- Interviewers may look at your assessment code later.
Rules to know before you start
- Candidates report a proctored session with camera, microphone and screen sharing on for the whole test.
- One reviewer said the C++ environment lacked some STL containers they expected, so check your language in practice mode first.
- Invitations commonly give one to two weeks to start; once started, the clock runs continuously.
- Outside help, including AI tools, is not allowed.
How to prepare
- Practice in CodeSignal's own environment so the editor, tests and console are familiar.
- Drill implementation problems: grid simulations, matrix rotations and partitions, and string processing with many edge cases.
- Add binary search on the answer and tree problems for the final question.
- Do full mocks of four problems in 70 minutes, aiming to finish the first two in under 25 minutes combined.
- Use the language you are fastest in; many candidates find Python quicker on implementation-heavy problems.
A two-week practice plan
- Days 1 and 2: take CodeSignal's practice test and read its candidate guide.
- Days 3 to 5: one easy and one medium implementation problem a day, timed at 10 and 15 minutes.
- Days 6 to 8: grid and matrix simulations with careful edge cases, 20 minutes each.
- Days 9 and 10: binary search on the answer, trees and graphs at medium to hard level.
- Days 11 and 12: two full mocks of four problems in 70 minutes, with your camera on to rehearse the setup.
- Day 13: review every kind of hidden-test failure from your mocks.
- Day 14: take the test in one sitting, early in the window.
Related guides: what an online assessment is, the HackerRank assessment guide, Databricks coding interview questions.
On the day, and the mistakes to avoid
- Check the platform, the allowed languages and the time limit in the invitation.
- Try the practice environment or tutorial so the editor and run buttons are not new.
- Use a reliable computer on a stable connection, with other apps and tabs closed.
- Read every problem before starting, and do the quickest ones first.
- Write and run your own edge-case tests before submitting.
- Keep a few minutes at the end to check output formats and resubmit if needed.
Mistakes that cost candidates:
- Writing an elegant solution that fails large hidden tests because of its complexity.
- Mismatched output formats: extra spaces, prompts or debug prints.
- Spending most of the time on one hard problem while easier points go unclaimed.
- Pasting code you did not write, which integrity settings can flag.
- Not reading the input limits, so a solution that works on samples times out.
What happens after the Databricks online assessment
Candidates commonly report a technical phone screen, then a loop with an algorithm round and an implementation round of about 45 minutes each, plus system design for experienced hires and a hiring-manager or behavioral conversation. Guides say data and ML roles may add SQL or data-architecture questions. For the next stage, see software engineer behavioral answers.
Where CoPilot Interview fits
Online assessments are tests you take on your own: outside help is not allowed, and proctoring settings can flag other apps, tab switches or a second voice. Practice beforehand instead. CoPilot Interview is an AI interview assistant; its free AI mock interview prepares you for the interviews that follow the assessment, with questions built from your résumé and the job description and each spoken answer scored out of ten. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Read the invitation carefully and follow your employer's rules.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
What platform does Databricks use for its OA?
CodeSignal, in nearly every intern and new-grad report since 2020.
How many questions are on the Databricks OA?
Four, in 70 minutes in most reports; one review described 90 minutes.
How hard is the Databricks OA?
Harder than average by most accounts: usually one easy problem, then medium to hard problems with long implementations.
Is the Databricks OA proctored?
Candidates report camera, microphone and screen sharing for the full session, so treat it as proctored.
Can I use AI tools during the Databricks online assessment?
No, unless the instructions explicitly allow it. Assessments are meant to be taken on your own, and proctoring settings can flag other apps, tab switches or pasted code. Use AI tools to practice beforehand, and follow your employer's rules.
Practice this interview before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview