Project manager: job description, interview questions, and screening workflow

The generic advice for this role is "check for a PMP certification and experience with your project management tool." Neither one tells you what actually breaks this hire. A certification proves someone studied a methodology. Tool experience is the easiest thing to train. What actually determines whether a project manager works out at a small company is whether they can get a designer, a contractor, or a client's own staff, none of whom report to them and none of whom have to listen, to actually deliver on time. There's no PMO backing them up and no formal authority to lean on. This guide is built to screen for that, because it's the thing a resume and a certification both hide.

What a project manager actually does at a small company

At a large company, a project manager usually operates inside a PMO: standardized templates, an escalation path, sometimes even the formal authority to pull resources. At a small agency, contractor, or professional services firm, a project manager is often the only person holding a project together, with no team of their own and no formal authority over the people actually doing the work.

The core of the job, in practice:

• Keeping scope, timeline, and budget on track for one or more projects at once
• Getting designers, developers, contractors, or a client's own staff to hit deadlines without having any authority to fire, promote, or formally direct them
• Spotting early that a project is going off the rails, before it becomes a crisis
• Managing scope changes and stakeholder requests without letting either derail the timeline
• Communicating status honestly, including bad news, to clients or leadership
• Deciding what to handle themselves versus what to escalate
• Building just enough process to keep a small, often part-time or multi-hatted team aligned, without burying them in meetings

The methodology part of this job is learnable from a book or a certification course. The part that actually predicts success is influence without authority: getting people who don't have to listen to actually deliver, calmly, and repeatedly. That's what this guide screens for.

Job description you can post today

Copy this, then adjust the specifics (your project types, your tools, your team structure) to match your company.

Project manager
[Company name] is looking for a project manager to keep our projects on scope, on time, and on budget. You'll work across our team and directly with clients or stakeholders, often without formal authority over everyone whose work you're coordinating.

What you'll do
Own project scope, timeline, and budget from kickoff to delivery. Keep contributors, some of whom you don't formally manage, aligned and on deadline. Spot risk early and raise it before it becomes a crisis. Manage scope changes and stakeholder requests without letting the project drift. Communicate status clearly and honestly, including when something's off track.

What we're looking for
A real track record of running projects, ideally with a mix of internal and external stakeholders. Comfort getting buy-in and deadlines from people who don't report to you. Clear, direct communication, including the ability to say no or deliver bad news. Familiarity with project management tools like [Asana, Monday, Jira] is a plus, not a requirement, if the fundamentals are strong.

Schedule
[Insert hours, remote/hybrid/in-office policy, and any client-hours expectations]

