Teach programming well: diagnose novice misconceptions, use PRIMM, pair programming and Parsons problems, plan standards-aligned units, assess code fairly and navigate teacher certification.

Teaching Computer Science

## Why it matters

Computing has long had unequal participation. In many countries, girls, students from some racial and ethnic groups, students from low-income families and students with disabilities are under-represented in CS classes and careers. Much of that gap comes from **access** (whether a school offers CS at all) and **belonging** (whether students believe "people like me do this"). A teacher cannot fix every structural problem, but classroom choices make a measurable difference to who enrols, who persists and who succeeds.

## The core idea: belonging and relevance

Two ideas run through the research and frameworks:

- **Belonging:** students who feel they belong in a subject work harder and persist through difficulty. Stereotypes ("CS is for boys", "you need a geek gene") undermine that. There is no evidence for a fixed programming aptitude; skill comes from practice and good teaching.
- **Relevance:** students engage more when projects connect to their lives, communities and interests.

**Culturally responsive** (or culturally relevant) teaching builds on students' cultures, languages and experiences as assets, not obstacles. The **Kapor Center** published a Culturally Responsive-Sustaining CS Education Framework, and CSTA's standards include "fostering an inclusive computing culture" as a core practice.

## Practices that help

**Classroom culture**

- Normalise struggle: bugs are a normal part of programming, not a sign you are bad at it. Share your own bugs.
- Praise strategies and effort ("you traced it line by line") more than speed or "being smart".
- Set norms for help-seeking and for talking about each other's code respectfully.
- Watch for dominance: who answers, who types, who gets interrupted. Use structured turn-taking and pair roles.

**Curriculum and projects**

- Offer project themes with choice: a quiz about students' own interests, a data project on a local issue, an app for a community group.
- Show a wide range of people in computing: examples, guest speakers, case studies.
- Discuss the **impacts of computing**: biased algorithms, accessibility, privacy. Students who see CS as relevant to justice and community are often more motivated.

**Access and accessibility**

- Use tools that work on school devices and low-bandwidth connections; avoid tasks that need a home computer.
- Apply **Universal Design for Learning (UDL)**: multiple ways to learn (video, text, examples), to engage (choice) and to show learning (demo, writing, code).
- Check tools for accessibility: screen reader support, keyboard navigation, colour contrast, captions. Block-based tools vary in screen-reader support.
- Support multilingual learners with visual examples, glossaries and allowing discussion in home languages.

**Recruitment**

- Personally invite students who might not see themselves in CS; personal encouragement from a teacher is a strong factor in enrolment.
- Look at your enrolment data by group and ask counsellors to check placement practices.

## Worked example: rewriting a project brief

Original: *"Build a game where you shoot asteroids. Bonus points for the most explosions."*

Problems: one narrow theme that some students find unappealing; competition on a single measure.

Revised: *"Build an interactive program for someone you know: a game, a quiz, a story or a tool. It must use variables, conditionals and at least one loop. Write two sentences about who it is for and why it would help or delight them."*

The technical requirements are the same; the space for students' identities and interests is much larger.

## Common mistakes

- **Treating inclusion as a one-off lesson.** It is a set of everyday practices.
- **Tokenism:** a poster of a famous woman in computing without changing who participates in class.
- **Assuming access:** homework that requires a laptop and Wi-Fi at home.
- **Calling students "naturals".** It implies others are not, and reinforces the fixed-ability myth.
- **Ignoring disability:** accessible tools and flexible deadlines are part of inclusion.

## Quick recap

- Participation gaps in CS come largely from access and belonging.
- There is no fixed "programming gene"; teach that skill grows with practice.
- Use relevant, choice-based projects, structured collaboration and visible role models.
- Design for access and accessibility (UDL, school devices, accessible tools) and recruit actively.


Apply culturally responsive and inclusive practices so every student can belong and succeed in computing.

Inclusive CS classrooms

Equity in Computer Science

Culturally relevant pedagogy in the computing classroom | Computing education research

Create a free teacher account on Code.org (or the platform you chose) with a professional email address.

Create a class section with a test name (for example 'Practice Period 1') and choose a grade band.

Assign one course or unit to the section and look through the first lesson's teacher materials.

Find how students join (section code, picture or word passwords for young students) and write those instructions as a one-page handout.

Join your own section as a pretend student in a private browser window using an invented name, and complete one activity.

Back in the teacher view, find the progress dashboard and locate your pretend student's work.

Write down your school or district's rules for approving student data tools (US examples: FERPA, COPPA, state privacy laws), and who to ask before using the tool with real students.

Delete the pretend student or archive the practice section when you are done.

## Why it matters

