Curriculum Developer interview questions and practice.
Designs and updates curricula, learning materials and assessments for schools, colleges or training providers.
No card for the taster. Full interviews are paid one at a time. Nothing renews.
Last reviewed
This page is still being written: no authored question bank for this competency family. The role is fully supported in the interview itself; only the published question bank is outstanding.
What interviewers for Curriculum Developer actually ask
The question bank for this role is still being written. These are the first three competencies in the model the interview is scored against.
Maintains accurate student records, registrations, marks and graduation checks, and catches errors before they affect a student's progression or funding.
Applies admission, progression, exclusion, appeal and concession rules consistently, explains them to students and staff, and identifies genuine exceptions for escalation.
Handles queues, distressed and angry students calmly, resolves what they can, and escalates or refers (funding, wellness, academic advisors) at the right point.
What they are really assessing
Interviewers rarely score whether you seemed nice. They score against a model like this one, usually without telling you it exists. Each competency has a weak, adequate and strong shape, and the difference is almost always the level of specific detail you volunteer without being asked.
Student records & registration accuracy
Maintains accurate student records, registrations, marks and graduation checks, and catches errors before they affect a student's progression or funding.
- Weak
- Describes records as data entry; cannot describe a check they use or an error they caught or caused.
- Adequate
- Describes checks (reconciliations, verification against source) and an error caught, but not a process change to prevent recurrence.
- Strong
- Describes a specific error that affected students (wrong marks, missed registration, graduation block), how it was found, how they owned and fixed it, and the check introduced.
Applying academic rules & policies
Applies admission, progression, exclusion, appeal and concession rules consistently, explains them to students and staff, and identifies genuine exceptions for escalation.
- Weak
- Applies rules mechanically or bends them for whoever complains loudest; cannot describe an exception case and how it was decided.
- Adequate
- Explains key rules and describes a hard case escalated, but not how they distinguished a genuine exception from a routine complaint.
- Strong
- Describes a specific case (late registration, exclusion appeal, concession): the rule, the student's circumstances, what they recommended and why, who decided, and how consistency was protected.
Student-facing service & escalation
Handles queues, distressed and angry students calmly, resolves what they can, and escalates or refers (funding, wellness, academic advisors) at the right point.
- Weak
- Describes students as demanding; cannot describe de-escalating a situation or a referral made.
- Adequate
- Describes calming a distressed student and resolving an issue, but not recognising a wellbeing or funding risk or following it up.
- Strong
- Describes a specific situation (registration crisis, funding failure, distress): what they said, what they resolved, the referral made, and the follow-up.
Timetabling, examinations & logistics
Plans timetables, examinations and venues to avoid clashes and breaches of exam rules, and manages the exam period under pressure.
- Weak
- Describes timetabling as 'using the system'; cannot describe a clash or exam incident and how it was handled.
- Adequate
- Describes the planning process and an exam incident handled, but not a change made to prevent it.
- Strong
- Describes a specific clash or exam incident (venue failure, paper leak, invigilator absence), the immediate response, the communication, and the process fix.
Reporting & compliance data
Produces accurate reports for internal management and regulators (e.g. HEMIS or DHET returns, accreditation evidence) and reconciles discrepancies.
- Weak
- Cannot name a report they own or describe a data discrepancy resolved.
- Adequate
- Describes reports produced and a discrepancy fixed, but not the root cause or the impact on funding or accreditation.
- Strong
- Describes a specific reporting cycle: the reconciliations done, a discrepancy found, its root cause and impact, and how they fixed the upstream process.
Confidentiality & POPIA
Protects student personal information under POPIA, verifies identity before releasing information, and handles requests from parents, employers and sponsors correctly.
- Weak
- Would give a parent a student's results on request; cannot describe POPIA obligations or a breach.
- Adequate
- Knows verification and consent rules and describes a request declined, but not a breach or near-miss handled.
- Strong
- Describes a specific request or breach (parent, sponsor, email to wrong recipient): the rule applied, how they handled and reported it, and the process change.
Cross-department coordination
Works across faculties, finance, IT, residences and student services to solve student problems that cross boundaries, and follows through until resolved.
- Weak
- Refers students elsewhere and considers the job done; cannot describe a cross-department problem they resolved.
- Adequate
- Describes coordinating with another department to solve a problem, but not one where the other department was unresponsive.
- Strong
- Describes a specific case stuck between departments, how they took ownership, who they engaged and how, and the resolution and process change.
Reading the questions is the easy half. Try answering three of them out loud, to someone who follows up.
Try 5 minutes freeWhat your 30 minutes covers
The same shape as a real first-round interview, pitched at mid-level Curriculum Developer and scored throughout.
Warm-up, then Motivation & fit
Build rapport, settle nerves, and get a short walk-through of your background. Why this role, why this employer, and what you are actually looking for.
Your experience
Two or three real situations from your CV in depth: context, what you did, what happened, what you would change.
Pitched at mid-level scope: faculty administrator or senior officer: runs the academic administration cycle for a faculty or school, supervises assistants, owns reports.
Role-specific questions
The core competencies and domain knowledge for the role, with follow-ups on anything vague.
Drawn from this role's domain: admissions, registration and late registration rules, student records systems and marks capture and progression, exclusion and appeals policies, and the rest of the competency model.
Your questions, then Wrap-up
Your questions for the interviewer, and yes, they are assessed. Next steps and a clean finish.
What changes with seniority
The questions barely change between levels. What changes is the answer they will accept.
| Junior | Mid | Senior | |
|---|---|---|---|
| Scope of ownership | Administrative assistant or faculty officer: owns a set of processes (registrations, marks capture, exams admin) for a department or programme. | Faculty administrator or senior officer: runs the academic administration cycle for a faculty or school, supervises assistants, owns reports. | Faculty manager or senior administrative officer: accountable for a faculty's administration, compliance reporting, systems and service standards. |
| Tolerance for ambiguity | Handles routine exceptions using policy; escalates appeals, breaches and unusual cases. | Interprets policy for edge cases; decides on escalations and process changes. | Decides on responses to appeals, audits and system failures; balances service with compliance. |
| People leadership | May train student assistants. | Supervises and rosters a small team; handles first-line performance issues. | Line-manages administrators; appraises and develops staff. |
| Who they deal with | Faculty administrator, lecturers, students, finance and IT. | Dean's office, HODs, registrar's office, student services. | Dean, registrar, auditors, DHET or CHE contacts, IT. |
What your report would say
Every competency above scored from your own answers, the sentence that cost you quoted back, and your weakest answers rewritten the way a strong Curriculum Developer would have said them.
- Describes a specific situation (registration crisis, funding failure, distress): what they said, what they resolved, the referral made, and the follow-up.
The format, not a result. Scores on your report come from what you actually said.
Is the AI interviewer realistic? See a full sample report