Prepare evidence against the actual job description
Underline the responsibilities in the vacancy: calendar management, customer contact, document preparation, purchasing, or record keeping. These are different tasks. For each responsibility, note one real example and a tool you actually used. If you have not used their system, explain the comparable workflow you know and what you would need to learn.
Your examples can come from work, study, volunteering, or organizing a project. Be specific about the volume and complexity only when you can support those details. Do not turn familiarity with a spreadsheet into a claim of advanced financial expertise.
How do you handle several urgent requests?
Explain how you assess deadlines, impact, dependencies, and who can authorize a change. Simply saying “I multitask” leaves your judgment invisible. A useful answer shows what you clarified, what you prioritized, and how you communicated the trade-off.
Fictional example: “A manager needed a meeting moved while a supplier was waiting for a purchase confirmation. I checked the supplier’s cutoff and confirmed whether the meeting was flexible. I sent the time-sensitive confirmation after getting approval, then offered two meeting times and updated the attendees. I told the manager the order I was following so there was no unexplained delay.”
Be ready for a follow-up: what if both deadlines were fixed? Describe escalation and options rather than promising to complete incompatible tasks simultaneously.
How do you prevent errors and protect confidential information?
Describe an actual checking routine: confirm the source, check dates and recipients, compare the final document with the request, and resolve discrepancies before sending. For confidential work, explain how you verify authorization and use approved access controls. Avoid sharing the confidential information itself during the interview.
Practice answering: “Tell me about a mistake you caught” and “What would you do if someone requested a document they might not be authorized to see?” Separate an example of something you did from a hypothetical process you would follow.
Try a ten-minute prioritization exercise
Imagine three requests: a visitor arriving in fifteen minutes, a report due tomorrow that depends on missing data, and an invoice with a cutoff today. List the questions you need answered before deciding. Then write the first action for each request and a short update to the people affected.
There is no universal order without more context. Explain your assumptions: visitor arrangements might take one message; missing report data might need requesting immediately even if the report comes later. Good prioritization includes starting dependencies early, not only finishing tasks in a queue.
Ask about the working relationship
Ask: “Who sets priorities when several people request support?” and “Which recurring tasks need the most attention to detail?” The answers help you understand expectations. Before the interview, prepare one scheduling story, one accuracy story, and one example of handling a difficult request.
Use the free STAR answer builder to organize those examples. Read your answer aloud and remove background that does not explain your decision. The goal is a clear, truthful account you can discuss, not a script to recite.