Junior Programmer

Multiple-choice throughout. You read a short scenario or code snippet and choose one answer; there is no live coding and no project submission. Some items ask you to predict printed output, others to locate a bug or pick the correct declaration. Because answers are fixed, precision matters more than cleverness - read the exact variable names and boundary values before selecting.

Manageable if you have written a few hundred lines of working code; surprisingly hard if you have only watched tutorials. The questions are not trick puzzles, but they punish gaps: a candidate who never really understood scope, or who guesses at whether arguments are passed by value or by reference, drops easy marks. Aim for comfortable fluency rather than expertise.

The official site states which languages are supported, so check there first. If you have a free choice, prepare in the one you can write without looking up syntax. The underlying concepts - scope, iteration, reference versus copy - transfer between languages, and pseudocode questions reward plain reading over idiom knowledge.

Most candidates need a few weeks of consistent practice rather than a weekend cram. A workable plan: two to three weeks on fundamentals, loops and functions; one week on collections, strings and classes; one week on debugging, files and algorithms; then a week of mixed practice questions. Start writing code early - reading alone will not build the fluency tested.

Follow dependency, not percentages. Get variables, operators and conditionals solid first, then loops, then functions and scope - nearly every later question assumes these. Collections and strings come next, then classes and objects, then error handling and files. Leave algorithms and tooling for last; they are smaller areas and easier once the basics are automatic.

Three recur: misreading a loop boundary so the count is off by one, confusing assignment with comparison or value equality with identity, and losing track of scope when a function modifies a parameter. A fourth is answering the code you expected rather than the code printed. Practise tracing values in a table - one column per variable, one row per iteration.

The official programme publishes the current retake rules, including any waiting period and fee. Check its website or your candidate handbook before booking, since policies change. Practically, if you miss narrowly, note which domains cost you marks and re-drill those specifically rather than repeating identical preparation.

Usually no formal prerequisite is enforced, but the exam assumes you can already write and run a small program in at least one language: read input, loop over data, define a function, and use a list or dictionary. If you have never done those unaided, build that base first; a certification will not teach you to code.

It is a signal, not a guarantee. For a first role it can help get past an initial filter and gives you shared vocabulary in interviews, but employers still ask you to write code. Pair it with two or three small finished projects you can explain - a portfolio does more work than a certificate alone. Check how recognised it is in your target market.

The passing score is set and published by the official body and is not fixed across years, so check its site for the current threshold. Generally, multiple-choice scoring gives no partial credit - a nearly right answer scores the same as a wrong one - so when two options look similar, eliminate on a specific detail instead of guessing overall.