How to study for a technical exam: evidence-based method

Most candidates study by re-reading. It feels productive, it is comfortable, and the research is fairly clear that it is among the least effective things you can do with the time.

Here is what works instead, applied specifically to a certification syllabus rather than to undergraduate coursework.

Why does re-reading fail?

Re-reading produces fluency: the material starts to feel familiar, and familiarity is easily mistaken for mastery. The problem is that recognising a passage and being able to reproduce or apply its content are different skills, and only the second one is tested.

The large 2013 review by Dunlosky and colleagues, which assessed ten common study techniques against the evidence, rated rereading and highlighting as low utility. Practice testing and distributed practice were rated high utility — the only two techniques to earn that grade.

That is the whole argument in one sentence: test yourself, and spread it out.

1. Retrieval practice: make yourself produce the answer

Retrieval practice means pulling information out of memory rather than putting it back in. Reading a corrosion-rate formula is putting in. Closing the book and writing it from memory is pulling out.

The effect is not marginal. Karpicke and Roediger’s work found that repeated retrieval produced dramatically better retention a week later than repeated study, even when the study group spent more total time with the material.

In practice, for a certification:

• After reading a section of the standard, close it and write down the requirement in your own words. Then check.
• Use practice questions during study, not only at the end. Every question you answer is a retrieval event.
• For closed-book calculation sections, reproduce formulas onto a blank sheet rather than reviewing a formula card.

The discomfort is the point. If it feels easy, you are probably recognising rather than retrieving.

2. Spacing: distribute the same hours differently

Spacing means separating your study of a topic across days instead of concentrating it. The striking finding is that this works even when total time is held constant — the same hours, distributed differently, produce better retention.

A workable pattern for an eight-week preparation:

Week	Focus
1-2	First pass across all domains. Broad, shallow, no attempt at mastery.
3-5	Domain-by-domain depth, with retrieval after each. Revisit earlier domains weekly.
6-7	Full practice sets. Error analysis. Targeted repair of weak domains.
8	Timed rehearsal under real conditions. Light review only. No new material.

The instinct to cram in week eight is strong and should be resisted. Cramming reliably produces a short-lived peak that has often decayed by the time you sit down.

3. Error logging: group by cause, not by question

This is the technique most candidates skip, and the one that repays the most effort.

After each practice set, log every error — but classify it by why you got it wrong, not by which question it was. A useful set of categories for technical exams:

• Calculation slip — right method, arithmetic or unit error
• Wrong method — reached for the wrong formula or procedure
• Code requirement — did not know or misremembered what the standard requires
• Misread — answered a question you were not asked
• Judgement — knew the rule, applied it to the wrong situation
• Genuine gap — had never encountered the material

The pattern that emerges is far more actionable than a score. Fifteen misses that are mostly calculation slips mean you need timed arithmetic drill and unit discipline, not more reading. Fifteen misses that are mostly code requirement mean the opposite. A raw score of 68% tells you neither.

Review the log weekly and watch which categories shrink. That, rather than the score line, is your real progress indicator.

4. Rehearse the actual structure

Exams have shapes, and the shape is part of the difficulty.

API 510 runs 2 hours 45 minutes closed-book, then a 45-minute break, then 3 hours 45 minutes open-book. That is a long day, and the open-book section is not easier — it is a different skill, testing how fast you can locate a requirement rather than whether you memorised it.

If you have never rehearsed navigating the reference set under time pressure, you will discover on exam day that finding the clause takes four minutes and you have ninety seconds.

At least once before the exam:

• Sit a full-length set in one block, with the real time limit
• Use the same reference format the exam provides — on-screen PDFs, not your annotated paper copies
• Take the break where the exam takes it
• Do not pause, look anything up, or check your phone

Putting it together

A week that applies all four looks roughly like this:

• Three sessions of 60-90 minutes, each covering a domain with active retrieval rather than reading
• One practice set, taken cold and followed immediately by error classification
• A ten-minute weekly review of the error log to decide what next week targets
• One formula sheet written from memory, if your exam has a closed-book calculation component

That is roughly five hours a week. Sustained over eight weeks with spacing and retrieval, it beats twenty-hour weekends of re-reading, and it does so comfortably.