From CVs to Verifiable Work Graphs
The CV had a good run. For decades, it served as the default container for professional identity—a neat, linear story of where you’ve been and what you’ve done. Titles, dates, bullet points, maybe a few quantified achievements if you were paying attention. It was simple, portable, and, for a long time, good enough. But somewhere along the way, it started to feel less like a reflection of reality and more like a carefully edited narrative.
Part of the problem is structural. A CV compresses complex, collaborative work into isolated lines. “Led project,” “managed team,” “delivered results.” These phrases say just enough to sound credible but not enough to be meaningfully verifiable. You can’t see the actual work, the context, the trade-offs, or the contributions of others. Everything becomes flattened into a format optimized for scanning rather than understanding.
Digital profiles didn’t fundamentally change this—they just made the CV more visible and slightly more interactive. You can click around, see endorsements, maybe follow links to projects, but the core idea remains the same: a self-reported summary, lightly supported by external signals. Useful, but increasingly insufficient in a world where work itself is more complex, distributed, and traceable than ever.
This is where the idea of a work graph starts to make sense.
Instead of presenting your career as a list, a work graph maps it as a network. Projects connect to collaborators, outputs connect to timelines, contributions connect to outcomes. Rather than saying “I worked on X,” the graph shows how you were part of X—who else was involved, what was produced, how it evolved. It turns static claims into something closer to observable reality.
At first glance, this sounds like a technical upgrade, but it’s actually a shift in how credibility is constructed.
In a CV model, credibility comes from presentation. How well you frame your experience, how recognizable the companies are, how convincingly you describe your impact. In a work graph, credibility comes from linkage. The strength of your position in the network—who you’ve worked with, what you’ve contributed to, how those contributions connect to other validated signals. It’s less about telling your story and more about letting it be inferred.
That doesn’t mean storytelling disappears. It just moves to a different layer. The narrative becomes an interpretation of the graph rather than the graph itself. You can still explain your role, your decisions, your thinking—but it sits on top of something that can be explored independently.
One of the immediate advantages is context. A project isn’t just a line item, it’s an entry point. Someone evaluating your work can trace it outward—see related projects, recurring collaborators, patterns over time. Are you consistently involved in early-stage builds? Do you tend to work across disciplines? Do your projects cluster around certain themes? These are things that are hard to capture in a CV but become visible in a networked view.
Verification also becomes more natural. Instead of asking for references after the fact, the graph itself contains elements of validation. If multiple collaborators are linked to the same project, if outputs are publicly accessible, if timelines align across different profiles, the system starts to reinforce itself. It’s not foolproof, but it raises the cost of misrepresentation significantly.
There’s an interesting side effect here. Work graphs make collaboration more visible, which changes how individual contribution is perceived. In a CV, it’s easy to overemphasize your role because the format isolates you. In a graph, your contribution sits alongside others. That can feel less flattering at first, but it’s arguably more accurate. And over time, patterns of meaningful contribution become easier to spot than isolated claims of leadership or ownership.
Of course, this raises questions about privacy and control. Not all work can or should be fully mapped. Some projects are confidential, some collaborations are sensitive, some contexts don’t translate well into public representation. Any viable work graph system needs to allow for selective visibility—showing enough to establish credibility without exposing everything.
There’s also the question of adoption. CVs persist not because they’re perfect, but because they’re universally understood. Everyone knows how to read one. Work graphs introduce complexity, and with it, a learning curve. For them to gain traction, they need to feel intuitive enough that people can extract value quickly without needing to understand the underlying structure in detail.
Still, the direction seems clear. As more work leaves behind digital traces—code commits, published content, collaborative tools, version histories—the raw material for work graphs is already being generated. The challenge is less about creating data and more about organizing it in a way that reflects reality without overwhelming the viewer.
Over time, the CV may not disappear entirely. It might evolve into a kind of summary layer—a quick snapshot derived from a deeper graph. Something you can still send, still skim, but backed by a richer structure for those who want to look closer.
And that’s probably the real shift. From claims to connections. From summaries to systems. From static documents to living representations of work that continue to evolve as you do.
It’s not just a new format—it’s a different way of thinking about what it means to show what you’ve done.