• LinkedIn
• Twitter
• Instagram
• YouTube
• RSS Feed

Apple •Spotify• Pocket Casts •Youtube •Overcast •RSS

What’s up everyone, today we conclude our 3 part series we’re calling The Martech Job Hunt Survival Guide.

• Part 1: Find hidden job opportunities
• Part 2: Stand out from the AI crowd
• Part 3: (you are here) How to interview a company before you say yes

Summary: Darrell shares a firsthand account of taking a job under financial pressure, ignoring red flags he recognized in the moment, and landing in a toxic environment within months. What follows is a structured set of interview questions across 6 categories, from leadership self-awareness to what happened to the last person in the role, designed to help you separate the job offer from the job reality.

In this Episode…

• What to Figure Out Before You Ask a Single Interview Question
• How to Test a Hiring Manager’s Self-Awareness in a Single Question
• How to Find Out If a Hiring Manager Can Handle Being Wrong
• Why “When Did You Last Take a Vacation?” Is the Most Revealing Culture Question
• How to Find Out If a Company Sticks to Its Priorities or Changes Them Every Quarter
• How to Find Out What a Marketing Ops Role Actually Requires Before You Accept It
• Why Fear in a Peer Interview Is the Red Flag You Should Never Ignore

What to Figure Out Before You Ask a Single Interview Question

The US healthcare system has a way of making bad career decisions feel necessary. When you’re laid off with a family depending on employer-sponsored coverage, the clock starts immediately. Every week without an offer is another week closer to COBRA. That pressure doesn’t make people irrational. It makes the math of a job offer feel different than it normally would.

Darrell Alfonso was in that position last year. A few months after getting laid off, he received what looked like a career comeback: a higher title, more responsibility, better pay, and benefits. The package was attractive enough that he pushed aside doubts surfacing during the process. He knew some things felt off. He took the job anyway. Within 2 months, he was having near-anxiety attacks, sleeping poorly, and barely present with his family. He left quickly. He has no regrets.

“I ended up in a very toxic environment. It made me viscerally realize that there are some places, regardless of how much you’re getting paid, it’s not worth it. I wasn’t present with my family. I was having almost anxiety attacks. I wasn’t sleeping. That’s not worth it.”

Most interview prep points in a single direction: getting the offer. Candidates research companies, rehearse answers, and practice looking calm under pressure. The harder question, whether the offer is worth taking, gets almost no airtime. Phil frames this episode as being for people with enough options to ask both. That might mean multiple offers in play, the ability to keep searching while still employed, or simply enough runway to be selective. If you’re in survival mode, some of this will still apply. But the questions work best when you have the leverage to actually act on the answers you get.

Before choosing which questions to ask, decide what you’re trying to find out. Phil and Darrell use what makes you happy at work as the starting filter. For some people it’s ownership and interesting problems. For others it’s stability, predictable hours, or family-friendly flexibility. Darrell puts the manager relationship at the top. Your boss marks your performance, sets your priorities, and shapes whether it feels safe to admit you’re stuck or struggling. Career advice tends to understate how much that single variable determines whether someone thrives or burns out, regardless of how strong everything else looks on paper. The candidates who ask the sharpest questions are usually the ones who did that harder internal work first.

Key takeaway: Before your next round of interviews, write down 3 things that would make you miserable in a role. Be specific: not “bad culture” but things like “a boss who overrides my work constantly” or “no flexibility on hours.” Use that list as your filter when deciding which questions to prioritize. If a company can’t answer those 3 things in a way that gives you confidence, the decision gets harder than it needs to be.

Back to the top ⬆️

How to Test a Hiring Manager’s Self-Awareness in a Single Question

The most common reason people leave jobs is their manager. That gets cited often but rarely changes how candidates behave in interviews. Most people assess for chemistry from the vibe of the conversation, look for red flags in the standard answers, and hope the hiring manager turns out to be reasonable. Phil uses a more deliberate approach.

His bank of questions for probing leadership self-awareness:

• What’s something leadership got wrong in the last year?
• What feedback do you get most often as a hiring manager?
• What decision would you revisit if you could?
• What’s changed about how you lead over time?
• What’s something you’re still figuring out about your leadership style?

