Questions to Ask in a Project Coordinator Interview
A project coordinator job can be the first step toward running projects or a support desk for five managers, and the posting seldom says which. These questions to ask in a project coordinator interview are for the candidate's turn at the end: they open with the role and the managers you would support, then cover the daily tracking work, who decides when requests collide, where the job leads, and hours and pay. The last group is for employers, with questions to put to a coordinator candidate.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
The role
Which projects and which project managers would I be supporting?
Why ask it
Ask for names and a count. One project manager on one large job is close to an apprenticeship, while five managers across a dozen small jobs is closer to a service desk. The split can shift as projects finish, so it helps to know who sets it.
What does a typical day look like for a project coordinator here?
Why ask it
Have them walk through what the current or last coordinator did yesterday, in order. Listen for how much of it was updating a tracker, how much was sitting in meetings and how much was chasing other people for answers. If nobody can describe it, the role has not been shaped yet and you would be shaping it.
How much of the role is scheduling, tracking and admin, and how much is work I would own outright?
Why ask it
A rough percentage is enough, followed by one example of something a coordinator there owns from start to finish, such as a vendor order or the weekly status report. If no example comes to mind, the job is support all the way through. That suits plenty of people, as long as it is said plainly before you accept.
Is this a new coordinator position, or did someone hold it before me?
Why ask it
A predecessor who became a project manager is the best evidence you will get about where the seat leads, and how long it took them is your rough timeline. If the last person left instead, what they found hardest is worth one follow-up. In a brand-new role, nobody has yet agreed which tasks the project managers will actually let go of.
By the end of my first three months, what should the project managers no longer be doing themselves?
Why ask it
The reply is your first duties, ranked by the people you would support. Meeting notes and schedule updates are a common place to start. If the list runs on into client contact or budget tracking, the job is bigger than the title suggests and the training matters more.
Who else is on the project team, and would I be the only coordinator?
Why ask it
Two or three coordinators can cover each other's leave and compare how they handle the same manager. A lone coordinator is the single point of contact for everything, which is more visible and harder to step away from. Find out who updates the trackers when the coordinator is off.
Who would train me in the first few weeks, and is the way you run projects written down anywhere?
Why ask it
A procedures folder or a project handbook means you can look things up before interrupting someone. Where the process lives in the project managers' heads, the training is shadowing, and how good it is depends on which manager has a quiet week when you start.
What stage are the projects at right now: just starting, mid-delivery or closing out?
Why ask it
Joining at kickoff means you set up the trackers and the folders your own way. Joining halfway means inheriting somebody else's spreadsheet and a backlog of open actions, possibly from a person who has already gone. Closeout is heavy on paperwork: final documents, sign-offs and archiving.
What is the biggest challenge the project team is dealing with right now?
Why ask it
A team short of people wants a coordinator to absorb the overflow, and a team with an unhappy client wants tighter records and faster follow-up. Either answer describes the first month you would have. Ask which part of it a coordinator could take on first.
How much do I need to know about the industry itself, as opposed to how projects are run?
Why ask it
A coordinator on a building job handles submittals and requests for information, and one on a software team lives in tickets and release notes. How long the last person needed before the vocabulary stopped slowing them down is the useful figure. Say honestly which parts are new to you, since the first week would show it anyway.
Would I deal with clients, vendors or subcontractors directly, or does that go through the project manager?
Why ask it
Direct contact makes the job more visible and more exposed. Sending a client meeting times and document requests is one level of trust, and sending progress updates is another, so an example of a real message shows which they mean.
The daily work
Which software do you use to plan and track projects, and what would I be expected to know on day one?
Why ask it
You might hear Microsoft Project, Smartsheet, Asana, Jira, Procore or a shared spreadsheet, and each is a different week of learning. If you have not used theirs, name the closest one you have and ask how the last hire got up to speed. A spreadsheet-only shop is worth a follow-up about who built it and who is allowed to change it.
Who keeps the project schedule up to date, the coordinator or the project manager?
Why ask it
Typing in dates that someone else decided is data entry. Building the schedule, linking the tasks and noticing that one slip moves three others is the start of planning. Which of the two the coordinator does today, and whether that could grow, says a good deal about the route to project manager.
Do the projects follow a set method, such as Agile sprints or a phased plan, and what does that mean for the coordinator's week?
Why ask it
The method sets your calendar. Sprints bring daily stand-ups and a board to keep current, and a phased plan brings gate reviews and a long schedule to maintain. In either case the coordinator is often the one booking those sessions and recording what came out of them.
Would I prepare the status reports, and who reads them?
Why ask it
Writing the weekly report is one of the quicker ways to learn a project, because you have to ask what every line means. Find out whether the project manager edits it before it goes out and whether it reaches the client or stays inside.
Which meetings would I schedule or take minutes for, and who chases the action items afterwards?
Why ask it
Minutes are the easy half. Chasing is where the job gets harder, since it means reminding people senior to you that they promised something. If that falls to the coordinator, ask how the project managers respond when an item stays open for weeks.
Are there templates and a set filing structure, or would I be building those?
Why ask it
Where a project office hands you templates, the task is to learn them and keep to them. Where there are none, your first real piece of work is creating the system, which is more ownership than the word 'coordinator' suggests. A tracker or a report from a live project, if they can show one, settles this faster than a description.
Would I handle any of the money side: purchase orders, invoices, timesheets or budget tracking?
Why ask it
Matching invoices to purchase orders is exacting work, and a useful skill if you want to manage projects later. The line to locate is between entering the figures and being expected to question one that looks wrong. Whoever approves the spending is the person your queries would go to.
How much document control is in the role: contracts, drawings, change requests, sign-offs?
Why ask it
In construction and engineering this can be most of the job. Ask what happens when someone works from an out-of-date version, because preventing that is what you would be answerable for. Which system holds the documents, and who else can file into it, decides how hard that is.
Would I also book travel, order supplies or cover other general office tasks?
Why ask it
Some coordinator jobs are office administration with a project title on top. That is not a problem when it is stated up front. What matters is the share of the week it takes, and whether those tasks give way when a project hits a busy stretch or stay on your list regardless.
What tends to fall through the cracks on your projects that you would want a coordinator to catch?
Why ask it
The approval nobody followed up, the vendor date nobody confirmed, the action from three meetings ago: the thing they name is the heart of the job. It also deserves a line in your thank-you note, next to a time you caught something similar.
When I can see that a task is going to be late, what do you want me to do about it?
Why ask it
This shows whether the coordinator is a recorder or a voice. 'Tell the project manager that day' is a common instruction, and the next level up is being expected to speak to the person doing the task as well. If the reply is to mark it red and move on, the role stops at the tracker.
Who decides
Who would I report to: one project manager, a project office lead or someone else?
Why ask it
The person who writes your review is not always the person who hands you work. When they are different people, ask how the reviewer finds out what you did all year. A coordinator who reports to a manager they rarely see needs the project managers to speak up for them.
When two project managers both need something from me by the end of the day, who decides which comes first?
Why ask it
You are hoping for a name, usually the person you report to, or a standing order such as 'the project nearest a client deadline'. 'You would work it out between you' leaves the most junior person in the room refereeing between managers. Ask when it last happened and how it ended.
How is a coordinator's time divided between projects: a fixed share for each, or whoever asks first?
Why ask it
A set split, say two days on one project and three on another, lets you tell a manager that their request belongs to Thursday. Without one, the most insistent manager gets the most of you. Hours logged against each project are your record when someone feels shortchanged, so it is worth knowing whether they are kept.
How do the project managers differ in the way they like to work with a coordinator?
Why ask it
One wants a call before anything goes to the client, another reads only the tracker, a third forwards emails with no comment. An interviewer who can describe those habits has been paying attention to the role. If you take the job, keep your own page of each manager's preferences from the first week.
Can a coordinator say 'not today' to a request, and how did that go the last time it happened?
Why ask it
The example matters more than the policy. If the last coordinator pushed back and was backed up, you have room to manage your own workload. If nobody can remember it happening, assume everything handed to you is expected to be done.
When I need something from a person senior to me and they do not answer, what is the next step?
Why ask it
Much of coordinating is chasing people you have no authority over. A workable ladder is a second reminder, then a copy to the project manager, then the manager raising it themselves. If the only step is to keep asking, you would be held to dates you cannot enforce.
Would I make any decisions on my own, and can you give me an example of one?
Why ask it
Moving a meeting, choosing a courier or approving a small order are typical. The examples are minor, and they show how far the team trusts the seat. The other half of the answer is what must always go to the project manager, which is the line you need on your first day.
If a project manager is out for a week, would I cover for them, and what could I decide while they are away?
Why ask it
Covering is how many coordinators get a first taste of running the work. It can also mean carrying a manager's responsibility with none of the authority, so ask who you would call when a client wants an answer you cannot give.
Growth
Is there a path from project coordinator to project manager here, and has anyone taken it?
Why ask it
A named person and a rough timeline are what you are after, because a path that exists only on a chart is hard to plan around. How long it takes differs from one employer to the next, so their example is the only figure that counts. If no one has made the move, ask where the coordinators went instead.
What would I need to show before being trusted with a small project of my own?
Why ask it
Good answers are things you can do on purpose: run the weekly meeting, keep the schedule through a whole phase, handle a vendor alone. Write the list down. It becomes the agenda for your first review if you take the job.
Would the company help with a credential such as the CAPM or PMP, or with other project management training?
Why ask it
Help can mean exam fees, a course, or study time during work hours, and each employer draws that line in its own place. The eligibility rules belong to the body that issues each credential, so check those yourself and do not rely on an interviewer's memory of them. A flat no still tells you how the company sees the role.
Would I sit in on planning sessions, budget reviews and client meetings, or mainly hear about them afterwards?
Why ask it
Watching a project manager argue for a date or explain an overrun is training no course supplies. Being there only to take notes still counts. Being kept out and handed the outcome to type up makes it hard to learn the next job.
How is a coordinator's work judged here, and how often would I hear how I am doing?
Why ask it
Coordination done well looks like nothing going wrong, which makes it easy to overlook. Listen for things a reviewer could point to: reports out on the day, actions closed, project managers requesting you for their next job. Feedback gathered from every manager you support is fairer than one manager's view.
What separates a coordinator you would promote from one who simply does the job well?
Why ask it
A frequent answer is some version of anticipation: one coordinator waits for the request and the other has it ready. Push past the adjective to a specific thing a past coordinator did that made someone think 'project manager'. That story is your target.
Terms and closing
What are the usual hours, and what happens to them in the weeks before a deadline or a launch?
Why ask it
The last crunch is the one to pin down: how long it ran and how many evenings it took. A coordinator's hours tend to follow the managers they support, so the busiest manager's habits are a fair guide to yours.
Is the job in the office, on a project site, hybrid or remote, and does that change with the phase of the project?
Why ask it
Construction and event coordinators may be needed on site on certain days, and site hours can start earlier than office hours. Travel between locations, and who pays for it, belongs in the same answer. A remote role may still expect you in person for kickoffs or client meetings.
Is this a permanent position, or is it funded by one project or contract?
Why ask it
Some coordinator jobs exist because a single project needed one, and they end when it does. Ask what became of the last coordinator when their project closed. A contract role can still be a good one if you know the end date going in.
Is the role paid hourly or by salary, and how is time beyond the normal week treated?
Why ask it
How extra hours are handled depends on where the job is and how the employer classifies it, so the thing to learn is what happens there: paid, given back as time off, or neither. If the answer matters to you, ask to have it in the written offer.
What range have you budgeted for this role, and where in it would my experience put me?
Why ask it
Coordinator pay varies a lot by industry and location, so their range is worth more than any general figure you have read. If the interview has shown the job includes budget tracking or client contact, mention that when you discuss where you fall. A recruiter is often the better person to ask than a project manager.
If I took on more of a project manager's work over time, would the title or the pay move with it?
Why ask it
A coordinator's duties can grow faster than the title. A step in between, such as senior coordinator or assistant project manager, gives the extra work a name and gives a pay review something to attach to. Without one, extra responsibility is a favor until someone decides to recognize it.
What do you like about working with this project team?
Why ask it
If the interviewer is one of the project managers you would support, the answer is a preview of your own working week. A specific story, such as how the team got through a bad delivery, is worth more than 'great people'. It is an easy one to put to each person you meet, and the answers are worth comparing.
Could I talk to one of the project managers I would be supporting?
Why ask it
Their habits would become your working day, so ten minutes with one of them tells you more than the posting. Two things to get from that conversation: what they most want off their desk, and what the last coordinator did that they miss. If it cannot happen now, the offer stage is a reasonable time to ask again.
After this conversation, what would make you hesitate to hire me as your coordinator?
Why ask it
For a coordinator the hesitation is often the software, the industry, or never having served several managers at once. Answer it with one short example and stop. Hearing the concern now is better than guessing at it after a rejection.
What is the timeline from here, and would there be a handover from whoever is doing this work now?
Why ask it
Somebody is updating the trackers at the moment, whether a departing coordinator or a project manager doing it late in the day. An overlap with that person, even a few days, is worth requesting. An empty seat means a backlog, and what is in it tells you how your first month would go.
For employers
Tell me about a project you supported. Which parts were yours, and which belonged to someone else?
Why ask it
Strong candidates draw the line cleanly: 'I kept the schedule and the action log, and the project manager dealt with the client.' Be wary both of someone who claims the whole project and of someone who cannot name one thing they owned.
How do you keep track of tasks and deadlines when you are working on several projects at once?
Why ask it
You want a real system described in detail: one list checked every morning, a tracker with owners and dates, reminders set before a deadline and not on it. Ask what it looked like last Monday. 'I am just very organized' is a claim with no method behind it.
Two project managers each hand you something due today and you can finish only one. What do you do?
Why ask it
The weak answer is a silent choice. A good one has the candidate asking both managers what the deadline really protects, then telling the one who will wait before the time runs out. Change the scenario to match your own team so the answer is useful to you.
How do you follow up with someone senior who has not delivered what the project needs?
Why ask it
This is the standing difficulty of the job, so ask for a real case. Listen for a specific request with a date and a reason attached, then a point at which they brought in the project manager. Candidates who say they would never bother a director will let dates slide politely.
Tell me about an error you caught before it reached the client or the project manager.
Why ask it
Anyone can write 'detail-oriented' on a resume. A wrong date in a schedule or an invoice that did not match its purchase order is proof, and the useful follow-up is how they caught it: a routine check, or luck.
Which project tools have you used, and what did you do in each one?
Why ask it
Viewing a Gantt chart and building one with linked tasks are different levels of skill, and a list of product names hides which the candidate has. If the tool matters to you, set a ten-minute exercise: hand over a jumbled action list and ask for it back in a form they would send to the team.
Where would you like this job to lead in the next few years?
Why ask it
Many coordinators want to become project managers, and that ambition is a reason to hire them if you can offer the route. If you cannot, say so in the interview. Someone who would be happy to stay a coordinator for years is just as good a hire for a seat with no step above it.
Using your questions to size up a coordinator job
Practical guidance for the conversation itself
Before you go in
Underline the verbs in the posting
Go through the job posting and mark every verb: schedule, track, update, assist, coordinate, manage, own. A posting built on 'assist' and 'support' describes a support seat. One that says 'manage' and 'lead' is either a junior project manager's job under a cheaper title or wishful writing. The opening questions under The role are there to find out which.
Work out who can answer what
A recruiter can usually answer on hours, the pay range and whether the role is permanent. A project manager you would support knows what the days hold and what they want off their desk. A project office lead or department head knows whether coordinators move up. Asking a project manager about the salary band, or a recruiter about the tracking software, mostly gets you a guess.
Take one from each group
The time left for a candidate's questions is often short. Take one from each of the first five groups and put first the one whose answer could change your mind. For most people that is the split between admin and ownership, or who settles it when two managers want the same afternoon.
Decide what you want the job to be
Some people want coordination as a step toward managing projects, and some want it as steady work in its own right. Both are sound reasons to apply, and they point to different questions. If you want the step, spend your time on Growth. If you want the steady job, spend it on Who decides and on hours, because those settle whether the work stays manageable.
While you are asking
Ask about last week
'What does the coordinator do?' gets the job description read back to you. 'What did the coordinator spend last week on?' gets the launch that ate three days, the report that went out late and the manager who needed everything reprinted. Nearly every question under The daily work gets a better answer when it is pinned to a recent week or a named project.
Add one line about yourself
A question can carry evidence. 'In my last job I kept the action log for two teams, so I am curious who chases the open items here' asks the question and shows you have done the work. Keep it to a single clause so it does not turn into a second round of selling.
Let your note-taking be seen
The job is largely about capturing who said what and what happens next. Writing down the project names, the tools and the managers' names as they come up is a small live demonstration of that. Read one detail back before you leave, such as the software they named, to confirm you have it right.
Raise pay once, with the right person
If a recruiter gave a range earlier, confirm it with them and leave it out of the conversation with the project managers. If nobody has mentioned pay by the final round, it is fair to ask. Put the question after the ones about the work, so the answer can take account of what the job turned out to include.
Making sense of what you heard
Sort the tasks into two columns
Afterwards, list every task they mentioned under one of two headings: 'I keep it current' and 'I produce or decide it'. Updating a schedule goes in the first column and writing the status report goes in the second. A page with everything in the first column is a tracking job, whatever the title says.
Count the people who can hand you work
Add up the project managers, plus anyone else who was named as a source of requests. Then check whether you heard a rule for ranking them. Four managers and a clear tiebreaker is a workable week. Two managers and no tiebreaker can be harder.
A promotion story needs a name
'There is definitely room to grow' costs nothing to say. A former coordinator who now runs projects there, and whom you could look up or meet, is evidence. If the path is real but nobody has walked it yet, ask what the first person would have to do, and decide whether you want to be the test case.
Compare two accounts of the week
If you get to meet someone doing the job, or one of the managers you would support, put the admin-and-ownership question to them as well. A gap between the two versions need not mean anyone is misleading you: the interviewer may be describing the job as planned and the coordinator the job as it runs. Plan on the second.
If you are the one hiring
Describe the seat before you test for it
Tell the candidate how many managers they would serve, which tools you use and how much of the week is general admin. Coordinator candidates often cannot tell from a posting whether the job is a first step in project management or an office role, and the ones you want will choose better with the facts in front of them.
Swap one hypothetical for a small task
Organization is easier to see than to hear about. Hand over a short, jumbled set of meeting notes and ask for the actions, owners and dates in a form the candidate would send out. Ten minutes shows you their eye for detail and how they write to people senior to them.
Be plain about how far the job goes
If coordinators at your company do become project managers, say who did and how. If the role has no step above it, say that too. A candidate who took the job expecting a promotion that was never available is likely to leave about when they have become most useful.