Resume said 8 years experience. Interview was flawless. Three months in, team was rewriting everything.
We're still hiring for skills AI already handles and ignoring the one it can't: how someone actually works with it.
Builders, Assemble. 🛡️
If you're shipping with AI agents, building dev tools, or just figuring it out in public, I want you in my timeline.
Drop what you're building 👇
Your team has AI in every editor and output barely moved. The standup, sprint planning, and review process look identical to 2019. The tool changed but nobody redesigned how the work actually flows.
Your hiring process still grades the final code. AI wrote half of it. The devs who actually perform decompose the problem before they ever touch a prompt. Grade that instead.
300 Cursor licenses and zero productivity change. The workflow never moved. AI-native teams don't happen by decree. They happen when you measure where the process breaks and actually fix it.
We benchmarked hundreds of developers working with AI coding agents. Problem decomposition is the single biggest predictor of output quality. Most devs jump straight to prompting without breaking the problem down first.
@benkimbuilds@fdotinc@speedrun@GreylockVC@sequoia Hi there, I’m building AgenticRank, an AI Performance Platform.
we make performance with AI tools, visible, measurable, and improvable. so teams can take better decisions for hiring and investing on talent development.
I’m significantly older than you. I started coding in the late 60s. My current strategy is to not read any of the code written by my agents. That’s the only way I can take advantage of their productivity. What I do instead is to surround the agents with extreme constraints. Unit tests, gherkin tests, QA procedures, quality metrics, mutation testing, test coverage, and a plethora of others. In the end, I have very high confidence in the code they produce because they’ve had to run the gauntlet of all of my constraints and tests.