[Insert pay range, per your company's policy and any applicable state salary transparency requirements]

10 interview questions, and what a good answer sounds like

1. Tell me about a project where a key deliverable came in late, and it genuinely wasn't your fault. What did you do?

You're checking for ownership without excessive blame. A strong answer names what actually went wrong, what they did in the moment (communicate early, adjust the plan), and doesn't spend the whole story pointing fingers. A candidate who can't own any part of a late delivery, ever, is a flag.

2. Tell me about a time you had to get someone who doesn't report to you to hit a deadline they were resisting.

This is the single most important question on this list. A strong answer names a real, specific tactic: understanding what was actually blocking them, finding shared stakes, escalating appropriately if needed, without pulling rank they don't have. A candidate who can only describe this in the abstract, or who can't produce a real example, likely hasn't had to develop this skill yet.

3. A client or stakeholder changes scope halfway through a project. Walk me through how you handle that conversation.

Strong answers describe naming the impact clearly (on timeline, budget, or both) rather than just absorbing the change silently, and negotiating a real tradeoff. A candidate who says they'd just "make it work" without addressing the impact is setting up a burned-out team and a blown deadline.

4. Describe how you'd set up a new project from scratch. What's the first thing you actually do?

Listen for a real starting point: clarifying the actual goal and success criteria, identifying stakeholders and dependencies, before jumping to a timeline or a tool. A candidate who starts with "I'd set up the Gantt chart" is starting with the artifact instead of the understanding.

5. Tell me about a time a project was quietly going off the rails. How did you notice, and what did you do?

This tests proactive risk-spotting. Strong answers name a specific early signal they caught (missed a small deadline, a stakeholder went quiet, scope kept creeping) and a specific intervention. A candidate whose projects only ever go off the rails in ways they "couldn't have seen coming" may not be watching closely enough.

6. How do you decide what to escalate to leadership versus handle yourself?

Good answers describe a real threshold: risk to the timeline or budget, whether it's a repeat pattern, whether it needs authority they don't have. A candidate who escalates everything, or nothing, hasn't developed real judgment about it yet.

7. Walk me through how you'd keep a small team, several of whom are also doing other jobs, aligned without daily status meetings eating everyone's day.

This is specific to a small-company reality. Strong answers describe lightweight, asynchronous habits: a short written update cadence, a single source of truth for status, meetings reserved for actual decisions. A candidate who defaults to "more meetings" as the answer to alignment may create more friction than clarity on a small, stretched team.

8. Tell me about a time you had to say no to a stakeholder's request.

Listen for directness paired with a real reason, not just refusal. A strong answer explains the tradeoff they named and how the stakeholder responded. A candidate who can't recall ever saying no may struggle to protect a project's scope and timeline when it matters.

9. What's your process when you inherit a project mid-stream with little or no documentation?

Good answers describe actively rebuilding context: talking to stakeholders, reviewing whatever artifacts exist, confirming the actual goal before assuming the plan in place is still right. A candidate who'd just pick up where the paper trail left off, without questioning it, may inherit someone else's mistakes along with the project.

10. Why project management at a small company, rather than a larger organization with a dedicated PMO and more defined process?

This surfaces whether they understand what they're signing up for: less structure, less formal authority, more direct ownership. A candidate who can't name a real reason beyond "it was the job that was open" may be underprepared for how much of this role is built from scratch at a small company.

A scorecard you can score candidates against

Ten questions are only useful if everyone on your side is listening for the same thing. Score every candidate on the same six signals, so you're comparing evidence instead of comparing gut feelings.

How to screen project manager candidates without losing a week to it

Truffle is a candidate screening platform that combines resume screening, one-way video interviews, and talent assessments, so you can build a screening workflow around what actually matters for a role where the wrong hire quietly costs you missed deadlines and frustrated clients for months before it's obvious.

Project manager openings tend to pull a mix of candidates: people with a real track record running projects, and people who've held an adjacent title without the influence-without-authority skill this role actually needs. That mix is exactly what a layered screen is built to sort through.

A workflow that fits a small agency, shop, or firm:

• Resume screening first. Cut obvious mismatches on relevant project experience and scale before you spend live interview time on anyone. This is also where you handle volume, since a flood of applicants for one opening is manageable once you're not reading every resume yourself.
• A short one-way video interview for your first real look. Ask 2-3 of the scenario questions above, especially the influence-without-authority question and the scope-change question, so you can hear how someone actually reasons through the moments that matter most, before you commit any live interview time.
• A leadership-focused skills check instead of a long take-home. Our leadership skills test surfaces the same influence, delegation, and conflict-handling signals that separate a project manager who can actually move people from one who can only move a spreadsheet.
• A live conversation only for candidates who clear the first three steps. By this point you already know they can reason through influence, risk, and scope conversations. The live conversation is for fit and specifics, not for finding out for the first time whether they have the judgment for the job.

Our resume screening and one-way video interview tools handle the first two steps in one place, with AI that surfaces your strongest matches against the criteria you set. You review the evidence and decide. It doesn't decide for you.

What the leadership skills test surfaces for this role

Project management at a small company is really a leadership problem without a title to back it up, so it's not a fixed-answer skills test. Instead, Truffle's leadership skills test walks a candidate through real scenarios and surfaces three signals that matter directly for this hire:

• How they delegate under pressure. One scenario asks how a candidate decides what to hand off when they're overloaded and their team is waiting on approvals. Strong answers delegate outcomes with clear boundaries and a check-in cadence. Weak answers delegate tasks but keep every decision, which doesn't scale past one or two projects.
• How they decide with incomplete information and disagreeing stakeholders. A scenario asks about a real decision made without enough data while two stakeholders disagreed. Strong answers pick a decision method deliberately, deciding alone, consulting, or building consensus, and say up front which one applies. Weak answers stall for more data or default to whoever pushed hardest, a bad habit in a role built on managing competing priorities.
• How they handle conflict between people they need to keep working together. A scenario asks what a candidate actually does when two valuable team members can't stand each other. Strong answers surface the conflict early and facilitate a conversation that ends in specific agreements. Weak answers avoid it or take it over completely, both of which a project manager without formal authority can't really afford to do.

The point isn't a perfect score on a leadership questionnaire. It's that these scenarios surface, in a few minutes, the influence and judgment skills that ten interview questions alone can take an hour to get to. Truffle's AI scores and surfaces the results against the bar you set. You still make the call on who clears it.

Common hiring mistakes for this role

Weighting a PMP certification over real influence-without-authority examples. A certification proves someone studied a methodology. It says nothing about whether they can actually get a resistant contributor to deliver, which is the daily reality of this job at a small company with no PMO behind them.

Treating tool familiarity as a proxy for skill. Knowing your specific project management tool is the easiest thing to train and the least predictive of success. A strong PM in an unfamiliar tool will out-perform a tool expert with no influence skill.

Not testing how they handle scope change and pushback directly. A project manager who absorbs every scope change silently, or who's never had to say no to a stakeholder, will struggle to protect your timeline and budget when it matters most.

Skipping a real risk-spotting question. The value of a good project manager is often invisible: the crisis that never happened because they caught it early. Ask directly for a specific example, since it won't show up on a resume.

Assuming more process automatically means better management. On a small, often multi-hatted team, a project manager who adds heavy process and daily meetings can do more damage than one who builds a lighter, asynchronous system that actually gets used.