Executive Assistant Interview
Questions & Answers

Prioritisation framework agreed with the executive: what categories of meetings require their presence vs what can be delegated or handled asynchronously? Buffer time protected around high-stakes meetings and travel. Standing blocks for the executive's own deep work that are not available for scheduling. When declining or rescheduling meeting requests, respond promptly with a proposed alternative that shows respect for the requester's time. Calendar management is strategy execution — you are protecting the executive's time for their highest-value activities.

Briefing document one day before: who is attending (LinkedIn profiles, role, history with the executive), the purpose of the meeting, context the executive needs (recent news about the other party, prior conversation notes from CRM), key talking points, and any open items from prior interactions. Pre-read materials highlighted for the executive's specific action items. Confirm logistics (location, dial-in, parking) the day before. A well-prepared executive walks into every meeting with full context — the EA is the intelligence operation that makes that possible.

Information the EA accesses (board communications, compensation data, M&A discussions, personnel decisions) is held strictly within the role. No discussion outside the office or with colleagues who do not have a legitimate need to know. Sensitive documents handled on secure systems and not forwarded to personal devices. When in doubt about whether to share information with a third party, ask the executive before sharing. The EA's value is partly built on the executive's confidence that sensitive information stays confidential — a single breach of that trust is unrecoverable.

Understand their communication style and adapt to it: some executives want bullet points, others want narrative. Learn their rhythm: when they are most accessible vs when they need to focus. Anticipate needs before they are articulated — after 3–6 months, you know what they will need before a major event or trip. Raise problems with proposed solutions, not just problems. Manage their time as if it were the company's most valuable resource — because it is. The best EAs develop a working relationship where the executive trusts them to make judgment calls within agreed parameters.

This is the core competency question for EAs. The situation should show proactive awareness: a scheduling conflict discovered three weeks early (not the day of), a venue that cancelled before the executive was told (and a replacement already booked), or a board package missing a document (caught before it was distributed). Show that you scan for problems continuously, not just respond to them. The EA whose executive is never surprised by avoidable problems has earned a level of trust that cannot be achieved by reactive problem-solving alone.

Structure your answer as a 60-second professional narrative: where you have been (your background), what you have done (your strongest achievement), and where you are going (why this role). Lead with your most relevant experience, not your entire career history. End with why you are excited about this specific opportunity.

Choose a genuine weakness that you have actively worked to improve. The structure is: name the weakness → show self-awareness of its impact → describe the concrete step you took to address it → show the improvement. Never say "I work too hard" — interviewers recognise this as evasion and it damages your credibility.

Use the STAR method (Situation, Task, Action, Result) but add a fifth element: what you learned. Choose a real failure, not a disguised success. Show you can take responsibility without making excuses, and demonstrate that the lesson changed your behaviour in a specific, verifiable way.

Be honest but constructive. Acceptable reasons: seeking greater scope, new challenge, skills you can not develop in the current role, or company-level changes (restructuring, direction shift). Never speak negatively about your current employer or manager — it signals you will do the same to the prospective employer in future conversations.

Describe the conflict specifically, show that you sought to understand the other person's perspective, and explain the resolution approach you took. Interviewers are assessing your emotional intelligence and whether you escalate or resolve. Avoid stories where you were right and they were wrong — choose a story where both parties grew.

Describe your specific prioritisation system: impact × urgency matrix, stakeholder alignment, or a specific tool or process you use. Then give an example where you applied it under real pressure. Show that your system is systematic rather than reactive, and that you communicate proactively when priorities change.

Choose an achievement that is specific, measurable, and relevant to the role. Lead with the result ("I reduced our error rate by 40% in 90 days"), then explain the context, challenge, and what you specifically did that drove the result. Show your ownership and impact, not just your team's work.

Be honest about your ambitions while showing that this role is a genuine step in that direction — not a stopgap. Hiring managers want to invest in people who will grow with the organisation. Show that your 5-year goal requires the specific skills and experience this role provides, making your ambition an asset for both sides.

Research before the interview and make the answer specific: cite their product, a recent company development, something about their culture or team, or a professional aspect of this particular role that matches your goals. Generic answers ("I love your values") signal you did not do the research. Specific answers signal genuine interest.

Always have 3–5 questions prepared. Ask about the biggest challenge in this role, what success looks like in the first 90 days, how the team operates, and the interviewer's own experience at the company. Never ask about salary, benefits, or holidays in a first interview. Questions show interest, strategic thinking, and that you care enough to have done research.