Customer Service & Administration · Executive & Office Admin · 30-minute interview

Records Administrator interview questions and practice.

Maintains an organisation's records system, controlling how documents are stored, tracked, retained and disposed of. An interviewer hiring a Records Administrator is not testing whether you know what the job is. They are trying to establish whether things stop falling through the cracks once you are in the room, and whether you can be trusted with what you will inevitably overhear.

No card for the taster. Full interviews are paid one at a time. Nothing renews.

Last reviewed

7 scored competencies10 questions in the bank30-minute voice interviewScored in about a minute after the call

What interviewers for Records Administrator actually ask

Three questions from the bank below, each scored against one competency. The follow-up is what separates a prepared answer from a memorised one.

  1. Two people both need the same hour with your manager, and one of them is the CEO. What do you do?

    Scored against: Diary, travel & priority management
  2. Tell me about a trip or event you organised that did not go to plan.

    Scored against: Diary, travel & priority management
  3. What is something you started doing that nobody asked you to do?

    Scored against: Initiative, follow-through & working ahead

What they are really assessing

That gets scored against 7 competencies: diary, travel & priority management, accuracy, documents & record-keeping, discretion, confidentiality & judgement, gatekeeping & stakeholder handling, office operations, suppliers & processes, initiative, follow-through & working ahead and office tools & technology proficiency. Each one is assessed from the specifics in your answers, which is why "we improved the process" scores lower than a sentence with a number, a date and a decision in it.

At mid level they assume you can do the job and are testing how you handle the parts that go wrong. Expect them to push hardest on prioritisation and gatekeeping examples, confidentiality judgement and process improvements made.

Diary, travel & priority management

Runs calendars, travel and logistics for one or more principals, anticipates clashes and needs, and reprioritises calmly when plans change at short notice.

Weak
Describes diary management as 'booking meetings'; cannot give an example of a clash resolved, a trip rearranged, or how they decide what gets priority.
Adequate
Describes managing a busy diary or trip and one disruption handled, but is vague on how they anticipated needs or what rules they used to prioritise.
Strong
Recounts a specific week or trip: the competing demands, how they protected the principal's priorities, a last-minute change (cancelled flight, urgent meeting) and how it was solved, and how the principal's time was measurably better used.

Accuracy, documents & record-keeping

Produces correct documents, minutes, spreadsheets and filings, checks their own work, and keeps records that others can find and rely on.

Weak
Claims attention to detail without describing a checking method, a document type they own, or an error they caught or made.
Adequate
Describes documents and records they maintain and a checking habit, but has no example of an error caught or a filing system improved.
Strong
Describes a specific document or process (board pack, minutes, expense reconciliation), the checks applied, an error caught before it went out, and a filing or tracking improvement with its effect.

Discretion, confidentiality & judgement

Handles sensitive information (HR, financial, strategic) appropriately, knows what can be shared with whom, and exercises judgement when asked to act on the principal's behalf.

Weak
Says they are 'trustworthy' with no example of handling sensitive information or being pressed to share something.
Adequate
Describes handling confidential information and a rule they follow, but no example of a judgement call or pressure resisted.
Strong
Describes a specific situation: the sensitive information, who wanted it or what decision was needed, how they handled it and why, and how the principal's trust was reinforced.

Gatekeeping & stakeholder handling

Manages access to the principal, handles senior internal and external contacts with tact, and represents the office professionally in writing and in person.

Weak
Cannot describe a specific difficult request for the principal's time, a demanding stakeholder, or how they said no politely.
Adequate
Describes managing requests and difficult callers, but is vague on how they judged what to escalate or how relationships were protected.
Strong
Recounts a specific case: the request or person, how they assessed priority, what they said and wrote, how the principal was briefed, and the outcome for the relationship.

Office operations, suppliers & processes

Keeps the office running: procurement, suppliers, facilities, onboarding logistics, expense and invoice processing, and improves the processes they own.

Weak
Lists tasks with no example of a supplier problem solved, a budget managed, or a process they improved.
Adequate
Describes office processes they run and one problem solved, but is vague on cost, service levels or the improvement's effect.
Strong
Describes a specific process (procurement, travel, expenses), a supplier or cost problem and how it was resolved, and an improvement with measured time or cost saved.

