Lenny's Polls

How AI changes hiring

What 150+ product leaders have to say

Data collected April 2026
The tl;dr
of teams still have no clear policy on AI in interviews
43%
Just 7% prohibit AI outright. Another 12% provide tools and evaluate how candidates use them.
How AI is reshaping hiring

What's your policy on candidates using AI during interviews?

We haven't established a clear policy yet
56
43%
Candidates can use AI if they want, but we don't evaluate it specifically
29
22%
We provide AI tools and evaluate how candidates use them
16
12%
Other (please add a comment)
12
9%
We've redesigned exercises to be harder to fake with AI
9
7%
We prohibit AI to assess unassisted ability
9
7%
Most teams haven't picked a stance on candidate AI use. 42.7% admit no clear policy. 12.2% provide tools and evaluate usage. 6.9% prohibit AI outright. The remaining 38% sit in the middle — allowing AI without scoring it, or redesigning exercises. Candidates show up not knowing what's allowed, what's scored, or what counts as cheating. The fastest move isn't a new rubric. It's a one-paragraph policy in the recruiting email before the next loop opens.

What's the single biggest change you've made to your interview process because of AI?

Started evaluating candidates' AI workflows or tool stack in interviews
34
26%
Redesigned take-home assignments so AI use is expected, not hidden
25
19%
We haven't changed our process
24
18%
Shifted weight from technical screens toward judgment and problem-framing
21
16%
Added a live exercise where candidates use AI tools to solve a real problem
17
13%
Other (please add a comment)
9
7%
Cut or shortened steps that AI made obsolete (e.g., coding trivia, rote knowledge checks)
2
2%
Hiring practices haven't caught up to the tools. Only 25.8% evaluate candidates' AI workflows. 18.9% redesigned take-homes to assume AI use. 12.9% added a live AI exercise. 18.2% haven't changed anything. Candidates arrive with AI fluency that didn't exist 18 months ago, but most interview loops still look pre-AI. Pick one stage to redesign before the next req opens. Don't wait for a stable rubric that may never arrive.

How has AI affected your team's headcount relative to output in the past year?

Same team size, significantly more output
44
35%
Smaller team, same or more output
27
21%
Same team size, same output (AI hasn't moved the needle yet)
25
20%
We've grown the team, and AI has amplified that growth
19
15%
We've grown the team, but AI hasn't been a major factor
9
7%
Other (please add a comment)
3
2%
One in five teams is leaner. Most are doing more with the same people. 21.3% have shrunk teams while keeping or growing output. 34.6% kept the same team and produce more. 19.7% say AI hasn't moved the needle. 15.0% grew the team and credit AI. The "leaner" story is real for a fifth of teams; for most others, AI shows up as more output per person, not fewer people. Before approving the next backfill, ask whether AI plus the current team can absorb the work.

What's the biggest hiring mistake you've made (or seen) related to AI?

Haven't made or seen one yet
61
49%
Over-indexed on AI fluency at the expense of domain knowledge
19
15%
Hired someone who talked a big AI game but couldn't deliver
19
15%
Didn't test for AI skills and regretted it later
12
10%
Other (please add a comment)
7
6%
Passed on someone because they lacked AI skills who would have been great
7
6%
Mistakes split evenly between over-indexing and under-indexing on AI. Among teams who made or saw a hiring mistake, 15.2% over-weighted AI fluency at the cost of domain knowledge, 15.2% hired someone who talked a big AI game but couldn't deliver, and 9.6% regretted not testing for AI. AI talk is cheap. Shipped work with AI is the signal. Ask candidates for two things they shipped with AI last month, and what they'd do differently.

How has AI changed the seniority mix you're hiring for?

No real change to our seniority mix
49
38%
We're hiring almost exclusively senior people now
27
21%
We're skewing more senior but still hiring some juniors
27
21%
We're actually finding AI-native juniors more valuable than before
20
16%
Other (please add a comment)
6
5%
The senior tilt is real but not universal. 41.8% skew senior (20.9% almost exclusively, 20.9% mostly). 15.5% find AI-native juniors more valuable than before. 38.0% report no change. Two strategies work: hire seniors who use AI to compress execution, or hire AI-native juniors who ramp faster than old curves predict. The strategy that doesn't work is hiring juniors and assuming they'll pick up AI on the job.

Has AI changed the speed of your hiring process — from posting to signed offer?

About the same
88
70%
Somewhat faster
18
14%
Somewhat slower
8
6%
Significantly slower
7
6%
Significantly faster
5
4%
AI tools haven't made hiring faster yet. 69.8% report no change in time from posting to signed offer. 11.9% say hiring has slowed; 18.3% report any speedup. The same teams reporting large output gains in engineering and product aren't seeing them in their hiring funnel. Added AI evaluation steps, screening against AI-assisted candidates, and the difficulty of telling humans from models are absorbing whatever speed AI screening tools could deliver.
How teams are evaluating AI fluency vs. the hardest parts of hiring in the ai era

Themes from open-ended responses. Click any to see quotes.

How teams are evaluating AI fluency

The hardest parts of hiring in the AI era