What are computer science students saying about their teaching staff?

Published May 10, 2024 · Updated Mar 02, 2026

teaching staffcomputer science

Computer science students tend to rate their lecturers positively, but their comments quickly turn when assessment expectations are unclear or delivery is inconsistent. In the National Student Survey (NSS), the UK‑wide survey of final‑year undergraduates (see our open-text NSS comment analysis methodology for details), Teaching Staff comments are predominantly favourable (78.3% Positive), yet Computing sits lower on the sentiment index (+44.6) and Computer Science is closer to even (50.1% Positive).

In Computer Science, feedback scores poorly (−27.8), a pattern explored in our analysis of feedback challenges in computer science education, while predictable access to staff remains a strength (+30.1). These patterns frame the analysis below of how students experience expertise, communication, availability, pedagogy, enthusiasm, and feedback in computer science programmes.

Why does technical expertise matter in computer science teaching?

Students value lecturers who combine strong theoretical grounding with recent, applied experience. They respond when staff connect algorithms, architectures, and tooling to authentic workflows and contemporary practice. In technical subjects where sentiment trends lower than the category baseline, lecturers lift understanding by demonstrating worked examples, explaining trade‑offs, and aligning assessment briefs with the skills industry expects. Providers should prioritise continuous professional development to keep curricula and lab practice current, and enable staff to iterate modules in response to cohort feedback. This helps students connect theory to assessed work and build confidence in labs and projects.

How should lecturers communicate complex concepts?

Students engage when lecturers scaffold explanations and signpost what good work looks like. They report stronger learning when staff break down problems, use multiple representations, and check understanding at natural pause points. In Computing, a sharper focus on explicit assessment criteria, exemplars, and a consistent session structure improves perceptions of delivery and reduces avoidable confusion, especially when teams address the communication barriers in computer science education that students describe. Institutions can provide practical training on explanation strategies and encourage teaching teams to align on shared marking criteria and language across modules. That consistency makes it easier for students to understand what good work looks like, regardless of who teaches a session.

How available and supportive are lecturers?

Predictable access to teaching staff is consistently valued by computer science students. They want timely responses, clear office hours, and drop‑ins that line up with deadlines. Programmes should set simple, visible service standards, support part‑time and commuter cohorts through flexible contact options and asynchronous Q&A, and ensure personal tutor systems are easy to navigate. Brief pulse surveys after major teaching moments help teams close the loop and keep support consistent across a large teaching workforce.

Which teaching methods work best in computer science?

Students favour interactive labs, project‑based tasks and code‑along demonstrations that let them apply concepts immediately. Structured session signposting, short problem‑solving sprints, and peer review help students translate theory into practice. Where lecture‑only delivery feels abstract, blending it with hands‑on activities and regular formative checkpoints improves momentum and confidence. It also gives teaching teams earlier signals when a cohort needs support.

Does staff enthusiasm improve learning?

Enthusiasm from lecturers lifts participation and helps students see the relevance of their studies. When staff share current projects and explain why a method or pattern matters, it accelerates understanding, raises ambition, and helps students persist through challenging material. Teams sustain this energy by coordinating guest inputs, showcasing student work, and making links to personal development and career pathways visible within modules.

How should coursework and feedback be handled?

Assessment and feedback represent the most actionable improvement area for Computer Science. Students ask for marking criteria they can trust, annotated exemplars, and feed‑forward that shows exactly how to progress next time. Consistent turnaround times, structured feedback aligned to published criteria, and a single source of truth for any changes to assessment briefs reduce noise and help students use feedback effectively. For programme teams, this is often a high‑leverage place to start.

What do students want improved, and what already works?

Students praise approachable staff and appreciate when teaching connects to real‑world practice. They ask for more interactive sessions, consistent communications about changes, and assessment expectations that are unambiguous across modules. Programmes that stabilise delivery rhythms, maintain predictable access to teaching teams, and make marking criteria explicit see satisfaction rise without compromising academic standards.

How Student Voice Analytics helps you

If you want to spot these themes early and evidence the impact of changes, Student Voice Analytics helps you:

• Track Teaching Staff comments and sentiment over time, with drill‑downs from provider to subject family and cohort within Computer Science.
• Compare like‑for‑like by subject group and student demographics, and segment by mode, site, and year of study to find where change matters most.
• Produce concise, anonymised summaries for programme and departmental briefings, with export‑ready tables for quality boards.
• Evidence progress with comparable benchmarks, so teams can show how assessment clarity, delivery rhythm, and access standards improve over time.

Request a walkthrough

Book a free Student Voice Analytics demo

See all-comment coverage, sector benchmarks, and reporting designed for OfS quality and NSS requirements.

• All-comment coverage with HE-tuned taxonomy and sentiment.
• Versioned outputs with TEF-ready reporting.
• Benchmarks and BI-ready exports for boards and Senate.

Book a free demo Prefer email? info@studentvoice.ai

UK-hosted · No public LLM APIs · Same-day turnaround

Related Entries

• What do computer science students need from feedback?
• Do computer science students trust marking criteria?
• Can fixing course communications lift computer science learning?
• NSS open-text analysis methodology for UK HE