Two scoring systems. One conclusion. If a company can't talk about customer relationships in a job description, they're not building a CS function — they're building an automation workflow with a human placeholder.
Paste the full job posting or your internal job description. The scorer reads how the company talks about relationships vs. processes — and returns a displacement risk score, rationale, and the specific signals it found in the text.
Paste any CS job description — your current role or that job you're checking out.
No spam. Just the scorer + March 25 session details.
Andrej Karpathy scored 342 BLS occupations by how much AI will reshape them. That's the macro lens — useful, but blunt. It can't tell you whether this CS role at this company is a real relationship job or a process workflow in disguise. That's what the second lens is for.
Scores every BLS occupation category from 0–10 by how much AI will reshape it. A score above 7 means the work product is fundamentally digital and the trajectory is steep. CS-adjacent BLS categories score high — because BLS still thinks CS is customer service.
Source: karpathy.ai/jobs — BLS Occupational Outlook Handbook, LLM-scored. Scores are approximate for CS-adjacent categories.
Reads the actual job description. How much does the company talk about human judgment, executive relationships, business outcomes, and navigating ambiguity — vs. processes, volume, tooling, and task execution? The ratio is the real displacement signal.
Based on 15+ years of CS org design. See the scorer below.
That single categorization error is why macro AI-exposure data tells an incomplete story for CS professionals. The BLS is measuring the wrong thing.
The real question isn't whether the occupation is exposed. It's whether this specific role, as written, is doing real CS work — or executing an automation-friendly process that a company will eventually hand to an agent. The job description tells you. If you know how to read it.
AI isn't coming for CS. It's coming for the version of CS that was never really CS to begin with. This session covers what that means for your team, your role, and how to build a CS practice that AI makes stronger — not redundant.
Recording available to registered attendees only.