Keshinie Sajeevan

My lessons are structured but flexible. I always start by figuring out where a student currently stands, then build a plan around their specific gaps rather than following a generic syllabus from the top. For A-Level Computer Science, that usually means working through core topics (programming fundamentals, data structures, computer systems, networking) with a mix of clear explanation, worked examples, and hands-on coding practice, since I think you learn Computer Science best by actually writing and debugging code, not just reading about it.

Closer to exams, I shift focus onto exam-style questions and mark scheme language. a lot of students lose marks not because they don't understand the concept, but because they don't know how to phrase the answer the way examiners want. I work through past papers with students, break down what a "good" answer looks like, and build that technique alongside the subject knowledge.

Lessons are conversational rather than me just talking at a screen. I ask questions throughout to check understanding as we go, rather than waiting until the end to find out something didn't land. If a concept isn't clicking, I'll explain it a different way rather than repeating the same explanation louder.

My background: I'm currently completed an MSc in Cyber Security at the University of Birmingham, with a BSc (Hons) in Computer Science. I've tutored Mathematics and basic Computer classes previously, and I've also run a cryptography workshop for 30+ secondary school students, so I'm comfortable teaching across different ages and levels. I've built real software projects myself (including a full-stack web application as my final year project), so when I teach programming, it comes from genuine hands-on experience rather than just theory.

My goal in every lesson is the same: leave the student more confident than when we started, with a clearer sense of what they actually know versus what still needs work.