Guide
Raspberry Pi Foundation Coding Challenge: from puzzles to code
How the UK Bebras follow-on turns computational thinking into a supervised programmed solution.
Competition Guides
Problem allocation, shared debugging and the difference between several coders and one functioning team.
The Perse Coding Team Challenge is not simply an individual contest with adjacent laptops. Teams solve text-programming problems online at school, with two pupils in the first round and three in the final. That change in team size reveals the competition’s real demand: students have to distribute attention, share discoveries and combine work under a fixed window.
The event is open across Years 7–11 and equivalents, with international schools able to participate for certificates under the current official description. The strongest Round 1 performers move towards a harder final. A team that assigns every problem to its fastest coder wastes the format; the bottleneck soon becomes reading, testing or explaining rather than typing.
CompeteMap recommends PCTC to students who already write text-based programs and can accept peer review. It is less suitable as a first introduction to syntax. Preparation should include shared conventions for input, output, test cases and handover, because team speed disappears when nobody can understand another person’s code.
| Field | Details |
|---|---|
| Competition | Perse Coding Team Challenge |
| Format | Online, supervised at school |
| Team | Two pupils in Round 1 and three in the final |
| Eligibility | Years 7–11 and equivalents under current rules |
| Skill | Text-based programming and team problem solving |
| International entry | Supported, with outcome restrictions stated by the organiser |
Rated Advanced. Teams need reliable text coding, strategic allocation and mature multi-part work under timed conditions.
For current dates, eligibility and registration details, see the Perse Coding Team Challenge competition page.
Checked on 26 September 2026.
Read the whole problem set before coding. Assign an owner and a reviewer, then agree when a stuck solution returns to the team. Parallel work helps only when discoveries are shared.
Use the same input parser, test checklist and naming habits. A teammate should be able to run and inspect another solution quickly. Practise explaining a bug in one minute without taking over the keyboard.
EXPLORE NEXT
Guide
How the UK Bebras follow-on turns computational thinking into a supervised programmed solution.
Guide
What a short puzzle challenge can reveal about logic, representation and a student’s readiness for computing.
Guide
Why preliminary submissions, test cases and the Irish informatics pathway reward robust code rather than clever-looking code.
Comments
Share a question, note, or update.
No comments yet.