Most hiring processes obsess over the wrong things. Do they know our project management software? Are they proficient in this specific tool? Meanwhile, the one capability that actually determines whether someone will make your life easier or harder—their ability to solve problems independently—gets a cursory “are you a good problem solver?” question that everyone answers with “yes.”
In this episode, Chip and Gini break down why problem-solving ability should be the primary hiring criterion, especially as AI makes technical skills easier to acquire and offload. The conversation explores why this matters more now than ever: as AI handles tactical execution, the ability to define problems clearly, break them into components, and figure out solutions becomes the differentiator between humans who add value and humans who get replaced.
Chip and Gini discuss how problem-solving cuts across every role, even ones you don’t typically think of as problem-solving positions. Designers facing impossible deadlines, account people navigating last-minute client demands, anyone dealing with the reality that things rarely go according to plan. They all need to be able to figure out how to move forward rather than escalating every obstacle upward.
The episode tackles the mechanics of actually interviewing for this capability. You can’t just ask “are you a good problem solver?”—you need scenario-based questions that reveal how candidates think through challenges. But not hypothetical scenarios you make up; real situations that have happened in your agency. Ask them to walk through how they’ve handled compressed timelines, missing information, conflicting priorities, or last-minute changes in past roles.
Gini shares how her daughter’s school explicitly focuses on humanities and emotional intelligence rather than technical skills, anticipating that AI will reshape what jobs exist. She connects this to Anthropic’s hiring practice of seeking people with humanities degrees who can absorb information, think critically, and demonstrate emotional intelligence rather than just technical proficiency.
The episode concludes with an important reminder: if you hire problem solvers but then micromanage how they solve problems, you’ve wasted the hire. You need to let them solve things their way, even if it’s different from how you’d do it, or you’ll end up with everything back on your plate anyway.
Key takeaways
- Chip Griffin: “The very best hires are folks who are able to figure out how to look at a problem and come up with ideas on how to solve it in ways that are reasonable that they can execute upon to get it solved.”
- Gini Dietrich: “When you think about problem solving, that is one thing that it will be challenging for AI to do, but really important for a human to be able to do. If you can demonstrate that you can solve problems and you know how to hire for people who can solve problems, then all of a sudden you’ve got AI over here doing the tactical work, but you’re doing the high level thinking work.”
- Chip Griffin: “This isn’t about the specifics of the answer, it’s more making sure that they can think through the method and approach. That’s what signals to you that they’re able to break down the challenge into its component parts to make progress.”
- Gini Dietrich: “I don’t wanna hear problems, I wanna hear solutions. That’s training the problem solving mentality. I need you to come to me with the solutions. I’m not gonna be the one who comes up with the solutions. It’s not scalable, it’s exhausting.”
Turn Ideas Into Action
Rewrite your interview questions to focus on real scenarios. Pull up your current interview script and replace skill-testing questions with situation-based ones drawn from actual challenges your team has faced in the past six months. Instead of “Do you know Asana?” ask “Tell me about a time you got an urgent request at 4pm Friday with a Monday deadline. Walk me through your approach.” Spend 30 minutes creating 3-5 scenario questions specific to each role you hire for.
Test whether you’re letting your problem solvers actually solve. Pick the last three times a team member brought you a problem this week. For each one, honestly assess: did you immediately jump in with the solution, or did you ask “how do you think we should handle this?” If you solved more than half yourself, you’re training your team to be dependent rather than autonomous. Next time someone brings you a problem, pause and ask them for proposed solutions before weighing in.
Audit your hiring criteria for trainable vs. essential skills. List the requirements in your most recent job posting and mark each as either “can be trained in 2 weeks” or “fundamental to the role.” Tools, software, specific methodologies—all trainable. Problem-solving, critical thinking, ability to work under ambiguity—essential. If more than 30% of your listed requirements are trainable skills, you’re screening out good problem solvers who could learn your tools in a week.