Administrative Assistant Interview Questions and Answers (2026)

Find out what each task needs and by when, and what happens if it slips. Do the one with the firmest deadline and biggest impact first. Tell all three managers what I am doing and when theirs will be done. If they clash, ask them to agree priority between themselves.

At four, three managers each told me their task was urgent. I did not start the nearest one. I asked each a quick question: what is it for and what happens if it is late? The first needed a contract pack for a client call at six, the second wanted a room booked for next week, and the third wanted a spreadsheet tidied for tomorrow's meeting. The contract pack had the hardest deadline and the clearest consequence, so I started on it. I messaged the other two: 'I'm finishing the contract pack for the six o'clock call. I'll book the room by five and send the spreadsheet by nine tomorrow morning. Is that okay?' The second manager was fine. The third said it was urgent for her, so I asked whether her meeting began before ten, and when she said it was at eleven, she accepted nine. Had two deadlines truly clashed, I would have asked the managers to decide priority together. I finished all three. Being open with everyone was easier than silently picking.

Write the process step by step in plain words, with screenshots and the files it uses, and who to ask for each decision. Then ask a colleague to run through it with me before I go, fixing anything unclear. A guide is not finished until someone else has followed it.

I was the only person who knew the monthly invoicing run, and I was going on leave for two weeks. Three days before I left, I wrote down every step, with screenshots of each screen, the names of the files, the order of the checks, the deadline for each stage and the three problems that came up most often, with what to do. I added who to ask about queries, and where the finished invoices go. I then asked a colleague to run the process on a dummy batch while I watched and said nothing. She got stuck on step six, because I had assumed she knew where to find the supplier code list. I added that to the guide. The following month I came back to find the run had been completed on time, and she had added two notes of her own. I keep the guide in the shared drive so that it is part of the team's knowledge and not mine. A handover is checked by watching someone else use it.

Tell my manager straight away, before anyone else finds it. Say what was wrong, which report went out, who has it and what the right figure is. Offer a correction to send, and then work out why it happened and add a check so it does not again.

Looking back through last week's data entry, I saw that I had typed a customer count of 1,240 as 2,140. The figure was already in a report that had gone to the board. I felt sick, but I did not wait. I checked the source, confirmed the right number, and went straight to my manager. I said, 'I made a mistake in last week's report. The count should be 1,240, not 2,140. I've drafted a correction email with the right figure and a line explaining the error. Would you like to send it, or shall I?' She sent it that day with a short apology. Then I looked at why it happened: I had keyed the figure by hand from a printout. I changed the process to copy the number from the system, and added a second person's check for any figure that goes in a board report. The accuracy principle in data protection law expects that inaccurate personal data is corrected without delay, and the same attitude applies to any figure. Owning the error fast mattered more than the error.

Do not pay until the difference is explained. Apply the same checks as for any invoice: match to the purchase order and delivery. Raise the 12% with the supplier and my finance lead, and tell the director why. Friendship with a supplier is not a reason to skip the process.

An invoice came in at £5,600 against a purchase order for £5,000. My director said, 'He's a friend of mine, just pay it.' I said, 'I'm happy to pay as soon as I can match it. It's twelve per cent over the order, and finance will ask me why, so can we find out what the extra is for?' I checked the delivery note, which matched the order, and phoned the supplier's accounts team for a breakdown. It was a delivery surcharge that had not been agreed. I sent the breakdown to my director and my finance lead, and asked whether the surcharge was approved. She said it was not. The supplier issued a corrected invoice for £5,000. I did not accuse anyone of anything. I applied the same check I apply to every invoice, because the checks protect everyone, including the director. The invoice was paid within terms.

Treat it as time-critical, because the organisation has one month to respond. Search every system and folder where the person's data could be, with HR's list of names and terms, log what I searched, and pass everything to the person responsible. I would not edit, delete or decide what is disclosed.

