--- title: "Hot Takes on Hiring: \"AI Fluency\" Is a Myth | CoderPad" description: "Learn more about Hot Takes on Hiring: \"AI Fluency\" Is a Myth from CoderPad." canonical: "https://coderpad.io/blog/hiring-developers/hot-takes-on-hiring-ai-fluency-is-a-myth/" last_modified: "2026-08-21 08:42:29" --- [Back to blog](https://coderpad.io/blog/) # Hot Takes on Hiring: “AI Fluency” Is a Myth August 21, 2026 5 Minute Read [Hiring Developers](https://coderpad.io/blog/hiring-developers/) Our CEO, Amanda Richardson, and our Head of Product, Frank Hauben, can’t agree on anything else. We put [Amanda and Frank on camera](https://coderpad.io/events/hot-takes-on-ai-hiring/), handed them five spicy hot takes about AI in hiring, and told them not to sit on the fence. They sat on the fence anyway. Here’s what they actually fought about. Amanda hires for the next ten years. Frank hires for next Tuesday. Both are right, which is exactly why this is hard. Here are the five fights, and the one thing they finally agreed on. ## 01. Is “AI fluency” a real skill, or a fad we all agreed to take seriously? The take: if you’re measuring how well someone prompts, you’ve already lost the plot. Amanda didn’t hedge: AI fluency isn’t really a thing. In a year we’ll be embarrassed that we treated it as a separate skill, like listing “Microsoft PowerPoint” on a resume as though it were a personality trait. Look at whether a candidate’s actual skills shine through, not whether they’re “good at AI.” Frank took the other side without blinking. It’s the number one thing customers ask about. Not the clean prompt, but whether you understand what context the model even has, how you feed it, and what you know to pull back out. That’s not a party trick, it’s something he wants to hire for. “It’s not yes-and. It’s necessary but not sufficient.” The question underneath: is AI a baseline skill like literacy, or the differentiator between good and great? Nobody would commit. Which is the honest answer. ## 02. Speed is a vanity metric. The take: everyone bragging about moving faster is optimizing the wrong number. Frank’s favorite company value and favorite metric are the same: speed. Speed to prototype, to ship, to get something in front of a real user. If he could optimize one number, that’s it. Amanda’s response: he only says that because he’s faster than me. Then she really dug in – speed is short-term. As models get faster, nobody wins on speed, because everyone has it. You win on good inputs and the right outputs. And then she coined the keeper: “Bot-shitting is real. Just because you can create it fast doesn’t mean it’s good, and just because you can ship it fast doesn’t mean it’s built well, or that it’s even the right thing.” Then she argued against herself: slow because you’re thinking critically? Good. Slow because you’re scared to pick a prototype? Build them all fast and let feedback decide. Frank conceded too: five half-built features is worse than one that’s finished. ## 03. Prompt quality and token usage are noise. The take: the signal isn’t the clean prompt, it’s the result. Rare agreement, sort of. Both think token-counting is a distraction. As Amanda put it, unless you’re the CFO, why do you care? But the token question refuses to die inside a real interview. If two candidates hit the same output and one did it at a fraction of the cost, do you hire the cheaper one? Do you let candidates pick their own model when the pick changes their score? Is model selection a skill, or a constraint we haven’t figured out how to grade? No answers, just a dozen new questions the industry hasn’t solved. ## 04. Rank them: process, output, speed. No fence-sitting. The take: you have to choose. Pick a hierarchy and defend it. Amanda put the process first, output second, speed dead last. Her reasoning is the sharpest idea in the whole conversation, and it’s specifically about hiring: “If you hire on output alone, you’ll miss great candidates who just got lost in the process. If they have a good process, you can coach them to the right output. It’s the McKinsey case study: miss the question at the top of the branch and the whole answer comes out wrong, even though the person is brilliant.” Frank, the self-declared speed evangelist, surprised everyone and ranked output first. His logic: speed was never the goal, it was always speed to output, and output is the thing you actually get paid for. The unlock was the distinction: process wins when you’re hiring, output wins when you’re managing performance. Two jobs, two metrics. Most companies use one yardstick for both and wonder why it doesn’t work. ## 05. Is AI fluency a real skill, or a category we invented to sell things? The take: the last one, and the meanest one. Amanda, who happily admits she’s all about inventing categories and selling things, still called it: AI fluency is the next word processor. Then she declined to fully commit, because plenty of customers are treating AI familiarity as a real culture change. Fence-sitting, and she said so. Then Frank landed it: “Maybe we should just call it a mindset. Then it’s something we can all accept.” And that’s where they met. Not fluency. Not prompting. Mindset. Curiosity, willingness to experiment, willingness to try modern tooling before anyone tells you to. The word will change within months. The thing underneath it won’t. ## So what do you actually do with this? Two aligned leaders at the same company couldn’t agree on how to hire for AI, and they built the platform other companies interview on. If it’s this contested inside CoderPad, it’s a coin flip inside a committee that hasn’t thought about it at all. That’s not a reason to freeze, it’s a reason to be deliberate. The companies getting this right aren’t the ones with the perfect definition of “AI fluency.” They’re the ones who decided what they value, built an interview that tests for it, and stopped guessing. Choose on purpose, not by accident. ## Stop guessing what AI-native talent looks like. Ask the people who measure it. Book a 15-minute call with a CoderPad AI hiring consultant. Bring a role you’re hiring for. We’ll help you pin down what to test for, what a good process looks like, and how to spot the mindset that separates AI-native from AI-curious. [Book your 15-minute call](https://coderpad.io/sales/) ## Subscribe for more CoderPad insights ## Trending Articles Previous slide Next slide [Hiring Developers ## How to Hire for AI Fluency Now That It’s a Critical Skill Based on the CoderPad webinar featuring Bayo Ojuri (CoderPad), Bonnie Dilber (Zapier), and Melany Austin (GoDaddy). “AI fluency” has quietly become a line item in nearly every technical job description. The problem: most teams added the requirement long before they had a reliable way to assess it. You can ask a candidate whether they use […] Read the post](https://coderpad.io/blog/hiring-developers/how-to-hire-for-ai-fluency-now-that-its-a-critical-skill/) [Hiring Developers ## 5 Unfiltered Takes on AI That Engineering Leaders Actually Believe We put a room full of senior engineering leaders together, took away the slides, added beer, and asked them to say the thing they’d never put in a LinkedIn post. No PR-approved talking points, no vendor gloss, just people who ship for a living telling the truth about what AI is doing inside their orgs […] Read the post](https://coderpad.io/blog/hiring-developers/5-unfiltered-takes-on-ai-that-engineering-leaders-actually-believe/) [Hiring Developers ## Your Developer Interview Loop Is a Year Old. Is It Still Finding Your Best Candidates? A YC-backed founder called me last week with some good questions. His 20-person startup hadn’t hired an engineer in over a year. Now they’re opening reqs again, and instead of just dusting off the old loop, he wanted to understand how interviews had changed and if candidates were ready for AI interviews. His process — […] Read the post](https://coderpad.io/blog/hiring-developers/your-developer-interview-loop-is-a-year-old-is-it-still-finding-your-best-candidates/) [Hiring Developers ## AI Fluency Is the New Technical Skill. Is Your Hiring Process Ready? Artificial intelligence has fundamentally changed software development. Developers are no longer working in isolation, writing every line of code from memory. AI has become part of the engineering workflow, helping developers brainstorm approaches, generate boilerplate code, and debug complex issues. The question isn’t whether engineers are using AI. It’s how effectively they’re using it. Hiring […] Read the post](https://coderpad.io/blog/hiring-developers/ai-fluency-is-the-new-technical-skill-is-your-hiring-process-ready/) [Hiring Developers ## AI Didn’t Kill Entry Level Hiring. Bad Screening Did. For the last two years, the narrative has been loud, confident, and mostly wrong: AI is coming for entry level engineering jobs. The story goes something like this: If AI can write code, summarize docs, generate tests, and debug basic issues, why would companies still hire junior engineers? It sounds logical. It is also incomplete. […] Read the post](https://coderpad.io/blog/hiring-developers/ai-didnt-kill-entry-level-hiring-bad-screening-did/) [Hiring Developers ## The Resume Is Dead. Most Teams Just Haven’t Admitted It Yet. Resumes made sense when applying for a job took real effort. That era is over. AI lets candidates apply to hundreds of roles in the time it once took to write a single cover letter. Employer-side AI systems process the flood. The result is a hiring funnel built almost entirely on artificial signals, where the […] Read the post](https://coderpad.io/blog/hiring-developers/the-resume-is-dead-most-teams-just-havent-admitted-it-yet/) [Hiring Developers ## Is Your Technical Hiring Process Screening Out Great Engineers? The short answer: Many technical hiring processes are doing the latter. High-friction interview loops, live coding under observation, and AI-restrictive assessments are measuring interview performance, not job performance. The fix isn’t rebuilding from scratch — it’s auditing whether your process measures engineering capability or something else entirely. If you attended our recent webinar with CoderPad […] Read the post](https://coderpad.io/blog/hiring-developers/is-your-technical-hiring-process-screening-out-great-engineers/) [Hiring Developers ## Junior Developers Are Your Strategic Advantage—If You Can Actually Evaluate Them Campus recruiting season arrives the same way every year: hundreds of applications, a narrow window, and a process that was never designed for this much volume or this much pressure. Meanwhile, the definition of “technical skill” is actively shifting—AI-polished resumes have made traditional screening nearly meaningless, and the skills that predict junior developer success look […] Read the post](https://coderpad.io/blog/hiring-developers/junior-developers-are-your-strategic-advantage-if-you-can-actually-evaluate-them/) [Hiring Developers ## Your Hiring Process Is Losing You Top Talent. Before They Ever Interview! Here’s a hard truth most TA leaders don’t want to admit: your hiring process is screening for the wrong thing. Not skills. Not judgment. Not potential. It’s screening for the ability to interview well. And those two things have almost nothing to do with each other. We sat down with recruiting experts Cammas Freeman, Phil […] Read the post](https://coderpad.io/blog/hiring-developers/your-hiring-process-is-losing-you-top-talent-before-they-ever-interview/) [Hiring Developers ## CoderPad Uses CoderPad to Hire Engineers. Here’s How. When we opened our latest software engineer role, we had 100 applications within 24 hours. By the end of the first week, without running a single ad, we had 160 candidates in the pipeline. That’s a lot of signal to sort through. And it forced us to be honest about something every engineering leader eventually […] Read the post](https://coderpad.io/blog/hiring-developers/coderpad-uses-coderpad-to-hire-engineers-heres-how/) [Hiring Developers ## Is Your Technical Hiring Process Built for the AI Era? Find Out With a New Quiz. AI didn’t just change how engineers build software. It changed what it means to hire one. The tools engineers use every day — AI coding assistants, prompt-driven debugging, multi-model workflows — are now fundamental to how modern development teams operate. According to our State of Tech Hiring 2026 Report, 82% of developers find generative AI […] Read the post](https://coderpad.io/blog/hiring-developers/is-your-technical-hiring-process-built-for-the-ai-era-find-out-with-a-new-quiz/) [Hiring Developers ## In the AI Era, Shopify Is Investing in Junior Engineers—Not Cutting Them We spoke with Farhan Thawar, VP and Head of Engineering at Shopify, about why the company 10x’d its internship program, what AI-native hiring really looks like, and the three-part framework reshaping how technical talent gets evaluated. The conventional wisdom goes something like this: AI is coming for developers, and the first casualties will be the […] Read the post](https://coderpad.io/blog/hiring-developers/in-the-ai-era-shopify-is-investing-in-junior-engineers-not-cutting-them/) ## Hire with confidence. See why engineering teams trust CoderPad to evaluate developers with realistic, AI-ready hiring workflows. [Request a demo](https://coderpad.io/sales/)