Five languages
Python 3, JavaScript (Node.js), Java, C++ and C. The candidate picks the one they write best.
Coding tests
Coding rounds that
run the code.
Candidates write code in the browser, run it against sample cases as they work, and are graded against every case, hidden ones included, when they submit.
Run it while you write.
Graded on every case.
Python, Java, C++, C, JavaScriptSample and hidden casesMixed with other phases
From problem
to grade.
- 1
Write the problem
A statement, the input and output format, and test cases: some shown as samples, the rest hidden.
- 2
Candidates write and run
In any of the five languages, running against the samples as often as the test allows.
- 3
Graded on submit
The submitted code runs against every case, hidden ones included, and the result lands with the attempt.
What a coding phase
gives you.
Hidden test cases
Samples teach the format; hidden cases test the solution. Candidates never see the hidden ones.
Run limits
A wait between runs and a cap per question, so a large sitting shares the runner fairly.
Alongside other phases
Put a coding phase after an aptitude phase and a written one, each with its own timer, in one test.
In the bank with the rest
Coding problems live in the same versioned question bank as objective and written questions.
Proctored like any phase
The same camera, screen and tab-switch rules apply while a candidate codes.
Good questions.
Straight answers.
Something else? Ask us.
Can candidates see the hidden test cases?+
No. They see the sample cases and their own output; the hidden cases only decide the grade.
Does code run on the candidate’s computer?+
No. It runs on Medhank’s own runner, so every candidate’s code meets the same compiler and the same limits.
Is it switched on for every institution?+
Code execution is switched on per institution. Ask us, and coding phases are delivered to your candidates.