The first 1 does the most work. Every leadership team makes mistakes. If a hiring manager can’t name 1, they’re either hiding something or genuinely can’t reflect on their own decisions. The answer that matters isn’t the mistake itself. It’s whether they can describe it clearly, explain what they took from it, and say what changed.

Darrell pushes the same idea with a different angle: ask what issues a hiring manager has had with a former leader, or with a former direct report. If the answer sounds carefully managed, nothing too specific, nothing too negative, that polish is informative. People who have actually led teams through difficult stretches can name them. They have timelines, outcomes, and lessons. Vague answers suggest either limited experience or a preference for impression management over honesty.

“People who’ve been doing this for a while know that leadership, plus people management, plus trying to get a team on the right track, is incredibly hard, specifically because of people issues. If the hiring manager can’t articulate those kinds of things, that’s a really big red flag.”

Phil’s version of the final question in this category is direct: describe your worst boss ever, and why were they the worst? A hiring manager who answers with a real story, including what it cost their team and how they changed as a result, is giving you the most reliable signal available in a 30-minute conversation. Darrell used a version of this in a recent interview. He was upfront with his prospective boss about coming from a toxic environment. She responded by citing 2 specific bosses who had made her professional life difficult, described what each 1 got wrong, and connected it to how she tries to lead now. That answer built more confidence than the rest of the process combined.

Leadership self-awareness is a practice developed through confronting moments where instincts were wrong and the team paid for it. The managers worth working for have had those moments and can talk about them specifically. The ones who can’t usually haven’t processed them.

Key takeaway: Ask your next hiring manager: “What’s something leadership got wrong in the last year?” Write down the answer verbatim as soon as the conversation ends. If the response is vague, hedged, or completely absent, you now have a data point that no amount of external research could give you. The managers worth working for have made real mistakes and can describe them specifically.

Back to the top ⬆️

How to Find Out If a Hiring Manager Can Handle Being Wrong

There’s a version of leadership that gets tolerated more than it should: the manager who hires people with deep expertise and then ignores them. The org chart implies delegation. The day-to-day contradicts it. You spend months delivering work that gets overridden by someone who hired you for your judgment and then second-guesses every call you make.

Phil’s set of questions for this goes directly at the pattern. Rather than asking whether a hiring manager is open to feedback in the abstract, ask for a specific instance: can you describe a time when someone on your team pushed back on your direction? What happened, and what was the outcome? The abstract answer to “are you open to disagreement?” is always yes. Asking for a specific instance surfaces the actual dynamic. Follow-ups that tighten the signal:

• How do you give feedback when things aren’t going well?
• What does a hard week look like for this team?
• Tell me about a time your team disagreed with your idea and took it in a different direction.

Darrell’s view: when his teams have pushed back on his ideas and taken a different approach, he’s gone with them. It requires evaluating evidence without bringing your own attachment to the decision, and genuinely asking yourself why you’re so married to your original idea. A good leader asked about this would have at least 1 story where they say, honestly, that the team was right and they were wrong.

“Real leaders will pick someone and say: this person is way better than me at this. Executives should operate with a ‘who, not how’ approach. Pick the best people to get the job done, and don’t tell them how to do it.”

If the interview process includes time with someone at the C-level or a founder, Phil recommends a question that opens an unexpected window: who is your best employee, and why? A leader who struggles to name anyone, and eventually lands on the person who works 17-hour days and never says no, is telling you what they value. A leader who names several people for different reasons, with specific contributions in mind, is demonstrating something more useful than leadership vocabulary.

Darrell connects this to a principle: executives worth working for operate with a “who, not how” mindset. Their job is to pick the best people for the work, then get out of the way. If you can’t get a sense from your conversation that the leader you’re talking to is genuinely comfortable with people on their team knowing more than they do, that gap in the interview will widen once you’re inside the organization.

Key takeaway: In your next interview, ask the hiring manager to describe a time their team pushed back on their direction and what happened. Listen for specifics: a team name, a project, an outcome. Then ask the same question to a peer or someone else on the team and compare the answers. The gap between what a manager says happened and what the team remembers is where you learn what kind of leader they actually are.

