What GCSE Computer Science covers, and what it leaves out

What the specification covers

The DfE subject content divides the course into two broad strands. The first, computer systems, covers how a processor works, how data is stored and moved, how networks are built and secured, how computers represent numbers and text in binary, and the ethical and legal questions around data, privacy and automation. The second, programming and computational thinking, covers algorithm design, writing and testing programs in a text-based language, producing reliable code, and Boolean logic.

Programming in the GCSE is done in a text-based language. The specification does not name one; schools most commonly use Python. Students write short programs, reason about what code does, and sit a controlled assessment programming task that contributes to their final grade. The volume of code is deliberately modest: the course is assessed partly by written paper, so clarity of thought about programs counts as much as writing them.

The Boolean logic section is one of the more mathematically demanding parts of the course. Students draw truth tables and simplify Boolean expressions using logic gates. It sits alongside the theoretical computer science content and provides useful groundwork for anyone who later studies hardware design or computer architecture.

The exam boards

Three exam boards offer GCSE Computer Science in England. AQA (specification 8525) and OCR (specification J277) are the two most widely sat; Pearson Edexcel is the third. All three track the DfE subject content closely, because Ofqual requires them to, so the differences between them are matters of exam style and assessment weighting rather than topic coverage.

Each exam board publishes its full specification and past papers without charge. If you want to see exactly what your child's school covers, look up which board the school uses and read the document yourself. The DfE subject content is also public and short enough to read in an afternoon.

When children choose it and sit it

GCSE options are chosen at the end of Year 9, when most children are 13 or 14. Schools typically ask for choices in the spring term, and the selected subjects start in September of Year 10. Computer Science competes with other optional subjects, including Design Technology, History, a second language and Geography, so not every child who is interested in computing ends up taking it.

The qualification is sat at the end of Year 11 at 16, with results arriving in August. For a child who chose options at 13, the course spans roughly two and a half years of teaching. A child who did not choose it has no formal school pathway to computing after Year 9, when the national curriculum's computing requirement ends.

Choosing Computer Science is not a prerequisite for working in software. Many people who work as engineers and software developers did not sit the GCSE, or took it at a school that did not teach it well. It is a useful qualification for a child who enjoys the subject, not a gatekeeping credential.

What the specification leaves out

Cloud computing does not appear in the GCSE content. Students learn that networks exist and that data is stored somewhere, but they do not deploy software to a server or work with any cloud platform. Linux administration is absent: the terminal and the commands engineers use to manage servers are not part of the course. Version control, the way software teams track and share code changes, gets no mention.

AI gets a brief entry in the ethical and legal topic, as one context among several for discussing data, bias and automation. Students do not build AI systems or evaluate their accuracy. The gap is not a criticism of the people who wrote the specification. It reflects the state of the industry in 2015 and the pace at which those fields moved afterwards.

Web technologies appear in the context of how the internet works, but students do not build and deploy a web application as part of the course. The specification teaches you to think precisely about programs. Shipping them to a real address where other people can use them is a different skill, and it is not in scope.

Why the specification has not been updated

The subject content was published in 2015 for first teaching from September 2016. Reforming a GCSE takes several years. Ofqual sets the timetable, exam boards develop and consult on their specifications, schools plan teacher training and buy resources, and the first cohort to sit the new exams needs at least two years of teaching. A specification written in 2015 can reach 2026 without substantive revision, and this one has.

The computing industry moved faster than that cycle. Cloud platforms became the standard infrastructure for software teams between 2015 and 2020. AI as a practical engineering discipline, accessible through an API with no specialised hardware, became mainstream after 2022. Neither shift is reflected in the GCSE content. There is no published timetable from Ofqual or the DfE for a substantial revision to the computer science specification.

How the gap is filled

School computing in the UK follows a GCSE specification last reformed in 2016. It covers the basics well and does not cover cloud, AI, Linux or putting software live on the internet. We pick up where it stops.

We do not teach the GCSE Computer Science specification. We teach cloud, AI, Linux and software engineering, which it does not cover, and the habits that make the GCSE easier.

The habits matter in both directions. A child who has written Python regularly and debugged their own code will find the GCSE programming content less demanding. The algorithm design and data representation topics are easier when there is practical context behind them. The GCSE tests precise thinking about programs; that is what engineers practise in every session.

Live online sessions run by engineers who work at AWS. From 14, your child deploys to Amazon Web Services in a sandbox we own and pay for, ships code the way engineering teams do, and builds an AI tool that answers questions from their own notes.