Junior Web Developer exam-day guide
Junior Web Developer · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring the same ID type and name you registered with. If your registration name and ID differ (for example, a shortened first name or a maiden name), confirm with the provider before test day how to resolve the mismatch, since proctors may refuse entry. Keep a second photo ID in your bag as backup if you have one.
Appointment confirmation and test-center address
Save the confirmation email or screenshot it to your phone, and write down the exact street address plus the building or suite number. Test centers are often inside office parks or shared buildings, so note any parking or entrance instructions in the confirmation. Confirm with the provider whether printed confirmation is required or a digital copy is acceptable.
Know your test format and delivery mode
Confirm with the provider whether your exam is taken at a test center or online with remote proctoring, and whether it is linear or section-adaptive. This changes what you practice in the final days: remote delivery means testing your webcam, microphone, and room setup; test-center delivery means planning travel and arrival time.
Review the published exam objectives one last time
Download or print the official objectives list and tick off each topic you can explain confidently. Spend remaining time only on the unticked items. Do not chase new topics that are not on the objectives list.
Practice the hands-on skills the exam actually names
For a junior web developer exam this usually means writing and reading HTML structure, CSS layout (box model, flexbox, basic grid), JavaScript fundamentals (variables, functions, arrays, objects, events, DOM manipulation), and debugging small snippets. Do at least one timed practice set of code-reading questions, because many items ask you to predict output or spot the bug rather than write a full program.
Scratch paper and writing tool policy
Many providers supply an erasable booklet and marker and prohibit bringing your own paper or pen. Confirm with the provider what is allowed, and if scratch materials are provided, practice tracing short code snippets by hand so you are comfortable without an editor or console.
Personal items plan
Assume bags, phones, watches, and notes must be stored in a locker or left outside the testing room. Plan to travel light: keys, ID, and confirmation only. Confirm with the provider whether a locker is guaranteed or whether you should leave valuables at home or in your car.
Break and timing policy review
Check whether your exam allows scheduled or unscheduled breaks, whether the clock stops during breaks, and whether you must remain in view of the proctor. Confirm with the provider if the rules are not clearly stated in your confirmation email.
Rest and logistics the night before
Set two alarms, plan your route and arrival buffer, and get a normal night of sleep. Avoid cramming new frameworks or libraries the night before; review your own summary notes instead. Eat a normal meal so blood sugar is stable during the test.
Water and comfort items
Rules on drinks and snacks vary by provider, so confirm with the provider whether water is allowed at the desk. If it is not, hydrate before you enter the room rather than risk being distracted by thirst mid-section.
Accessibility or accommodations request
If you need extra time, a separate room, or other accommodations, these are almost always arranged in advance with documentation and are not granted on test day. Confirm with the provider well before your appointment, and if you have not yet requested accommodations, contact them immediately. (needs_review: deadlines and documentation requirements vary by provider.)
Score-report and retake understanding
Know before you sit down how and when you will receive your result and what the retake policy and waiting period are. Confirm with the provider whether you get a provisional score at the end of the test or a later emailed report, and whether a failed attempt has a mandatory waiting period.
Plan the day
Switch from learning to consolidating. Re-read the official objectives list and mark each topic as confident, shaky, or unknown. Build a one-page summary sheet in your own words covering HTML semantics, CSS box model and flexbox, JavaScript data types, scope, functions, arrays and objects, DOM events, and common debugging patterns. Do two or three timed practice sets of code-reading questions and review every wrong answer until you can explain why the right answer is right and each distractor is wrong. Stop starting new tutorials or new frameworks.
Do one full-length timed practice run under realistic conditions: no editor autocomplete, no browser console, no phone. Note where you lost time and decide a pacing plan, for example a target average time per question and a rule for flagging and skipping hard items. Re-check your logistics: confirm the appointment time and time zone if remote, confirm the address and travel time if at a center, and confirm with the provider any open questions about ID, breaks, or allowed materials.
Do a light review only: your one-page summary and the questions you got wrong in practice. Do not take a full practice exam the day before; fatigue costs more than the extra repetition gains. Prepare your bag: ID, confirmation, and nothing prohibited. If your exam is remotely proctored, run the system check now and test your webcam, microphone, browser, and internet connection, and clear your desk and room of notes, phones, and second screens. Set alarms and confirm your route or login time. Go to bed at a normal hour.
Eat a normal meal and avoid heavy caffeine if you are sensitive to it. Glance at your summary sheet for ten minutes, not an hour. Arrive at the test center with a generous buffer, or log in early for a remote exam and complete the ID and room check without rushing. Bring only permitted items to the desk. Take a few slow breaths before the first question and read the instructions on the first screen carefully, especially any section timing rules.
Answer the questions you know quickly and flag anything that needs more than roughly your target time. Do not let a single hard code-tracing question consume five minutes early on. For code-reading items, read the code once for structure, then trace values step by step on scratch paper rather than guessing from the shape of the code.
Return to flagged items with the remaining time, prioritizing ones where a small amount of reasoning will settle the answer. For multiple-choice items, eliminate clearly wrong options first. Watch for classic traps: off-by-one loop bounds, strict versus loose equality, var versus let scoping, event timing, and CSS specificity or box-sizing effects. If a question is genuinely ambiguous, choose the best-supported answer and move on rather than leaving it blank unless the exam penalizes wrong answers, which you should confirm with the provider beforehand.
Check that every question has an answer if there is no penalty for guessing. Confirm you have not accidentally skipped a section or left a flagged item unvisited. Submit deliberately, read any post-test screens about score reporting, and note down what you found hardest while it is fresh, in case you need a retake.
Rules to check
Bring valid government-issued photo ID whose name matches your registration exactly; if it does not match, confirm with the provider before test day how to resolve it, because proctors may deny entry.
Arrive or log in at the time your confirmation specifies; late arrival can result in being turned away and losing your fee, so confirm with the provider what the cutoff is rather than assuming a grace period.
Leave prohibited items such as phones, smart watches, notes, and bags outside the testing room or in the designated storage; unauthorized materials at the desk are typically treated as a conduct violation.
Do not communicate with other candidates, do not attempt to photograph or reproduce exam content, and do not use unauthorized aids; exam content is confidential and misconduct can void your score.
Follow the proctor's instructions and the on-screen rules about breaks; confirm with the provider in advance whether breaks are allowed, whether the clock runs during them, and what you may do during them.
Understand the scoring model before you start: confirm with the provider whether unanswered questions count against you, whether sections are timed separately, and what score is required to pass.
If you experience a technical failure during a remote exam, stop and contact the proctor or support channel immediately rather than continuing, and note the time; confirm with the provider in advance how incidents are documented and resolved.
If you need accommodations or a retake, arrange them through the provider's published process; accommodations are not granted on test day and retake waiting periods, if any, should be confirmed with the provider.