Back to the top ⬆️

Why “When Did You Last Take a Vacation?” Is the Most Revealing Culture Question

Culture assessments in job interviews tend to surface the most rehearsed version of a workplace. Everyone says they’re collaborative. Everyone says they value work-life balance. None of it is exactly a lie. It’s the version of the truth that gets offered during hiring. 1 question cuts through that faster than almost anything else.

Phil’s go-to: when was the last time you took a vacation? Ask it of the hiring manager, and if you get time with someone higher up, ask them too. The answer matters less than the reaction. A manager who says “I love vacation, I actively encourage my team to take time off” and then mentions they haven’t taken a week off in 2 years is telling you something no culture deck would include. Teams learn what the real policy is by watching what leadership does, not by reading what the company says.

“If someone says ‘I’m a big fan of vacation and I tell my team to take vacation, but I haven’t taken one in two years,’ that’s a red flag. If you don’t lead by example, no one on your team feels safe taking a vacation. It comes from the top down.”

A companion question that tends to get skipped: how many people on the team have kids? It sounds informal. Phil argues it’s 1 of the most specific probes available for understanding whether the company has built flexibility into its culture or just tolerates it case by case. A founding team and leadership chain without children, operating in startup mode, will set different defaults around flexibility than a team where most people are navigating school pickups and daycare. The difference shows up in unspoken expectations that won’t be in any offer letter.

Darrell adds the flip side: when a company is upfront about demanding hours, you have to be honest with yourself about whether you can actually sustain that long-term. He turned down 1 opportunity after learning that evening calls across time zones would be standard. His current role requires consistent 7 AM meetings. He agreed to it knowingly. It’s not his favorite part of the job. But he chose it with clear information, and that makes all the difference.

Phil’s former boss shared a set of questions for this category worth adding to any list:

• If I take this role and we’re doing a review in a year, what would make you say I exceeded expectations?
• What keeps you up at night about this role?
• If you could wave a magic wand and change anything about the company, what would it be?
• If you had dedicated resources to hire, what would you want and why?

These questions do double duty. They surface concerns the hiring manager hasn’t said out loud, and they open space for the kind of honest conversation that most interview structures aren’t designed to have. The way someone answers the magic wand question, how quickly they name something and how specific they are, tells you whether they have a clear sense of what’s actually holding the company back.

Key takeaway: Ask every hiring manager when they last took a vacation, and ask the team separately. If the stated culture is “we encourage time off” but no 1 in leadership has actually taken any, you now know which 1 is real. Then ask yourself honestly whether the working hours they describe are hours you can sustain for more than 6 months.

Back to the top ⬆️

How to Find Out If a Company Sticks to Its Priorities or Changes Them Every Quarter

Nothing burns out a marketing ops team faster than chronic priority shifting. You spend 3 weeks building out a lead scoring model, a founder has a conversation with a sales leader, and the project quietly disappears. You start over. The team learns not to invest too deeply in anything, because nothing has a real commitment horizon.

Phil’s questions for probing decision stability:

• Can you walk me through the last time priorities changed mid-quarter and what drove that change?
• How do decisions get reversed here, and how is that communicated?
• What happens when leadership disagrees with what the team wants to do?
• How do you handle conflicting priorities between projects or stakeholders?

Change at most companies is constant, especially now with AI reshaping entire workflows mid-year. Phil wants to understand the framework behind it: whether decisions move through OKRs, a product roadmap, or a defined process, or whether direction mostly comes from whoever pushed hardest in the last executive meeting. The companies worth joining can articulate the difference.

“A great manager makes their team feel mentally safe. I’m not going to come to them tomorrow and say the priority I gave them last month is gone because the founder said to pull the plug.”

Phil uses the phrase “cover fire” for what he wants in a manager. A great hiring manager runs interference for their team. They fight for the roadmap they committed to. They say no to inbound requests that conflict with what the team is currently focused on. They make it safe to go deep on a problem without worrying it will get cancelled before it’s finished. The opposite is a manager who comes back from every executive meeting with a new direction and an apology.

