PGT Computer Science interview questions and answers (2026)
PGT Computer Science interview prep for CBSE and ICSE schools — real panel questions with model answers, and a Class 12 Python demo lesson plan.
What this interview actually looks like
An honest breakdown of how Indian schools run this interview — not a generic template.
- 1Written test (30–45 min) — 3–4 Python problems (one file-handling, one SQL, one data-structure).
- 2Demo lesson (15–20 min) — Class 11 (functions / lists) or Class 12 (SQL / stack). Topic often given the same day.
- 3Subject panel (20–30 min) — HOD CS + one senior teacher. Expect one live-code question.
- 4Principal / HR round (15 min) — school fit, salary, joining date.
- Two printed CVs + one Class 12 lesson plan
- Original degree (MCA / M.Tech / M.Sc CS), B.Ed, CTET where applicable
- A USB with 2–3 working Python + SQL demos in case they ask for one
- One printed problem you can code on the board in 3 minutes
Questions with model answers
Grouped by round. Each answer is 2–4 sentences — long enough to be real, short enough to remember. Dots show how often each is asked.
What they're really asking — Can you write correct code on a whiteboard while explaining?
def is_palindrome(s): s = s.lower(); return s == s[::-1]. Then talk it through: lowercase to make it case-insensitive, slice with step -1 to reverse, compare. Mention edge cases you're skipping — non-alphanumeric characters, unicode — and how you'd handle them if needed. Board panels test whether you code without autocomplete, not whether you produce the cleverest solution.
What they're really asking — Can you compress a Class 11 concept clearly?
Both are ordered sequences. List is mutable — you can append, remove, modify. Tuple is immutable — once created, no changes. Use a tuple when the data shouldn't change (coordinates, RGB colours, database row); use a list when it will (a shopping cart). Tuples are also slightly faster and can be dictionary keys; lists can't. Give one example of each on the board.
A 15-minute demo you can teach on Monday
Panels don't score creativity — they score structure, board work and closure. This is the skeleton that works.
- Class 12 — SQL joins with a two-table example
- Class 12 — File handling: writing a log to disk
- Class 11 — Functions with default arguments
- Class 11 — Lists vs tuples with a small program
- Live coding without autocomplete
- Explaining while writing
- Realistic error handling shown, not skipped
- Cold-calling students
- Clean board layout — indentation matters
State a real problem — 'we need to log every failed login attempt to a file' — before naming the topic.
Explain the syntax on the board with a minimal example.
Type or write out a working example. Predict output before running.
Give a variation. Circulate; help those who freeze.
Cold-call two students. Close with one board-exam-style question.
Ask them back — questions for the interviewer
Most candidates freeze at “do you have any questions for us?” These signal that you take yourself seriously.
- How many periods per week does a PGT CS teacher get, and how many lab batches?
- What's the ratio of students per lab machine — 1:1, 2:1, or worse?
- Do you have a school-wide policy on AI-assisted coding by students?
- What's the CPD budget for CS workshops (CSTA India, Google Educator, etc.)?
- How do you handle students who need extra lab time — is it institutionalised or informal?
- What's the appraisal cycle — board results, project quality, or feedback?
Ready to apply?
PGT Computer Science openings across Indian schools, updated daily.
See open PGT Computer Science jobs