# Boris Cherny: Engineering, Product, Design, Data Science Are Melting Into Archetypes. Seeing the Same. Published: 2026-06-29 **Boris Cherny (Creator & Head Of Claude Code @Anthropic) says the job titles are melting away and mapping to a new set of roles** ...and I am seeing similar changes in businesses I work with. **Boris' point** - Engineering, product, design, data science.. all melting into one kind of role. The work now maps to **archetypes - prototyper, builder, sweeper, grower, maintainer** - rather than to your title. Seeing something very similar with the folks I work with. These are small businesses. And in many cases, I am the one bringing in Claude Code and Claude Cowork ...and getting them started. And as things progress, introduce options beyond Claude to manage costs better ... **What I am seeing day to day** - marketing and finance folks building their own local automations and dashboards. The builders and developers turning them into production grade tools. Developers now working across the whole stack, doesn't matter if they started out as frontend, backend etc. Data scientists running more models, better validated, refreshed more often... and creating working prototypes of deployable tools and passing on to builders... the whole thing is changing very fast ... **The work is moving across the team. Job titles matter less and less.** Boris' original: --- ## Full Deck Content (Text Format) ### Slide 1 - How the roles might look in the future Engineering, product, design and data science.. **melting into a new kind of role**. ### Slide 2 - Boris Cherny's framing: five archetypes > 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: - **Prototyper:** comes up with brand new ideas; churns out many ideas, most of which don't ship. - **Builder:** quickly turns a prototype/idea into production-grade product/infra. - **Sweeper:** cleans up the UI, simplifies the code and system, unships, optimizes performance. - **Grower:** takes a product that has been built and iterates on it to improve Product-Market Fit. - **Maintainer:** owns a mature system to make it secure, reliable, fast, and efficient as it scales. ### Slide 3 - The mix depends on the product stage Many people **span across 2 roles, and sometimes 3 roles**. I also notice that these roles are **not really tied to job function** -- e.g. 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? ### Slide 4 - What I am seeing in small businesses - **Business teams** - Marketing and finance build their own automations and dashboards, in VBA and Python. - **The handoff** - When it has to become a real, secure tool, it goes to a developer, or me, to build out and harden. - **Developers** - Maintain it, secure it, and now work full-stack across every language and platform. - **Data science** - More models, more robust, better validated, refreshed more often. **The work is moving across the team. Job titles matter less and less.** --- *Amar Harolikar · Decision Sciences & Applied AI · [tigzig.com](https://tigzig.com).*