Interview Preparation

Total marks should reflect the GLH and the breadth of content. A 60-GLH qualification might warrant 60 marks (roughly 1 mark per GLH). Each criterion gets marks proportional to its relative importance within the unit. The total must also be practical — enough to differentiate learners but not so many that the assessment becomes unwieldy. I validate through the blueprint: do the marks sum correctly, does the weighting match the specification AO targets, and can learners complete it in the allocated time.

Norm-referenced assessment ranks learners against a cohort (e.g., top 10% get A). It is used for selection where relative performance matters. Criterion-referenced assessment measures against a defined standard (e.g., pass = 60%). It is used in competency-based qualifications where absolute competence matters. Most vocational and professional qualifications are criterion-referenced because we need to know the learner can do the job, not just that they are better than peers.

This is a serious regulatory issue. Step 1: Immediately notify the Chief Examiner and compliance/regulatory team. Step 2: Assess the scope — how many learners are affected? Which criterion? Step 3: Determine if special consideration can compensate. Step 4: If the criterion is mandatory and cannot be compensated, a resit opportunity must be arranged. Step 5: Document everything — regulators will need a full account of what happened, why, and what was done. Step 6: Review processes to prevent recurrence.

A validity argument has multiple lines of evidence. 1) Content evidence: the blueprint mapped to specification, confirmed by SME review. 2) Construct evidence: construct definitions showing what is measured, construct maps linking items to constructs. 3) Criterion evidence: if the qualification leads to employment, correlation with workplace performance. 4) Consequential evidence: analysis of results showing fair outcomes across groups. I would compile these into a validity report, documenting both strengths and limitations.

I would start with data: compare mark distributions, mean marks, and standard deviations across the two series. Check inter-rater reliability statistics if available. Then investigate causes: were new examiners introduced without adequate standardisation? Was the mark scheme changed? Were there different exemplar materials? I would sample scripts from both series and have them blind-marked by the same senior examiner to isolate whether the difference is in learner performance or marking behavior. Findings would guide corrective action — additional standardisation, revised mark scheme guidance, or examiner feedback.

For dyslexia, I focus on removing literacy barriers that are not part of the construct. 1) Use clear, sans-serif fonts at minimum 12pt. 2) Keep sentences short (under 25 words). 3) Avoid unnecessarily complex vocabulary. 4) Provide 25% extra time as standard. 5) Consider a reader or text-to-speech software. 6) Use modified papers with tinted backgrounds if requested. Critically, none of these adjustments change what is being assessed — they remove barriers to demonstrating competence. The standard remains identical.

Leading questions push learners toward a particular answer. I avoid them by: 1) Not including the answer in the stem ("Data protection is important. Explain why" — the stem already tells the learner it is important). 2) Using neutral framing: "To what extent is data protection important in administration?" 3) Avoiding emotional language ("the crucial principle", "the obvious choice"). 4) Not embedding evaluative terms in the question. 5) Having a peer review specifically looking for leading language. A good test: can a competent learner arrive at a different, equally valid conclusion from the same stem?

This happens regularly in extended responses and short answer. The mark scheme should include a general instruction: "Accept any other valid response." For point-based marking, if the answer is factually correct and addresses the criterion, award the mark. The examiner records the response so the mark scheme can be updated for future series. For levels-based marking, the overall quality of response determines the level, so specific wording matters less. The key principle: the mark scheme serves the assessment, not the other way round.

Consistency in practical observation requires: 1) A structured observation record with specific, observable criteria — not "did well" but "correctly positioned hands on keyboard throughout." 2) Standardisation sessions where all assessors watch the same video/performance and compare judgments. 3) Double-observation of a sample, especially for borderline candidates. 4) Ongoing moderation — the lead assessor observes each assessor observing a learner. 5) Regular calibration meetings. The goal is that two independent assessors observing the same performance would reach the same judgment.

First, check if the difference is statistically significant or within normal variation. If significant: 1) Compare the centre's results across multiple series — is this a one-off or a pattern? 2) Check if the centre's learner profile differs from the national cohort (prior attainment, demographics). 3) Review any malpractice or special consideration data. 4) If no obvious explanation, consider an investigation visit — are they delivering the qualification correctly? Are internal assessments being marked accurately? 5) Do not jump to conclusions — lower results could indicate honest issues with teaching, not malpractice.

I would collect: 1) Item-level: facility index, discrimination index, distractor analysis (for MCQs), and item response time data. 2) Marker-level: inter-rater reliability, marker consistency, common errors noted. 3) Centre-level: feedback forms, queries raised during marking, special consideration requests. 4) Cohort-level: grade distributions, pass rates, comparisons with previous series. 5) Qualitative: examiner reports, Chief Examiner commentary. This data feeds into a post-series review meeting where improvement actions are agreed and tracked to the next development cycle.

From my background, I bring: 1) Attention to detail — I am used to checking work against defined standards, which directly transfers to specification mapping and technical review. 2) Systematic working — I follow processes and document decisions, essential for version control and audit trails. 3) Subject expertise applied in real contexts — I understand what competence looks like in practice, not just in theory. 4) Quality assurance experience — I understand the importance of documented checks and sign-offs. 5) Communication skills — I can explain complex ideas clearly, which transfers to writing clear assessment items and briefing SMEs.

This is a behavioural question — use STAR. Situation: [Describe the project]. Task: [What was your responsibility? What were the constraints?]. Action: [How did you plan? How did you communicate? How did you handle risks? Give specific examples of your actions]. Result: [What was the outcome? Was it on time? Were stakeholders satisfied? What did you learn?]. The interviewer wants evidence you can handle multiple competing demands, communicate clearly, and deliver to deadline.

STAR response: Situation — during a routine check, I noticed [specific error]. Task — I needed to confirm it was genuinely an error and ensure it was corrected before [consequence]. Action — I verified the error independently, gathered evidence, and approached [the responsible person] privately and constructively with "I think there may be an issue here — could you check?" I focused on fixing the problem, not assigning blame. Result — the error was corrected before [impact]. The team appreciated the collaborative approach. I learned that raising issues early and constructively is always the right approach.

Situation: [Name the topic you had to learn and the timeline]. Task: I needed to reach a level where I could [apply the knowledge]. Action: I broke the topic into chunks, identified the best resources (official documentation, expert colleagues, structured courses), set a learning schedule, and applied the knowledge to a real task as quickly as possible to test my understanding. I was not afraid to ask questions. Result: Within [timeframe], I was able to [demonstrate competence]. I continue to build on that foundation.