Initiative, follow-through & working ahead

Sees what needs doing before being asked, closes loops on actions, chases others politely but persistently, and does not let tasks fall through the cracks.

Weak
Describes waiting for instructions; no example of anticipating a need or chasing a senior person for an overdue action.
Adequate
Gives an example of initiative but is vague on how they track actions or handle non-responsive stakeholders.
Strong
Describes a tracking method, a specific need anticipated and handled before it was raised, and a case of chasing a senior person for a deliverable with the result.

Office tools & technology proficiency

Uses Microsoft 365 or Google Workspace, expense and travel systems, and collaboration tools competently, and learns new systems quickly.

Weak
Lists software but cannot describe a specific task done in it beyond basics, or a system they learned recently.
Adequate
Describes competent use of core tools but no example of solving a problem with a formula, template, automation or new tool.
Strong
Describes a specific use: a spreadsheet or template built, a mail merge, a workflow automated or a system adopted, and the time saved or error reduced.

10 questions you should expect

What a strong answer contains, not a model answer to memorise. A memorised answer falls apart on the first follow-up, and there is always a follow-up.

  1. Two people both need the same hour with your manager, and one of them is the CEO. What do you do?

    Scored against: Diary, travel & priority management

    A strong answer contains: A decision made rather than escalated: what you ask each side, what you move, what you offer instead, and when you would go back to your manager. The strong version includes protecting thinking time and travel time as real appointments.

  2. Tell me about a trip or event you organised that did not go to plan.

    Scored against: Diary, travel & priority management

    A strong answer contains: What broke (a cancelled flight, a venue falling through, a visa), what you did in the moment, who you told, and what you now build into every itinerary because of it.

  3. What is something you started doing that nobody asked you to do?

    Scored against: Initiative, follow-through & working ahead

    A strong answer contains: A specific process, template, tracker or routine, why it was needed, whether anyone else uses it now, and what it saved. This question separates people who do the job from people who improve it.

  4. How do you make sure nothing you have chased gets forgotten?

    Scored against: Initiative, follow-through & working ahead

    A strong answer contains: An actual system named and described, not "I'm very organised". Where the list lives, when it is reviewed, how a chase is escalated, and what happens to it when they are on leave.

  5. You see something confidential: a restructure document, a salary, a resignation. What do you do?

    Scored against: Discretion, confidentiality & judgement

    A strong answer contains: Nothing said to anyone, including the person it concerns and including "harmless" colleagues, plus a specific example of having sat on something. Strong answers also cover the practical side: screen position, printer, locked files, who else has access.

  6. Someone senior is angry that they cannot get to your manager. How do you handle it?

    Scored against: Gatekeeping & stakeholder handling

    A strong answer contains: Absorbing the frustration without either caving or stonewalling: acknowledging, finding out what they actually need, offering a real alternative, and telling the manager afterwards rather than hiding it.

  7. Tell me about a mistake in something you produced that went out.

    Scored against: Accuracy, documents & record-keeping

    A strong answer contains: The actual error, how it was found, what they did in the next ten minutes, and the specific check added since: a read-back, a second pair of eyes on anything external, a template.

  8. How do you proofread your own work when you have already read it four times?

    Scored against: Accuracy, documents & record-keeping

    A strong answer contains: A real technique: reading backwards, reading aloud, leaving it and returning, checking numbers and names separately from prose. Vague claims of being "detail-oriented" score nothing here.

  9. Tell me about a supplier or office process you took over and changed.

    Scored against: Office operations, suppliers & processes

    A strong answer contains: What was wrong, what you compared, what you negotiated or restructured, and the saving in money or time. Includes who had to agree.

  10. What is the most useful thing you can do in Excel, or in whatever tool you live in?

    Scored against: Office tools & technology proficiency

    A strong answer contains: One capability described concretely (a lookup across two data sets, a pivot for a monthly report, a mail merge, an automated form-to-tracker flow) and what it replaced. Honest ranking of depth beats a list of software names.

Reading the questions is the easy half. Try answering three of them out loud, to someone who follows up.