The right tools let students start coding in minutes and let you see their progress at a glance. The wrong ones eat lessons with login problems, installation failures and blocked websites. Choosing and setting up tools is a real part of a CS teacher's job, along with protecting students' data.

## The main kinds of tools

| Kind | Examples | Good for |
|---|---|---|
| **Block-based environments** | Scratch, Code.org App Lab and Sprite Lab, MakeCode | younger students and first courses; no syntax errors |
| **Curriculum platforms with sections** | Code.org, CodeHS, Runestone Academy (CS Awesome for AP CSA) | full courses with lessons, teacher dashboards and progress tracking |
| **Browser code editors** | Python Tutor, online editors built into platforms | quick text-based practice without installs |
| **Local editors** | Thonny (Python for beginners), IDLE, VS Code | older students, offline use, real-world workflow |
| **Assignment and grading** | GitHub Classroom, Gradescope, your LMS (Google Classroom, Canvas) | distributing starter code, autograding, collecting work |
| **Physical computing** | micro:bit, Raspberry Pi, Arduino | engagement, connecting code to the physical world |

Many of these have free tiers or are free for teachers. Features, pricing and age limits change, so check each provider's current education terms before planning around them.

## Choosing tools: questions to ask

1. **Does it fit the course?** Language, level and standards.
2. **Does it run on our devices?** Chromebooks, tablets, locked-down school laptops, slow networks.
3. **What does it cost now and later?** Is the free tier enough for a whole year?
4. **How do students log in?** Single sign-on with school accounts saves lessons.
5. **What student data does it collect?** Is it approved by the school or district?
6. **Is it accessible?** Screen-reader and keyboard support, captions, contrast.
7. **What is the backup?** If the service is down, can you teach the lesson unplugged?

## Student data and privacy

Teachers are responsible for using tools their school allows. In the US, relevant laws include **FERPA** (student education records), **COPPA** (online services and children under 13) and many state student-privacy laws; other countries have their own (for example GDPR in the UK and EU). Practically:

- Use tools your school or district has approved, or ask your technology coordinator before signing students up.
- Prefer platforms that let students join a teacher section without personal email addresses.
- Do not upload student work or names to tools that are not approved.
- Know how to delete student accounts and data at the end of the year.

## Worked example: first-week setup checklist

For a new middle-school class using Code.org:

1. Teacher account created with school email; section created per class period.
2. Students join with a section code; younger students use picture passwords.
3. Course assigned to each section; teacher previews lesson 1 as a student.
4. Login cards printed for each student and a copy kept securely.
5. Test on a school device with the school network, including the student login flow.
6. Unplugged backup activity ready for day 1 in case the network fails.
7. Parent or guardian letter sent explaining the tool, if the school requires it.

## Managing the room

- Use the **teacher dashboard** to spot students who are stuck (no progress) during the lesson, not just after.
- Ask students to put screens down or lids half-closed during instructions.
- Keep a "three before me" rule: check notes, ask a partner, check the hint, then ask the teacher.
- Have an extension task ready so fast finishers do not drift.

## Common mistakes

- **Testing only on your own laptop.** School devices and networks often block things.
- **Signing up students before approval.** Privacy rules exist for good reasons.
- **Changing tools every unit.** Each new tool costs a lesson of setup and confusion.
- **No backup plan.** Platforms go down; unplugged activities save the lesson.
- **Ignoring the end of the year.** Archive work, export what students want to keep and remove accounts.

## Quick recap

- Choose tools for fit, devices, cost, login, privacy, accessibility and backup.
- Many good platforms are free for teachers; check current education terms.
- Use approved tools and follow your school's privacy rules (FERPA, COPPA, state law in the US).
- Test the full student flow on school devices before day 1 and keep an unplugged backup.

## Try it

Open the Do tab and set up a practice class section on a free platform.


Choose free classroom platforms and set up a class section safely and practically.

Classroom tools

Getting Started with CodeAI: Creating a Classroom Section

Decide the setting you are aiming for: public K-12, private or charter school, community college, university, or informal teaching (bootcamps, after-school clubs).

For K-12 in the US, open your state department of education's educator certification page (search '<your state> department of education educator certification'). Record whether the state has a computer science licence, a CS endorsement or allows CS under another subject.

Record the requirements: degree, teacher preparation programme, subject test (some states use a Praxis Computer Science test), background check, and any student-teaching hours.

Look for alternative or career-changer routes on the same official site, and note their conditions (for example teaching on a provisional licence while completing a programme).

If you already hold a licence in another subject, find out how to add a CS endorsement. If you hold a licence from another state, check reciprocity on the official site.

