Timed coding assessments, AI-assisted sections, hidden test cases, proctoring rules and when a retake is worth it.
6 questions in Early Careers, Internships & Graduate Hiring.
Use code tracing, not reading. Write a small table with one column per variable and one row per step, count loop iterations from the bounds first, and apply the language's own rules for integer division, references and evaluation order. Skim the options to see which rule the question is testing.
Proctored assessments usually require a verified ID, a webcam showing your face, a quiet room with nobody else present, one screen and only allowed materials. Read the rules before the day, set up so your eyes stay on the screen, and if anything goes wrong, note it and contact the support channel in your invitation.
Retake an online assessment only after you know which section cost you and have practised that section under the same timer. First check the invitation or ask the recruiter whether a new score replaces the old one and whether other employers can see either attempt.
An AI-assisted assessment section scores whether you understand the code before you change it, whether you verify every change by running the tests, and whether you can explain what you changed and why. The assistant speeds up reading and typing, but judgement is yours, and clever prompting earns nothing by itself.
Spend the first few minutes reading all four problems and their constraints, then solve them easiest first so points are banked early. Give each a time box, submit a working version once it passes your own checks, and take partial credit on hidden tests rather than chase one perfect answer.
Turn each constraint into a test: empty input, one element, the maximum size, duplicates, negatives, totals that overflow a 32-bit integer and inputs big enough to time out. Then compare your solution with a brute force on small random inputs; the first input where they disagree is your missing hidden test.