Try 5 minutes free

What your 30 minutes covers

The same shape as a real first-round interview, pitched at mid-level Records Administrator and scored throughout.

0 to 7 min

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.

7 to 16 min

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: pA or senior administrator: owns support for a senior manager or department including complex travel, meetings, minutes and budget tracking.

16 to 25 min

Role-specific questions

The core competencies and domain knowledge for the role, with follow-ups on anything vague.

Drawn from this role's domain: complex diary management across time zones and executives, travel booking, visas, itineraries and disruptions and minute-taking, action tracking and meeting preparation, and the rest of the competency model.

25 to 30 min

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.

 JuniorMidSenior
Scope of ownershipAdministrator or junior PA: owns routine administration for a team or manager - diaries, documents, expenses, travel bookings.PA or senior administrator: owns support for a senior manager or department including complex travel, meetings, minutes and budget tracking.Executive assistant or office manager: owns an executive's office or the whole office operation; represents the executive to senior stakeholders.
Tolerance for ambiguityHandles standard requests; escalates conflicting priorities and sensitive matters.Prioritises competing demands independently; makes judgement calls on the principal's behalf within understood boundaries.Anticipates and acts without instruction on most matters; handles crises (travel, board logistics) calmly.
People leadershipNo formal leadership.May guide junior administrators or reception.Leads administrators or office staff; coordinates other EAs.
Who they deal withManager or team, other administrators, suppliers, visitors.Senior managers, executives' offices, clients, suppliers.Executives, board members, key clients, suppliers, HR and finance.

Where candidates lose this interview

  • "I'm very organised" with nothing behind it

    Every candidate for every administrative role says this, which is exactly why it scores zero. What is scored is the system: where the list lives, when you review it, what happens to your open items when you are on leave. Describe the mechanism, not the trait.

  • Escalating decisions you were hired to make

    The whole point of the role is to remove decisions from someone else's day. A candidate who takes every diary clash back to their manager is describing more work, not less. Show where your judgement stops and theirs starts.

  • Discretion answers that give something away

    Candidates asked about confidentiality sometimes prove the point by immediately telling you what they know about their current employer's restructure. The correct answer demonstrates discretion in the telling, not just in the content.

  • Software listed, never demonstrated

    A CV listing eleven tools invites one question: what can you actually do in the main one? Pick two or three, describe a specific thing you built or automated in them, and be straight about the rest.

  • No example of working ahead

    The difference between an adequate and a strong administrator is anticipation: the document prepared before it was asked for, the clash spotted a week out. If every example is reactive, the interviewer scores you as reactive.

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 Records Administrator would have said them.

Sample report · Records Administrator
Mid-level · Mixed · 30:00
64of 100
Competencies, scored
Diary, travel & priority management4/5
Accuracy, documents & record-keeping3/5
Discretion, confidentiality & judgement2/5
Gatekeeping & stakeholder handling3/5
Office operations, suppliers & processes4/5
What a strong answer to question 1 needed

Two people both need the same hour with your manager, and one of them is the CEO. What do you do?

  • A decision made rather than escalated: what you ask each side, what you move, what you offer instead, and when you would go back to your manager. The strong version includes protecting thinking time and travel time as real appointments

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

Related roles

FAQ

Records Administrator interview questions, answered.

Often: a typing or accuracy test, a short document to format, a diary-clash exercise, or an inbox triage scenario. Speed matters less than whether you catch the error deliberately planted in it.

Describe the working pattern rather than the personality: how you learned their preferences, what you agreed about interruptions, and what you changed. Criticising a named current manager is one of the fastest ways to lose the room.

Say so, and describe how you would triage competing requests. Interviewers are far more worried about candidates who do not notice the difference than about the gap itself.

Nearly always for executive support roles, because you will see restructure plans, salaries and resignations before anyone else. Have one example of holding something you could easily have shared.

Yes, if it can be anonymised: a template you built, a tracker, an itinerary structure. Concrete artefacts are unusual in administrative interviews and land hard.

Fail this interview here, not there.

Thirty minutes with a demanding Records Administrator interviewer now is the cheapest way to find out what you would have got wrong later.