The PM Pivot Series, Part 5 of 5: The Interview and the First 90 Days: How to Walk In Without the Title and Walk Out With the Offer

THE PM PIVOT SERIES, PART 5 OF 5

The final post in the PM Pivot Series — how Implementation Manager interviews actually work, what hiring managers are really listening for, and what to do once you land the role

Chile, we made it. Part 5. The final post.

If you’ve followed the whole series, you’ve gone from ‘I want to pivot’ to ‘I have a real plan.’ You audited your experience. You found the hidden lane. You picked your entry point. Now you have an interview scheduled. And the doubt is creeping back in. What if they ask me a question I can’t answer? What if they figure out I’ve never had the title?

Let me tell you something that will change how you walk into every interview from here forward.

Implementation Manager interviews are not knowledge tests. They’re not trying to quiz you on PM theory. They’re trying to figure out if you’re the kind of person they want sitting across from their most important customer during a go-live weekend when things are going sideways.

That’s a character test. A communication test. A thinking-out-loud test. And those tests you can prepare for, because they rely on a small set of recurring questions and a framework that works every time.

The framework that makes you instantly easier to interview

If you take one thing from this post, take STAR. It’s the answer structure hiring managers are trained to listen for, and it makes your answers dramatically easier to follow. It also keeps you from rambling — which is the single most common issue non-traditional candidates have. They start strong and trail off. STAR fixes that.

Situation. Set the scene. Where were you, what was the context, who was involved? Two sentences max.

Task. What were you specifically responsible for? What was the goal or problem?

Action. What did YOU do? Not your team. Not the company. You. This is where you spend most of your time.

Result. What happened because of your actions? Use numbers when you can. End on a high note.

Every story you tell in an interview should fit this structure. Pull stories from your Proof Bank (the one you started in Part 2) and run them through STAR until you have five to seven polished stories you can deploy for almost any behavioral question.

One rule. A great STAR answer takes 90 seconds to 2 minutes. Anything longer, you lose the interviewer. Anything shorter, you don’t give them enough. Time yourself. Practice. This is a muscle.

What makes a great interview answer actually feel great

Here’s a thing nobody tells you about Implementation Manager interviews. The hiring manager isn’t just listening to what you said. They’re feeling how you said it. Calm or jittery. Confident or apologetic. Curious or transactional. By the end of a 45-minute conversation, what they actually remember is the feel of you, not the words.

Four things make an answer feel great to a hiring manager.

Specificity

Vague answers feel rehearsed. Specific ones feel real. The difference between ‘I led a team’ and ‘I led a team of seven through a six-week migration that went live on a Friday at 4 PM’ is night and day. The numbers and the texture are what makes the hiring manager lean in.

Calm pacing

Nervous candidates rush. They want to get through the answer. The calmer you can be — even adding a one-beat pause before you start — the more senior you sound. Speed is the tell that you don’t fully trust your own answer. Slow down on purpose.

Self-credit without self-importance

Say ‘I’ when you mean I. Say ‘we’ only when the team genuinely shared the work. Most candidates default to ‘we’ because they were taught it sounds humble. It actually sounds like they didn’t do anything. Own your role, and the hiring manager will believe you did the work.

Curiosity at the end

Strong candidates finish a story and naturally ask a follow-up question to the interviewer. ‘Does that match what you’d expect a new IM to do here?’ It signals you’re thinking about the role, not just performing for the interview. Even one moment of genuine curiosity makes you feel like a colleague, not a candidate.

The questions you will almost certainly be asked

Implementation Manager interviews recycle the same core questions across companies, recruiters, and panel rounds. I’m going to share three of them here. The other four — including the deeper de-escalation and end-to-end project questions — are inside the playbook with full sample answers.

“Tell me about a project you managed from start to finish.”

What they’re really asking: Can you actually own something end-to-end? If you don’t have a formal PM title, do not apologize. Pick a non-PM project where you owned the outcome. Open with one sentence of context, walk through the arc using STAR, end with a concrete result. Do not use the word ‘we’ more than twice. This is your story, not your team’s.

“Walk me through how you’d approach a brand new customer implementation on day one.”

What they’re really asking: How do you think? They don’t expect you to know their specific process. They want to see you have a framework. Structure your answer around three phases. Discovery (who are the stakeholders, what does success look like, what are the risks). Planning (what’s the timeline, what are the milestones, where are the dependencies). Execution (how do you stay close to the customer, how do you escalate blockers, how do you measure progress). You don’t need to know their product. You need to show you have a process.

“You don’t have a PMP or a formal Project Manager title. Why should we hire you for this role?”

This is the one that intimidates everyone. It shouldn’t. They’re not trying to trip you up. They’re giving you the chance to address the obvious concern directly. If you don’t answer it well, they’ll decide for you. If you answer it well, you remove their biggest hesitation.

Do not be defensive. Acknowledge the gap, then reframe. ‘You’re right, I don’t have the title on paper. But here’s what I have done.’ Then list three concrete pieces of evidence that you’ve done the work. End with why you specifically fit this role. Confidence, not apology.

Then you get the offer. Now what?

Let me say something that surprises people. Landing the role is only half the battle. The first 90 days determine whether you keep it, whether you get promoted, and whether you build the kind of reputation that compounds over your whole career.

Most people walk in their first day intimidated. They sit quietly. They try to absorb everything. They try not to make mistakes. And without realizing it, they spend their first 90 days being invisible — which is the worst thing you can be in a new role.

Here’s a different approach. Walk in with a plan.

The first 90 days break down into three distinct phases, each with its own job.

Days 1–30 is the listen-and-learn phase.

Your job is to absorb, not impress. The people who try to prove themselves in month one almost always overplay their hand. The people who resist that urge outperform everyone who tried.

Days 31–60 is the first-win phase.

By day thirty, you should be ready to own something visible and finish it well. One specific, focused win matters more than broad effort. Reputation is built on a single signature move, not on being average at ten things.

Days 61–90 is the position phase.

By day sixty you’re past the ramp. This is the moment most people relax — and the moment you should quietly start acting one level up.

That’s the philosophy. The execution — the printable 30/60/90 Template with the action checklists for each phase, the reflection prompts you run at the end of each month, and the day-90 review — is inside the Toolkit Bundle tier of the playbook. Print it. Stick it where you can see it. The framework above teaches the why. The template makes you actually run it.

FROM THE TOOLKIT BUNDLE

Want the printable 30/60/90 Template with the full action checklist for each phase, the reflection prompts, and the day-90 review? Plus the other four interview questions with full sample answers, plus the questions YOU should ask the interviewer? The Toolkit Bundle tier of The Implementation Manager Playbook ($67 inThe Rich Life Vault) has everything.

What comes after this series

This is the last post in the PM Pivot Series. But it’s not the end of this conversation. Over the next few months I’ll be publishing follow-ups based on what’s actually coming up in my DMs — clinical staff who want to pivot, women negotiating their first IM salary, and the eventual ‘should I get a PMP?’ conversation.

If you want to make sure you don’t miss any of it, subscribe to The Rich List. Career posts hit that list first, plus the behind-the-scenes of how I’m building Rich Out Loud while still doing the day job.

The Rich Out Loud truth

Five posts ago, you might have thought you were underqualified, that you’d missed your window, that PM was a closed club for people with the right credentials.

None of that was ever true.

You were always qualified. You just needed the language, the lane, the plan, and the playbook. You have all four now.

The next move is yours. Go apply. Go pitch. Go interview. Go land the role. And when you do — and I mean when, not if — please come back and tell me. I want to celebrate with you.

Now go live your richest life and we’ll chat again soon 💋