A Level Computer Science has two gaps rather than one, and students usually worry about the wrong one.

The first is theory depth: data representation, architecture, networks, databases, all covered in more detail than IGCSE went into. The second is coding fluency: actually writing working programs under time pressure.

Over a summer, only the second is genuinely closeable. It is also the one that determines your first term.

What the syllabus expects you to arrive with

Computer Science is unusual in this cluster because it names the subject as a prerequisite.

Cambridge 9618 recommends that learners starting the course have completed a course in Computer Science equivalent to Cambridge IGCSE or Cambridge O Level.

Compare that with Business 9609, which states it does not expect prior study of business, or Psychology 9990, which says the same about psychology. Computer Science assumes you have been here before.

What it does not name is a grade. Cambridge frames prior study as a completed course; any grade threshold you have been given comes from your school.

The objective that moves

Cambridge splits 9618 into three assessment objectives:

• AO1 — demonstrate knowledge and understanding of the principles and concepts of computer science, including abstraction, logic, algorithms and data representation.
• AO2 — apply that knowledge and understanding, including analysing problems in computational terms.
• AO3 — design, program and evaluate computer systems to solve problems, making reasoned judgements about these.

Now the weightings. AO1 holds steady at 30% for both AS and A Level. AO2 falls from 40% at AS to 30% at A Level. AO3 rises from 30% at AS to 40% at A Level.

So the largest single share of the full A Level is designing, programming and evaluating. Not knowing about programming. Doing it.

Where that lands in the papers

The structure makes it concrete. 9618 has four components:

• Paper 1, Theory Fundamentals
• Paper 2, Fundamental Problem-solving and Programming Skills
• Paper 3, Advanced Theory
• Paper 4, Practical

At AS you take Papers 1 and 2. At A Level you take all four.

The split between them is sharp. Papers 1 and 3, the theory papers, carry 60% of their marks on AO1 and 40% on AO2, with nothing on AO3. Paper 2 inverts that: no AO1 marks at all, 40% AO2 and 60% AO3. Paper 4 is the practical paper and sits almost entirely in AO3.

Read that carefully, because it has a practical consequence. You cannot revise your way through Paper 2 or Paper 4. There are no knowledge marks in them to collect. If your code does not work, there is nothing else in that paper for you to score on.

Fluent, not merely able

This is the distinction that separates students in the first term.

At IGCSE you could usually write the program eventually. You looked up the syntax, tried a few things, and got there. That works when the task is small and the clock is generous.

At A Level the problem is the difficulty, and the syntax is supposed to be invisible. If writing a loop, a function or a file-read still costs you deliberate thought, that thought is coming out of the time you needed for decomposing the actual problem.

The test is simple. Can you write a function that takes a list, filters it on a condition, and returns a count, without looking anything up and without a false start? If not, that is the summer’s work, and it is a genuinely small amount of practice for a large first-term difference.

What to do before September

Four things, in order of value.

Pick one language and get fluent. Whichever you used at IGCSE. Do not start a new one in August; you would spend the window rebuilding syntax fluency you already had, and the examined skills transfer between languages anyway.

Write small programs from scratch, daily-ish. Twenty minutes, one short problem. Not tutorials, not reading. The skill is producing working code from a blank file, and that is only built one way.

Practise writing algorithms on paper. Paper 2 asks for problem-solving and program design, and pseudocode written by hand is a different motor skill from typing with an editor helping you.

Trace code by hand. Take a short program, work out what it outputs line by line without running it. Tracing is a large part of what the theory-adjacent questions actually test.

Why the practical papers cannot be revised around

Worth dwelling on, because it is the structural fact that makes this subject different from every other one in the transition.

In most A Levels, a weak area can be partly offset elsewhere in the same paper. Write a poor evaluation paragraph in Business and the knowledge and application marks are still available to you in the same question.

Computer Science does not work that way at component level. Paper 2 carries no AO1 marks at all: none of its credit is for knowing things. Paper 4 sits almost entirely in AO3, designing and programming and evaluating.

So if the program does not run, there is no partial credit waiting elsewhere in that paper for the theory you revised. The compensation has to come from a different component altogether.

That is the argument for treating coding as the priority rather than the enrichment. It is also why students who enjoy the theory and avoid the keyboard tend to be surprised by their first practical assessment.

The theory gap, honestly

The other half of the transition is real and is not a summer job.

Data representation, processor architecture, networking, databases and system software all go considerably deeper than IGCSE. That depth arrives across two years with a teacher, and it accounts for the AO1 marks that hold steady at 30% throughout.

Trying to pre-learn it is the classic misuse of the gap. Your class covers it at exam pace, and Cambridge designs the full A Level around about 360 guided learning hours against roughly 130 for an IGCSE. Twenty hours in August does not move that.

The coding fluency is different because it is a skill rather than a body of content, and skills decay and rebuild on a timescale a summer can affect.

What the AS year covers, and what it does not

Worth knowing before you start, because it changes what your first year looks like.

At AS Level you take Papers 1 and 2. At A Level you take all four. So the AS year covers Theory Fundamentals and Fundamental Problem-solving and Programming Skills, and the practical component, Paper 4, belongs to the second year.

That has an awkward consequence. If your school enters you for AS at the end of Year 12, your first formal result comes from a year in which the practical paper was not assessed at all. AO3 is 30% of the AS Level and 40% of the full A Level, so the objective that grows is the one you have least evidence about when you are deciding whether to continue.

The practical answer is not to wait. Build coding fluency in Year 12 whether or not it is examined that year, because Paper 4 assesses the later sections of the syllabus and arrives when there is no time left to become fluent from scratch.

Where to start

Open the 9618 syllabus on the Cambridge website. Read the Previous study line, the three assessment objectives, and the paper-by-paper weightings, so you can see for yourself where the AO3 marks concentrate.

Then open an editor and write something small. That is the whole preparation, and it is the part nobody tells you is the priority.

For how Computer Science compares with other subjects in this transition, which A Level subjects have the biggest jump works through them with the syllabus numbers. If maths is also on your timetable, the algebraic fluency it assumes underpins the computational thinking here too, and Tutopiya’s A Level Preparation programme covers that ground through Pre-A Level Mathematics.

Frequently asked questions

What does A Level Computer Science assume you can already do? +

Cambridge Computer Science 9618 recommends learners have completed a course in Computer Science equivalent to Cambridge IGCSE or Cambridge O Level. Unlike Business or Psychology, it does expect the subject to have been studied before, so this is a genuine prerequisite rather than an open entry.

How much programming is in A Level Computer Science? +

More than at IGCSE, and it is separately examined. Paper 2 is Fundamental Problem-solving and Programming Skills and Paper 4 is Practical. The objective covering designing, programming and evaluating systems rises from 30% of the AS Level to 40% of the full A Level.

Do I need to be good at programming before starting A Level Computer Science? +

You need to be fluent rather than merely able. The distinction matters because the exam gives you problems to solve, not syntax to recall. If writing a loop or a function still requires you to stop and think about how, that thinking time comes out of the problem you were meant to be solving.

Should I learn a new programming language over the summer? +

No. Get fluent in one you already know rather than starting another. The skills examined are decomposition, algorithm design and correct implementation, and those transfer between languages. Switching language in August means rebuilding syntax fluency you already had.

Ready to Excel in Your Studies?

Get personalised help from Tutopiya's expert tutors. Whether it's IGCSE, IB, A-Levels, or any other curriculum — we match you with the perfect tutor and your first session is free.

Book Your Free Trial