A-Level Computer Science Tutor: What to Check Before You Book

The short answer: an A-level computer science tutor is a subject specialist who can genuinely program, coach a student through demanding theory — algorithms, data structures, computation and complexity — and, crucially, guide the coursework project that counts towards the final grade. When you are choosing one, the thing that matters most is not a polished profile or a run of five-star reviews; it is whether you can actually verify that the tutor knows the current specification, can code well beyond A-level standard, and has been checked to work safely with a young person. On Tutorwise, that credibility is not something a tutor claims about themselves — it is a score built from real, checkable signals, so you are weighing evidence rather than a sales pitch.

This guide explains what an A-level computer science tutor really does, how the qualification is built — including the programming project that trips up families used to GCSE — and how to tell a genuinely credible tutor apart from a confident-looking listing, using checks that hold up rather than ones that simply feel reassuring.

What an A-level computer science tutor actually does

A-level computer science is a large step up from GCSE, and a good tutor treats it as a different subject rather than a harder version of the old one. The programming is deeper: a student is expected to write structured, object-oriented code, use recursion comfortably, and reason about data structures like stacks, queues, linked lists, hash tables, trees and graphs rather than just simple lists. The theory is broader and more abstract too — how algorithms are analysed and compared using Big-O complexity, how processors execute instructions at the level of assembly code, Boolean algebra and logic, the mathematics of computation including finite state machines and the limits of what a computer can decide, plus databases, networking and the ethical questions that surround the field. A tutor who is comfortable with GCSE material but hazy on recursion, complexity or the theory of computation is not equipped for A-level work.

What this means in practice is that A-level rewards understanding built on top of real programming fluency. A student cannot memorise their way through it, because the exam questions ask them to design an algorithm for an unseen problem, trace recursive code, or explain why one approach scales better than another. So a strong tutor spends less time drilling facts and more time building durable skills: how to decompose a hard problem before writing any code, how to choose the right data structure for a task, how to reason about efficiency, and how to write about abstract ideas in the precise language a mark scheme expects. A tutor who only sets past papers and marks them is doing half the job. The half that moves grades is teaching the student to think like a programmer and answer like an examiner.

How the A-level exam is built — and the project that counts

Knowing the shape of the qualification helps you judge whether a tutor really teaches it, and A-level computer science has one feature that catches families off guard. Alongside the written papers there is a substantial programming project, the Non-Exam Assessment or NEA, and unlike the GCSE project, this one counts. According to the AQA and OCR A-level computer science specifications, the programming project is worth 20 per cent of the final grade. It is a genuine piece of software the student analyses, designs, builds, tests and evaluates over many months — far closer to real development than anything at GCSE — and it needs proper technical supervision, not just encouragement.

The written papers make up the rest, and the exact structure depends on the board. The main boards are AQA (specification 7517) and OCR (H446), with Eduqas and WJEC also offering the qualification. AQA sets one on-screen practical paper, where students program live at a computer against preliminary material issued in advance, and one written paper on theory. OCR sets two written papers — one on computer systems, one on algorithms and programming — with the practical work concentrated in the NEA. So the first question to ask a prospective tutor is simple: which board does my child sit, and have you taught that specification recently? A tutor who has to look up whether the exam is on-screen or on paper is not the right fit for exam-year work.

The board choice also shapes the programming language. Most schools teach Python, but some use C#, Java or VB.NET, and a tutor who is fluent in one is not automatically fluent in another. A good tutor confirms the language your child is assessed in and can work in it confidently, while also coaching the student to read the exam-board pseudocode style, which is not identical to any real language. Getting this fit right early saves a term of quiet confusion later.

The programming project — where a real developer earns their fee

The NEA is where an A-level computer science tutor who can actually build software becomes worth far more than one who only knows the theory. A strong project shows genuine complexity — a sensible data model, a real algorithm doing real work, sound testing — and it has to be the student's own. A good tutor does not write the code; that would be malpractice and the boards check for it. Instead they teach the skills the project demands: how to scope a problem so it is ambitious but finishable, how to structure a program so it does not collapse under its own weight halfway through, how to test methodically, and how to write the analysis and evaluation the mark scheme rewards. This is exactly the kind of hands-on guidance a self-taught enthusiast or a pure exam-crammer cannot give, and it is why verifying that a tutor can genuinely program — not just talk about programming — matters more here than in almost any other subject.

