Boris Cherny, the Father of Claude Code: Five Talent Archetypes for the Future Workplace

Yesterday I came across a really interesting post from Boris Cherny, the father of Claude Code, about how workplace roles are going to change. His perspective is unique — let’s dig into it.

The Boundaries of Traditional Roles Are Fading

Boris noticed a trend: The lines between familiar roles like engineers, product managers, designers, and data scientists are getting blurrier and blurrier. What everyone does is starting to overlap and slowly merge into a new way of working.

This isn’t hard to understand. Think about it: a designer who knows how to use AI tools can now build a prototype on the spot without waiting for an engineer’s sprint. A product manager with a little coding knowledge can run their own data analysis. Tools are getting more powerful, and people’s skill boundaries are expanding. The old division of labor — “you handle design, I handle development” — is genuinely loosening.

Five Talent Archetypes

Using his own Claude Code team as an example, Boris identified five talent archetypes. Note: these aren’t five job titles, but five styles of working and areas of strength.

First: The Explorer. These people always have new ideas. They want to try this today and that tomorrow. They produce a lot of output, but most of their ideas never become formal products. Their value lies in constantly exploring possibilities and helping the team find new directions.

Second: The Builder. Once an Explorer finds a promising direction, the Builder steps in. Their strength is turning a rough idea into a usable, stable product quickly. Execution is their biggest weapon.

Third: The Polisher. The product is built, but it’s often not refined enough. The Polisher cleans up the mess: making the interface more usable, streamlining the code, cutting unnecessary features, and improving performance. They take a product from “it works” to “it works well.”

Fourth: The Grower. The product works well, but do enough users know about it? What does the market say? The Grower owns this. Through round after round of small iterations, they make the product fit real user needs better and boost product-market fit (PMF).

Fifth: The Maintainer. When a product is mature and has a large user base, the Maintainer becomes critical. They ensure the system stays secure, stable, and efficient as it scales. This role may not sound glamorous, but without them, even the best products will collapse under growth.

One Person Can Wear Multiple Hats

Boris specifically noted that many people actually have traits from two or three archetypes. You might be both a decent Builder and a good Polisher. That’s normal — people are complex.

More interestingly, these five archetypes don’t necessarily correlate with your job title. Inside Anthropic, some designers are classic Explorers, while others are more like Polishers. The same goes for engineers — some are great at building new things from scratch, others excel at maintaining existing systems. Data scientists are no different.

This observation is actually quite disruptive. When we look for jobs or build teams, we habitually think “I need a frontend engineer, a backend engineer, and a designer.” But Boris’ point is that maybe the more important question is: Do I need someone who’s great at going from zero to one, or someone who’s great at polishing and optimizing?

Different Product Stages Need Different Combinations

Boris also gave some very practical advice on team composition:

A brand-new product that hasn’t found its market yet needs Explorers, Builders, and Polishers the most. At this stage, the core task is to experiment quickly, build it, polish it, and see if the market bites.

A product that has found its direction and is growing fast needs Builders, Polishers, and Growers as the main force, plus a few Maintainers. The direction is clear — the focus is on making the product better, getting it to more people, and keeping the system from crashing.

A very mature product needs Polishers, Growers, and Maintainers as the core, supplemented by a few Builders. At this stage, there aren’t many big innovations — the key is continuous optimization, stable operation, and meticulous management.

This framework can be applied in many contexts. For example, if you’re starting a company, don’t hire too many people who prefer maintaining the status quo in the early days — you need people who can ship fast and aren’t afraid to experiment. Conversely, if your business is already very stable, don’t fill the team with people who always want to try new things — you need people who can settle down and get the details right.

Some Thoughts on Personal Development

From an individual perspective, this framework is also quite valuable. You can ask yourself: which archetype am I closer to? Am I someone who always has new ideas, or someone who prefers to polish something to perfection? Do I enjoy building from scratch, or do I get more satisfaction from keeping a mature system running well?

Understanding your own tendencies can help you be more targeted when job hunting. If you’re a classic Explorer, joining a very mature company with rigid processes might feel frustrating. Conversely, if you’re a Maintainer type, joining an early-stage startup that’s constantly tearing things down and rebuilding might feel chaotic.

Also, knowing where your weaknesses are allows you to consciously work on them. For example, if you’re great at coming up with ideas but never finish them, you may need to deliberately practice your “Builder” skills. Or if you’re great at execution but feel lacking in creativity, you could try setting aside some free time for exploration.

At the end of the day, the core message of Boris’ observation is this: In the future, team collaboration and personal development will increasingly focus less on your professional label and more on where you can deliver the most value in the product lifecycle. This shift is already happening. The sooner you realize it, the sooner you’ll benefit.