Darrell adds a practical angle: ask how the company communicates major change. A team meeting with context, the reason for the shift, the implications for current work, and time to process is a reasonable standard. The worst version he’s seen is leadership deciding behind closed doors, telling a handful of people, and expecting everyone else to absorb it somehow. A hiring manager who has never thought about their communication process around change is giving you a preview of what happens when priorities inevitably shift.

Key takeaway: Ask your hiring manager to walk you through the last time priorities changed mid-quarter. Ask what drove the change and how it was communicated to the team. Then ask a peer or team member the same question separately. If the answers don’t align, or if nobody can point to a clear process for how those decisions get made and shared, you have a preview of what your first 6 months will feel like.

Back to the top ⬆️

Demand & Expand 2026

Join the world’s best B2B marketers for 2 full days of tactical content, in-depth sessions, and meaningful connections. Use HOM20 at checkout 

How to Find Out What a Marketing Ops Role Actually Requires Before You Accept It

Marketing ops job descriptions have a specific inflation problem. The role gets posted as a strategic hire, the interview process treats the candidate as transformative, and the onboarding reality is a queue of tickets and a list of integrations that stopped working months ago. Phil and Ronald Gaines from Sunbelt Rentals have spoken about this pattern directly: marketing ops people get hired as saviors. They’re told they’re going to be celebrated. And then week 1 looks a lot like a helpdesk with a fancier job title.

The questions that cut through the job description:

• What does success look like at 30, 60, and 90 days?
• If I take this role and we’re reviewing my year, what would make you say I exceeded expectations?
• What will still be broken after 6 months that you’re not expecting me to fix?
• What authority does this role actually have to make changes?

That last question is where the real conversation happens. When someone says they “own marketing analytics,” there are 2 very different jobs hiding under that phrase. 1 version means owning the tickets to fix the dashboards. The other means owning the strategy for how analytics decisions get made across the org. Those are different roles, and the job description rarely distinguishes between them.

“If everyone on the team is saying ‘our lead routing is broken, sales is complaining,’ but the hiring manager is talking about AI-powered propensity models, you’re already seeing misalignment right off the bat.”

Phil adds another layer: ask “what keeps you up at night about the work that needs to get done” to the hiring manager, then ask the team the same thing separately. Compare the answers. If both sides name the same problems, you have at least a signal of shared understanding about what actually needs fixing. If the hiring manager is describing an AI transformation agenda and everyone on the team mentions broken lead routing that sales has complained about for months, you’ve just witnessed a misalignment before your first day.

Darrell points out that company size shapes what any of this means. Larger, more mature organizations tend to have more defined marketing ops scope and clearer expectations. Smaller companies often don’t. That tradeoff is real, and worth naming in the interview itself. He shared upfront with his current boss the things he doesn’t do: copy, design, branding. She appreciated the directness. In a market where candidates say yes to everything just to stay in the process, being specific about your scope is a differentiator worth trying.

Key takeaway: Ask your hiring manager what authority the role actually has to make changes, then compare that answer to what the team says is broken and why. If the list of what needs fixing is long and the actual mandate to fix it is vague, you have a preview of the role’s real scope. Use the 30/60/90 question and the “what will still be broken after 6 months” question in every marketing ops interview.

Back to the top ⬆️

Why Fear in a Peer Interview Is the Red Flag You Should Never Ignore

The question most candidates avoid is the 1 about the last person in the role. Why is this job open? Did they leave voluntarily? Were they pushed out? Were they overworked until they couldn’t take it anymore? It feels awkward to ask directly, but it opens access to information the rest of the process is structured to keep surface-level.

Phil goes at it directly: why did that person leave, and what would they say was hardest about the role? Darrell’s more useful framing: what do you wish the person in this role had done differently, and what do you wish you could have worked with them better on? These questions are harder to deflect, because they put the responsibility on the manager to reflect rather than evaluate. Honest answers tend to come out of that framing more often than direct ones do.

“The really big red flag is if, when you interview with tangential peers, you detect any type of fear or worry in them. If they seem stressed and tense, you’re likely going to feel that too when you come on. Before I joined the place that wasn’t a great fit, I saw those signals when I interviewed. And I ignored it.”