Where students most often lose marks

Knowing where the grade quietly slips away helps you judge whether a tutor is teaching the right things. At A-level, the patterns are consistent. Students write code that would nearly work but mishandle a base case in recursion or an edge case in a loop, and lose marks in questions worth several. On tracing questions, they follow recursive or iterative code too quickly and give the output they expected rather than the one the code produces. In theory answers, they describe a concept in everyday words when the mark scheme wants the precise technical term, so a broadly right answer scores little. Complexity questions go wrong because Big-O was half-learned rather than understood. And the longer, essay-style questions on the impact of technology or the design of a system get thin, one-line answers when the marks reward a developed, structured argument.

A tutor worth booking works on these directly. They train a student to reason carefully about recursion and edge cases, to trace code slowly and honestly, to answer theory questions in the exact vocabulary the specification uses, and to treat complexity and algorithm design as things to understand rather than memorise. None of this is about learning set answers; it is method, practised until it holds up under exam pressure. When you talk to a prospective tutor, ask how they would fix one of these habits — the answer tells you quickly whether they teach the exam or just supervise it.

Why a nice profile is the weakest signal

Choosing any tutor online has a built-in problem: the easiest things to see are the least reliable. A warm photo, a fluent bio and a run of five-star reviews tell you how good someone is at presenting themselves. They do not tell you whether that person turns up prepared, knows the current specification, can genuinely program to a level well above A-level, or has been checked to work safely with a young person. Reviews can be thin, early, or written by people who are not comparing like with like. A claim of "ten years as a software engineer" costs nothing to type and, on most sites, is never checked. Computer science makes this worse than most subjects, because the gap between someone who can talk fluently about coding and someone who can actually teach a seventeen-year-old to design a recursive algorithm and structure a real project is wide, and a bio hides it completely.

According to a 2024 Sutton Trust survey, around 30 per cent of 11 to 16-year-olds in England and Wales have had private tuition at some point, and the pattern continues into the sixth form, where the stakes for a demanding subject like computer science — often taken alongside maths and tied to a university application — are higher still. Many families are making exactly this decision, frequently under time pressure. The stakes are real and the information is poor. That gap between how much a booking matters and how little you can usually verify is the problem worth solving before you part with any money.

How Tutorwise turns credibility into something you can see

This is where Tutorwise works differently, and it is worth understanding because it changes what you are actually looking at. On most platforms a tutor's credibility is a story they tell about themselves. On Tutorwise it is a computed score — the platform calls it Credibility as a Service, or CaaS — assembled from signals the tutor cannot simply assert.

The score is built from several weighted areas rather than one number pulled from reviews. The largest weight goes to delivery — the tutor's actual track record of sessions taught and outcomes on the platform, because what someone has reliably done matters more than what they say they can do. Credentials — evidenced qualifications and subject expertise — carry real weight too, which matters for a technical subject like computer science where a genuine background shows. Then there are the tutor's network and standing on the platform, a trust component covering safety checks, a digital presence measure, and a smaller impact element. No single flattering signal can carry the score on its own.

The trust component is the one parents care about most, and it is deliberately weighted towards the checks that keep a student safe. Within it, an enhanced DBS check counts for the most, followed by verified identity, then completed onboarding, with confirmed email and phone as smaller supporting signals. The order is the point: a criminal-records check on someone whose identity is confirmed is worth far more than a working email address, and the score reflects that. Just as importantly, there is a hard gate underneath the whole system — a tutor gets no credibility score at all until they have verified their identity or completed onboarding. An unchecked stranger does not get a number to hide behind.

So when you compare two A-level computer science tutors on Tutorwise, you are not comparing two self-written biographies. You are comparing two scores, each built from delivered sessions, evidenced qualifications and completed safety checks. A tutor cannot inflate that by writing a better paragraph about themselves or by dropping in the right technical words. Contrast that with an ordinary tutoring directory, where the profile is whatever the tutor chose to type and the "verified" badge, if there is one, often means only that an email did not bounce. The Tutorwise score is not a promise; it is a summary of things that actually happened, and you can see what fed into it. If you want the full version of this thinking, our guide on how to choose a tutor you can actually trust walks through reading a profile as evidence rather than vibes.

What to check before you book

