All jobs / Project / delivery manager
Budget & Vendors interview questions
Budget & Vendors questions a Project / delivery manager can be asked, from first job to senior. Open one to see the strongest answer and why it works.
You own a project budget. What do you track each month, and why is “invoices paid” not enough?
The strongest answer: Spent to date, committed spend — orders raised but not yet invoiced — and the forecast to complete against the budget, with the variance explained; paid invoices lag by weeks and miss what is already promised
Why it works: Right — spent, committed and forecast-to-complete together tell you where you will land; invoices alone tell you where you were.
- Spent, committed, forecast.
- Track committed, not just paid.
- Forecast to complete monthly.
- Explain the variance.
You are contracting a vendor for work whose scope is only roughly defined. They offer fixed price or time-and-materials.
Which do you lean towards, and why?
The strongest answer: Time-and-materials with a cap and milestone reviews while scope is unclear — fixed price on vague scope makes the vendor pad or fight every change; fixed price suits work we can specify precisely
Why it works: Exactly — match the contract to the certainty you have; T&M with controls buys flexibility, fixed price buys predictability only when the spec is real.
- Match contract to certainty.
- Vague scope: T&M with a cap.
- Precise scope: fixed price.
- Milestones either way.
A vendor promised “next month” with no range and no written interface. How do you treat the date?
The strongest answer: As a hope — I keep our forecast as a range that assumes they slip, I ask for a written interface and a next check, I do not put their month on our slide as fact
Why it works: Exactly. Vendor months are inputs, not our date. Range, interface, next check.
- Treat the vendor month as hope.
- Keep our range wider.
- Ask for a written interface.
- Do not ink their month on our slide.
A contract wants a single delivery date. How do you protect the forecast?
The strongest answer: I keep an internal range, I name assumptions in the contract talk, and I refuse to treat their date as a fact we already know — I do not hide the range from our own team
Why it works: Exactly. Contracts can constrain; they do not create knowledge. Internal range stays visible.
- Keep the internal range visible.
- Name assumptions in the talk.
- Do not treat the contract date as knowledge.
- Do not keep a secret second date.
Halfway through, your forecast to complete comes out well above the approved budget.
What do you bring to the sponsor?
The strongest answer: The forecast and its causes, options with consequences — cut scope, extend, add funding, or stop — and my recommendation; I bring it now, not when the money runs out
Why it works: Right — a sponsor can decide between options; a single request or a surprise gives them nothing to decide with.
- Causes, options, recommendation.
- Bring it early.
- Scope, time, money, or stop.
- Never tune the forecast.
You are outsourcing an entire workstream to a vendor for a year.
How do you structure the contract so delivery stays honest?
The strongest answer: Payment tied to accepted deliverables with written acceptance criteria, visibility of work in progress, IP, data and security obligations, a change process with regular reviews, and exit terms — never payment for reported percent complete
Why it works: Exactly — acceptance, visibility, obligations, change and exit are the five things that stop an outsourced year becoming a dispute.
- Pay for accepted deliverables.
- Written acceptance criteria.
- IP, data, security, exit terms.
- Change process and regular reviews.
Budget season funds delivery heads and treats discovery as “optional contractor days.” What do you change?
The strongest answer: I fund both tracks as part of the same bet — a thin, reserved discovery capacity — I do not treat learning as leftover money
Why it works: Exactly. Dual-track at the budget. Leftover learning is how next year’s range is a guess.
- Fund discovery as reserved capacity.
- Keep it on the same bet as delivery.
- Do not treat learning as leftover.
- Do not hide it in delivery codes.