HR told me a former employee had made a subject access request and asked me to find his records. The organisation has a month to respond, so I asked for the date we received it and put the deadline in my diary. With HR I made a list of where his data could be: the HR system, payroll, my own email folders, shared drives, the helpdesk and any paper files. I searched using his full name, employee number and common spellings, and kept a log of each place and term. I did not delete or move anything, and I did not read more than I needed to find relevant items. I gave HR everything I found, with the log, and they decided what to disclose and what was exempt. I flagged that some emails mentioned other people, as HR would need to consider them. A good log shows that the search was reasonable. We responded within the month.

Report it immediately to my manager and the data protection lead. Try to recall the email, ask IT to remove it from inboxes, and tell recipients not to open or forward it. Write down exactly what was sent and when. A breach may have to be reported to the ICO within 72 hours, so speed matters.

I attached the wrong spreadsheet to a company-wide email, and it contained names, salaries and bank details. I realised within a minute. I did not delete it and hope. I rang my manager, who is also the data protection lead, and said exactly what had happened: the file, the time and the number of recipients. She asked IT to remove the message from all inboxes, which they could do within minutes, and I sent a short message asking people to delete it unread and not to forward it. I wrote a note of what was attached, who it went to and what we did. The data protection lead decided that it needed to be reported, and she told the ICO within the 72 hours and informed the affected staff. I also took part in the review. We changed the process so payroll files are password protected and sent from a restricted mailbox. I now check the file name and the recipients before I press send, every time.

Check the retention policy first, so I keep what must be kept and for how long. Sort the cabinets into keep, archive and destroy, list what is destroyed, and use confidential waste or a certified shredding service for personal data. If there is no policy, I ask who owns it before touching anything.

Before an office move I was asked to clear out six filing cabinets. I did not start shredding. I asked my manager for the retention schedule, which says how long we keep HR, finance and customer records. I went through each drawer and made three piles: records still within their period, records past it that could go, and records I could not place. I took the last pile to my manager and the finance lead. For the pile that could go, I made a list of what was destroyed and the dates, and used the locked confidential waste bin and the shredding company, with a certificate. Records still in date were boxed and labelled for the new office. The move was easier because we carried less, and I could show what we had disposed of and why.

Do not change the details or pay. Call the supplier on a number I already hold, not one in the email, to confirm both the old and the new details, then follow the change procedure, including a second person's sign-off. Report the email to IT, as it may be a payment diversion fraud.

Ten minutes before the payment run, an email arrived from a regular supplier saying their bank details had changed and asking me to update them for today's payment. I knew the request was a red flag: it was urgent, near a deadline and about bank details. I did not reply. I looked up the supplier's number in our contract file and phoned their accounts team. They told me they had not changed accounts and had not sent that email. I forwarded the email to IT, as our policy says, and told my manager. We held the payment until the right details were confirmed, and sent the supplier a warning that their email might have been compromised. A request to change bank details should always be checked on a number you already know, never one in the email. We also added a rule that any change needs a call-back and two sign-offs. A phone call took two minutes and could have saved thousands.

Show the evidence: time each step, show which two add nothing, and say what could go wrong if they are removed. Check with the people who own the process, trial the shorter version on a small batch and compare errors. Ask my manager to approve it before I change anything.

Our weekly expense report had six steps, and two of them copied data from one spreadsheet to another and then back again. I timed the process over three weeks and found it took about forty minutes, with fifteen of them on those two steps. I asked the finance team who used the report whether they needed the copied sheet. They did not. I wrote one page for my manager: current steps, proposed steps, time saved, and the one risk, which was that the copy acted as a check. I proposed replacing it with a formula that flagged mismatches. She agreed to a trial. I ran both versions for two weeks side by side. The new version caught the same errors and took twenty-five minutes. I wrote it up, updated the procedure document, trained the one colleague who also ran the report, and told finance. The business administrator standard asks administrators to review processes and suggest improvements, and proposing a change with evidence is how I do that.