What separates a strong A-level CS tutor
Three things. First, code fluency: they should be able to write a working binary tree insertion in Python live during the trial lesson, not look it up. Second, mark-scheme awareness — they should know that AQA Paper 1 weights efficiency analysis heavily and that OCR rewards specific terminology like “polymorphism” over a paraphrase. Third, NEA realism: they should tell your Year 12 child that an over-ambitious project (a full e-commerce site, an AI chatbot) will tank their NEA marks because the documentation can’t keep up. The tutor who says “let’s pick something smaller and document it properly” is the one who gets your child a clean A.
A note on personality. CS A-level pupils tend to be self-directed and comfortable with online tools. They get bored fast with handholding. The right tutor pushes them to debug their own code first, intervenes after 5 minutes of stuck rather than 30 seconds, and treats them as a junior developer rather than a child to be coddled. Trial lessons let you check that fit.
What’s on each board
Quick orientation:
- AQA — Paper 1 (on-screen programming exam, 40%), Paper 2 (theory, 40%), NEA (20%). Programming-language-of-choice for Paper 1.
- OCR H446 — Paper 1 (computer systems, 40%), Paper 2 (algorithms and programming, 40%), NEA (20%). Both written papers; no on-screen.
Topics that wreck the most students at exam:
- Recursion (especially recursive trees)
- Big O complexity analysis (O(1), O(log n), O(n), O(n²))
- Hashing and collision resolution
- TCP/IP stack vs OSI model — many mix the two up
- Boolean algebra simplification using Karnaugh maps
- Pointers, references, and pass-by-value vs pass-by-reference
A good tutor knows where each lurks in past papers and drills accordingly.
Pitfalls and a real case
The big trap is the “I’m good at coding so I’ll be fine” student. The exam isn’t a coding exam in the way a coding interview is — it rewards specific terminology and mark-scheme phrasing. Bright self-taught coders sometimes drop a grade because they wrote answers in their own language instead of the spec’s. The fix is past-paper practice with strict marking.
The other trap is the NEA submitted at midnight before the deadline, undocumented. NEAs are typically 60-100 pages of report. A weekend rush won’t get marked above 40/75. Plan it in October, write as you build, and your tutor reviews chunks weekly.
A real example: Year 13 from a state grammar in Trafford, OCR, predicted B in October. Tutor diagnosed weak Big O understanding and a chaotic NEA structure. Twelve £60 sessions across the year — six on theory drilling, six on NEA review. June: A*. NEA scored 71/75. Total tutor spend £720. The student went on to read computer science at Manchester.
Pricing, fees and how to book
A typical A-level CS contract — Year 12 January through to Year 13 May — is around 40-50 sessions, mixing weekly theory and NEA reviews. At £55/hour that’s £2,200-£2,750. NEA-only mentoring (8 sessions of 90 minutes) is roughly £660-£800.
TheTutorLink takes 5% per lesson, no subscription, no signing fee. Free trial lesson with any tutor — half an hour, no charge, get them to talk through a recursion question or review a snippet of your child’s code. If the explanation makes sense and the code review is sharp, you’ve found your tutor. Search “A-level computer science”, filter by exam board (AQA / OCR) and language (Python / VB / Java), and book a trial. The strong profiles name specific languages, name the boards they’ve taught this year, and list the universities their previous students went on to.