Whether you use Tutorwise or look elsewhere, the same evidence-first habits protect you. Run through this before you commit to a first session:

• Safeguarding first. For any one-to-one work with a young person, confirm an enhanced DBS check and verified identity. This is non-negotiable and should be visible, not something you have to ask about awkwardly.
• Board and language fit. Ask which exam board your child sits — AQA, OCR, Eduqas or WJEC — whether the practical paper is on-screen or written, and which programming language they are taught. Confirm the tutor has taught that specification recently.
• Can they really program. An A-level tutor should be able to write and explain a recursive function or reason about a data structure on the spot, not just talk about computing in general terms.
• Project experience. Ask whether they have supervised the NEA before and how they support it without doing the work — this is where a weak tutor is quickly exposed.
• Evidence over adjectives. Look for a track record you can inspect — sessions delivered, qualifications shown, outcomes recorded — rather than a paragraph of confident description.
• Fit with your child. The best tutor on paper is the wrong one if your child dreads the sessions. A short first session tells you a great deal about whether the two get on.

How tutoring works, and what it costs

A-level computer science tutoring can be online or in person, and both work well. Online suits the subject especially, because a shared screen makes it easy to write code together, run it, and see where it breaks in real time — much closer to how the work is actually done, and ideal for guiding a project remotely. In-person can suit a student who focuses better away from their own devices or wants steady coaching on the written papers. Many families in London and areas like Greenwich mix the two — in person before a mock, online for a focused clinic on a single topic such as recursion, complexity or the project's testing phase.

On Tutorwise, tutors set their own rates and you pay per session, so you can see exactly what a session costs before you book rather than committing to a package. A shorter, focused run of sessions aimed at a specific weakness — say, the theory of computation, or structuring the NEA — often does more than an open-ended weekly slot with no clear target. Decide what needs to improve, then book against that. If your child is taking maths alongside computer science, as many do, the same evidence-first approach applies there too; you can find an A-level maths tutor the same way, and if the year has slipped and you are worried about catching up, our guide on falling behind at A-level is a calmer read than it sounds. Families arriving here from GCSE may also find the GCSE computer science tutor guide useful for a younger sibling.

The bottom line

A good A-level computer science tutor can genuinely program well beyond the syllabus, teaches a method for both the coding and the theory, knows the exam board and mark scheme, can guide the programming project without doing it, and can prove they are safe to work with your child. The hard part has never been finding someone who says they can help — it is telling the credible tutors from the confident ones, which is harder in a technical subject where the right words are easy to borrow. The answer is to judge evidence, not presentation: confirmed identity, an enhanced DBS check, evidenced qualifications and a real track record. Tutorwise builds exactly those signals into a single credibility score, so you can compare tutors on what they have actually done and been checked for, not on how well they describe themselves — and no tutor appears with a score until the checks are in place.

Frequently asked questions

What does an A-level computer science tutor teach?

Both the deeper programming — object-oriented and recursive code, data structures and algorithm design — and the broader theory covered in the written papers, including complexity, computer architecture and assembly, Boolean logic, the theory of computation, databases and networking. A good tutor also coaches exam technique and helps the student plan and build the programming project, without doing the work for them.

Does the A-level programming project count towards the grade?

Yes. Unlike the GCSE project, the A-level Non-Exam Assessment counts. According to the AQA and OCR specifications, the programming project is worth 20 per cent of the final grade, so it needs proper technical supervision over many months, not a last-minute rush.

Which programming language does my child need?

It depends on the exam board and what the school teaches — most use Python, though some use C#, Java or VB.NET. Ask the tutor to confirm they can work in your child's language and can also read the board's exam pseudocode style, since the two are not the same.

How do I know an A-level computer science tutor is actually qualified and safe?

Look for evidence rather than a bio. For safety, confirm an enhanced DBS check and verified identity for any one-to-one work with a young person. For competence, look for evidenced qualifications and a real track record, and ask them to program something on the spot. On Tutorwise these signals feed a single credibility score, and no tutor gets a score until identity or onboarding checks are complete.

Is online or in-person better for A-level computer science?

Both work. Online suits the subject well because you can write and run code together on a shared screen, which is also ideal for guiding the programming project remotely. In-person can suit a student who focuses better away from their own devices or wants steady coaching on the written papers. Many families mix the two depending on the topic and the time of year.