The most reliable signal in this category doesn’t come from the hiring manager at all. It comes from the people you meet during the process who have no stake in selling you on the role. Read the room in every interaction: the peer interview, the cross-functional intro call, the informal meeting with a potential team member. Watch how people carry themselves. Body language and baseline energy are harder to perform than rehearsed answers. Darrell made this mistake in the process for the role that turned out to be toxic. He noticed stress and tension in the people he met. He decided things would improve once he arrived. They didn’t.

Phil has used the backdoor approach once. He had gotten inconsistent answers about why the previous person had left, different stories from different people in the process. He tracked down that person on LinkedIn and reached out directly. She was candid: the founding team was running the company in ways that made the environment unsustainable. He passed on the offer. They’re still in touch.

Phil and Darrell both acknowledge the backdoor approach works best from a position of strength: multiple offers in play, or the ability to keep searching without financial pressure. If you’ve been out of work for months and need to land something, the calculus looks different, and neither of them pretends otherwise. But for anyone sitting on a yellow flag with enough runway to investigate it, finding a former employee and asking for 10 minutes is worth trying. Formal interview processes are designed to produce a hire. Finding someone who already lived through the role gives you the view from the other direction.

Key takeaway: When you receive an offer for a role that replaced someone, track down the previous person on LinkedIn and ask for 10 minutes. Ask what they found most challenging about the role and listen to how they answer. If the interview process has given you yellow flags and you have the runway to investigate, that conversation is worth more than anything the formal process will tell you.

Back to the top ⬆️

Episode Recap

This episode starts with an honest admission: the whole conversation operates with a certain amount of privilege built in. Darrell took a job under financial pressure because health insurance and a higher title made the math feel different than it should have. He recognized red flags during the process and minimized them because he needed the offer. The framework in the rest of the episode, a structured set of questions across 6 categories, works best when you have options: multiple offers, the ability to keep searching while still employed, or simply enough runway to act on what the answers tell you. Phil and Darrell name that constraint early and return to it throughout.

The organizing principle before any of the questions is self-knowledge. Phil and Darrell reference the “50 Operators Share the Systems That Keep Them Happy” series, episodes 205 to 207, as a starting point for the kind of reflection that should precede any interview. What actually makes you happy at work is specific to each person: ownership and interesting problems for some, stability and predictable hours for others, the quality of the manager relationship for most. That filter determines which of the 6 question categories matters most to your situation, and which questions within each category deserve the limited time you have.

The 6 categories cover: leadership self-awareness (can your hiring manager reflect on their own mistakes?), manager style under disagreement (what happens when someone pushes back?), culture and working hours (when did they last take a vacation?), decision stability (how do priorities change and who communicates that?), role reality versus job description (what authority does the role actually have?), and the last person in the role (what does the pattern of departures actually tell you?). Each category includes specific questions and, more importantly, specific signals to listen for. A vague answer to “what’s something leadership got wrong last year” tells you as much as a detailed 1.

1 honest thread runs through the episode: some of what Phil and Darrell recommend is much easier to act on from a position of relative safety. Reaching out to former employees, pushing back when answers don’t align, walking away from a yellow flag — these are easier choices when you have another offer on the table. Darrell took a job he knew something was wrong with because the financial pressure made the math feel different. That honesty is what gives the rest of the episode its credibility.

Listen to the full episode for Phil and Darrell’s complete breakdown of each question category, including the specific follow-ups that produce the most useful answers and the real-time signals, in peer interviews and cross-functional meetings, that matter more than what anyone says out loud.

Full episode ⬇️ or Back to the top ⬆️

• Part 1: Find hidden job opportunities
• Part 2: Stand out from the AI crowd
• Part 3: (you are here) How to interview a company before you say yes

✌️

—
Intro music by Wowa via Unminus
Cover art created with Midjourney (check out how)

Apple •Spotify• Pocket Casts •Youtube •Overcast •RSS

Related tags

See all episodes

Future-proofing the humans behind the tech

Apple •Pocket Casts•Google •Overcast •Spotify •Breaker •Castro •RSS

• LinkedIn
• Twitter
• Instagram
• YouTube
• RSS Feed