How to Talk About Your Experience in Interviews Without the Title

Interviewers are pattern-matching against a job title, and yours doesn’t say “Project Manager.” That’s a real disadvantage in the first ninety seconds — and one you can mostly neutralise with how you frame your answers.

Name the gap yourself, early

Don’t wait for them to notice your title doesn’t match. In your own introduction: “My title is Operations Coordinator, but for the last two years I’ve been the person accountable for running our system migrations end to end — scoping, scheduling, and reporting to leadership.” You’ve pre-empted the discount before it happens.

Answer in scope-and-outcome terms, every time

When asked about a project, resist describing your tasks. Describe your scope of accountability and the outcome, the way an interviewer would describe their own PM’s work. “I owned the rollout plan and was the point of escalation for the vendor” reads as PM work. “I helped coordinate the rollout” doesn’t, even if it was the same job.

Handle the direct question well

If asked “why haven’t you had the PM title yet,” a straight answer beats a defensive one: “The org didn’t formally recognise the role that way, which is part of why I’m looking to move somewhere it will.” That’s honest, not an excuse, and it signals self-awareness rather than grievance.

Bring your evidence, don’t just describe it

If you’ve built the portfolio described in Building a Portfolio Without a PM Title, offer to walk through a real example in detail — “I can show you the actual RAID log I kept for this, if useful.” Very few candidates offer real artefacts; it’s a strong differentiator.

Ask the interviewer a scope question back

“What would the PM be directly accountable for in this role, versus just involved in?” This does double duty: it gives you real information, and it signals you already think in terms of accountability boundaries — which is exactly the thing your title currently obscures.