What a general interview actually sounds like for this role
The questions in a general session aren't written for admin work specifically, and that's the point. A candidate gets asked why they're looking for their next role, how they handled a disagreement with a coworker, what they do when priorities shift without warning.
None of that requires a posting to have already narrowed the field between an entry-level office assistant title and an executive assistant one.
What changes is how those universal questions land once an admin candidate starts answering them: a question about a coworker disagreement tends to pull out a scheduling conflict or a mix-up over who owns a task, since that's the kind of friction the job actually produces day to day. The interviewer isn't asking about admin work directly, and admin work still ends up being most of what gets described anyway.
What gets covered without a posting or resume on file
A general session opens with background and motivation questions, moves into a behavioral question or two, and checks how a candidate prioritizes competing demands, all without reading a job description or a resume first. There's no software check here and no scenario built around a specific title's tools, since neither document exists yet for the AI to draw from.
What a general session does surface is how a candidate talks under a small amount of pressure before any posting-specific stakes get added on top, worth knowing on its own before narrowing practice toward one particular opening.
Scoring
How the five dimensions read on a general admin session
Communication carries more weight in how a general session reads for this role than it might elsewhere, since there's no technical challenge or posting-specific detail to lean on if an answer runs short.
A candidate who can talk clearly through a coworker-conflict story or a prioritization question, without a scheduling scenario to anchor the answer, tends to score better on that dimension than one who needs a concrete prompt to organize a response.
Behavioral scoring follows the same logic: the interview doesn't hand over a scenario, so a candidate has to supply their own concrete story when asked about a past situation. The penalty system still applies in full, including the deduction for finishing without asking the interviewer anything back, a habit worth building here since a real admin interview usually closes the same way.
Frequently asked questions
Do I need to pick a specific admin job title before running a general interview?
No. A general session runs the same standard background, motivation, and behavioral questions regardless of whether the target is an office coordinator, receptionist, or executive assistant opening, so it works fine before that choice is made.
Will a general interview ask about scheduling or discretion the way a real admin interview would?
Not directly. General questions are the standard round asked across most roles, not admin-specific ones, though behavioral answers about coworker conflict or prioritization tend to surface scheduling and discretion situations anyway, since that's what the actual work produces.
Should I run a general interview before or after a job-description-based one?
Before makes sense if no specific posting is picked yet. A general session gives a baseline reading on communication and behavioral answers, then a job-description session can narrow practice once a real opening is targeted.
Does a general interview check my calendar or scheduling software knowledge?
No. There's no posting or resume for the session to draw a tool-specific question from, so a software check isn't part of a general interview. That kind of question shows up in the job-description-based type instead.
Related pages
Start with a general interview before you pick a posting
Run a general AI interview to get a baseline read on how you talk through background and behavioral questions, then move to a job-description session once a specific admin opening is in view.