For college teaching, read three current job postings for CS instructors or lecturers near you and record the degree they require (often a master's for community colleges, a doctorate for many university faculty roles).

Check CSTA (csteachers.org) for your local chapter and professional development, and the College Board's AP Central if you plan to teach AP.

Write a one-page route plan with each step, the official link, the date you checked it, and an estimated time and cost.

## Why it matters

You can learn to teach CS well on this platform, but **where and whom you may teach is set by law and by employers**, not by skills alone. Requirements differ by country, by US state, and by the kind of institution. Planning your route early avoids surprises such as discovering that your state has no CS licence and you need a different subject first, or that a college role requires a graduate degree.

Requirements change often. This lesson explains the common patterns and points to official sources; always confirm the details for your location. Checked on 2026-10-23.

## Teaching K-12 in a US public school

In most US states, teaching in a public school requires:

1. **A bachelor's degree.**
2. **Completion of a state-approved teacher preparation programme** (traditional, through a university, or an alternative route).
3. **A state teaching licence or certificate**, usually with a subject area and grade band.
4. **Subject knowledge tests** where the state requires them. Some states use a Praxis Computer Science test from ETS (https://www.ets.org/praxis); others use their own exams or none.
5. **Background checks** and sometimes student-teaching hours.

For computer science specifically, states take different approaches:

- some offer a **dedicated CS licence or certification**;
- some offer a **CS endorsement** added to an existing licence (for example mathematics or business);
- some allow CS to be taught under another licence area, sometimes with extra training;
- requirements may differ for middle school and high school.

The authoritative source is your **state department of education's educator certification office**. Search "<your state> department of education educator certification" and use the official .gov site. CSTA (https://csteachers.org) publishes advocacy and policy resources and has local chapters that can tell you how things work in your state.

**Alternative certification** routes let career changers with a bachelor's degree start teaching sooner, often on a provisional licence while completing a programme. Conditions, costs and timelines vary widely by state.

**Moving between states:** licences do not automatically transfer. Many states have reciprocity agreements (NASDTEC, https://www.nasdtec.net, coordinates the interstate agreement), but you may still need extra tests or courses.

## Private, charter and other schools

Private schools often do not require a state licence, and some charter schools have more flexibility; many still prefer or require one. Read job postings in your area to see what employers actually ask for.

## Teaching at college or university

O*NET classifies postsecondary computer science teachers (25-1021.00) in Job Zone 5: extensive preparation.

- **Community colleges** usually require at least a **master's degree** in computer science or a closely related field (often with a minimum number of graduate CS credits).
- **Universities:** tenure-track faculty generally need a **PhD**. Teaching-focused roles (lecturer, teaching professor) may accept a master's with strong teaching experience at some institutions.
- No teaching licence is required, but teaching experience (graduate teaching assistant work, adjunct roles) matters a lot.

## Outside the US

Most countries have a national or regional teacher registration system; for example, in England teachers in state schools typically hold Qualified Teacher Status, and many countries require a teaching qualification plus a subject degree. Check the official education ministry or teacher registration body for your country.

## Informal and adjacent routes

Not every CS teaching job needs a licence: bootcamps, after-school clubs, libraries, online tutoring, corporate training and nonprofits all hire CS educators. These can be good ways to gain experience while you work toward certification. The technical trainer path on this platform overlaps here.

## Worked example: a career changer's plan

Sam has a bachelor's in business and works as a data analyst. Goal: teach high-school CS in their state.

1. Official state site shows a CS endorsement exists; a full licence is needed first.
2. State offers an alternative route for degree holders: one-year programme, provisional licence while teaching.
3. A subject test is required for the endorsement.
4. Plan: apply to the alternative route programme, take the subject test, join the local CSTA chapter, and volunteer at an after-school coding club to gain classroom experience.

Every step has an official link and a "checked on" date in Sam's plan.

## Common mistakes

- **Relying on forums or old articles.** Use the official state or national site.
- **Assuming one state's rules apply elsewhere.**
- **Ignoring experience.** Schools value classroom experience; start volunteering or tutoring early.
- **Forgetting renewal.** Most licences need professional development hours to renew.

## Quick recap

- US public K-12: bachelor's degree, teacher preparation, a state licence, and often a CS licence or endorsement; rules vary by state.
- College teaching: usually a master's (community college) or a PhD (university faculty).
- Use official sources (state education departments, CSTA, ETS, NASDTEC, AP Central) and record the date checked.
- Informal teaching roles can build experience while you qualify.

## Try it

Open the Do tab and map your own certification route using official sources.


Map the degree and certification routes to teaching computer science in K-12 or college in your state or country.

Teaching licensure and degrees

Become A Computer Science Teacher

CS Teacher Certification Showcase + Teacher Panel

Build an inclusive CS classroom, set up a class on a free platform, and map the degree and certification routes for where you want to teach.