As engineering, product, design, DS, etc. melt into a new kind of role, I was reflecting on what roles might look like in the future. For example, when I look at the Claude Code team I see what I think is five archetypes:
1. Prototyper: comes up with brand new ideas; churns out many ideas, most of which don't ship
2. Builder: quickly turns a prototype/idea into production-grade product/infra
3. Sweeper: cleans up the UI, simplifies the code and system, unships, optimizes performance
4. Grower: takes a product that has been built and iterates on it to improve Product-Market Fit
5. Maintainer: owns a mature system to make it secure, reliable, fast, and efficient as it scales
Many people span across 2 roles, and sometimes 3 roles. I also notice that these roles are not really tied to job function -- eg. across Anthropic, some designers match category 1, some 2, some 3; same for engineers, PM, DS.
A healthy team needs a mix of these, depending on the product:
- A product that is new and pre-PMF needs people that are strong at 1+2+3
- A product that is growing and has found PMF needs 2+3+4 and some 5
- A product that has strong PMF needs 3+4+5 and some 2
Maybe product roles of the future will look more like this, and less like the domain-specific roles of today?
The best predictor of success for tech companies, at every stage from during the YC batch to public company with billions in revenue, is the rate of shipping new stuff.
@Kappaemme1926 I ask because, Iโm often asked by folks new to tech how to become SWEs in the AI era, and itโs been hard recommending a specific path since I learnt to code from the pre-AI era
@yaw_bossman It wonโt stop, because itโs essentially a commercial break bringing in millions of dollars
Their bet is people will get used to it, similar to how timeouts exist in other sports like NBA and NFL
If you want something from someone, make it clear what. It's not imposing to ask explicitly for something; it's imposing to be vague and make the recipient work to figure out what you want.