PRACXAWrite a task that matches the role
Start with the skill you want to check. A short coding task should have a clear problem statement, expected input and expected output. Include a sample so candidates understand the format. Avoid relying on unstated assumptions. If the task is for recruitment, choose work that is relevant to the role rather than a puzzle that tests an unrelated trick.
Choose languages and limits
Create a coding question and choose the supported languages candidates may use. Pracxa supports C, C++, C#, Java, Python and JavaScript. Add starter code where useful and check the execution settings. The code execution time limit is not the same as the overall exam duration: one limits a code run, while the other controls the time available to complete the exam. Explain these expectations before candidates start.
Test the candidate journey
Add the question to an exam and preview the setup. Use a test candidate to confirm that the problem, starter code and sample inputs make sense. Candidates work in a browser-based editor, compile or run their code and submit their answer. Running a sample is useful feedback, but it does not replace submission. Tell candidates to submit their final work before the exam ends.
Review the submitted code
Open the coding review workflow after submission. Read the solution, consider the approach and use your marking criteria consistently. Add feedback and assign marks. A successful run does not automatically mean the answer deserves full marks, and a sample output alone does not cover every case. Complete manual review before treating the overall result as final. For hiring, use the work to guide interview questions alongside other evidence rather than making the test score the only hiring decision.
Continue with Pracxa online exam software, explore platform features, or compare plans and credits.