The first version asked whether you could use AI tools. The second version asks whether you build repeatable systems with them, whether you're improving, and whether you catch errors before they ship.

Four dimensions: mindset, strategy, building, accountability. That last one is new and it's pointed. "With AI, you can delegate the work, but not the accountability."

The shift that matters most is from snapshot to slope. V2 measures the trajectory of someone's fluency, not where they are today. Hiring for growth rate.

It's already showing up in interview loops. Google, Figma, and Perplexity now run 45-minute "vibe coding" rounds where PM candidates build working prototypes with tools like Cursor. Not a whiteboard exercise. Not a take-home. Live building, observed in real time.

Adriane Schwager added necessary context: the floor has moved in tech, but it hasn't moved everywhere. A workflow Zapier now rejects as insufficient would be considered advanced at most accounting firms and small agencies. That asymmetry is an opportunity if you see it clearly.

Last week I wrote about building a customer dashboard over a weekend that changed how 200 people think about accounts. This week I read about the same instinct playing out across hiring, infrastructure, and knowledge systems. The pattern is the same: the people who build with AI are pulling ahead of the people who use AI.

I wrote up everything I read this week in the first edition of Foraging, my new reading digest. Link in comments.