The Job Positions of the AI Future

July 5, 2026

ai-daily-brief-podcast

Overview

This episode of The AI Daily Brief — a daily podcast and video focused on significant AI news and discussion — examines how job roles and organisational structures are evolving in response to agentic AI. The central thesis is that the traditional model of narrow, function-specific job descriptions is giving way to a new set of cross-functional archetypes defined by how people relate to work (building, maintaining, optimising) and how they relate to the world outside the organisation (scouting, editing, growing). The episode is anchored in a tweet by Boris Cherney, creator of Claude Code at Anthropic, who proposed five product-lifecycle archetypes for engineering teams. The host extends and critiques that framework, adding externally-facing roles and applying the full set across sales, marketing, and back-office functions.

Source video URL was not provided.

Prerequisites

Basic familiarity with software product development lifecycles (prototyping, production, scaling)
General understanding of what AI agents and agentic workflows are (systems where AI autonomously executes multi-step tasks)
Awareness of current AI coding and productivity tools (e.g., Claude Code, Codex)
Familiarity with standard organisational functions: product, engineering, sales, marketing, finance, HR, operations
Some exposure to concepts like product-market fit (PMF), go-to-market motions, and organisational design

Main Points

1. The Meta-Shift: From Doing to Managing Agents

The foundational change underlying all role evolution is the shift from executing tasks directly to managing agents that execute those tasks.
Workers must determine how much of their daily or weekly work can be outsourced to agent teams, then identify what substantive work remains.
Non-technical workers are increasingly mapping lessons from developer workflows onto their own roles.

2. Boris Cherney’s Five Work-Facing Archetypes

Boris Cherney (Claude Code, Anthropic) proposed five archetypes observed on his team. These track a product’s lifecycle from inception to maturity:

Prototyper — Generates new ideas and produces first versions rapidly; most ideas do not ship. Historically undervalued because “ideas are free,” but now more significant as first-version creation becomes cheap through code-generating agents.
Builder — Converts prototypes into production-grade, hardened systems. Requires different dispositions than prototyping (security, reliability, bug tolerance).
Sweeper — Optimises and cleans: simplifies code, prunes UI, removes what doesn’t work, improves performance. Key word is optimise, not merely clean up.
Grower — Takes a built product and iterates it toward better product-market fit; the first archetype that faces outward toward users and market signals.
Maintainer — Owns mature systems for security, reliability, and efficiency at scale; a categorically different disposition from builders.

Cherney also notes that healthy teams need different mixes of these archetypes depending on lifecycle stage:

Pre-PMF: Prototyper + Builder + Sweeper
Growing/found PMF: Builder + Sweeper + Grower + some Maintainer
Strong PMF: Sweeper + Grower + Maintainer + some Builder

3. The Missing Layer: Externally-Facing Archetypes

The host argues Cherney’s framework is largely inward-facing (toward the artifact) and proposes additional archetypes oriented toward people and external signals:

Editor — Decides which prototypes deserve to be built; acts as selector and focuser of organisational energy. Can be empirical or taste-based; increasingly critical as prototyping becomes cheap and attention remains scarce.
Scout — Aggregates and interprets external signals (market, culture, competitors, customer behaviour) to feed the prototyper. This role may be substantially filled by agents given their capacity for information collation, though taste remains human.
Evangelist — Moves the market to see the world the way the builders see it; operates across content, conversation, and community; owns the intersection of internal and external.
Orchestrator — Coordinates disparate role archetypes and agent bundles across the organisation; functions at both micro (own workflow) and macro (cross-functional) levels. Everyone will orchestrate to some degree; specialist orchestrators become more important as output volume scales.
Conductor — A more specific variant of orchestrator focused on managing teams of AI agents, ensuring coherent outputs across synthetic/digital workers.
Risk Steward — Anticipates risks created by accelerated, agent-driven operations; not a gatekeeper but a forward-oriented role that keeps momentum from creating derailments. Reframes risk management from bottleneck to enabler.

4. Applying the Archetypes to Sales

Prototyper: Tests new pitches, segments, and offers.
Builder: Turns successful prototypes into repeatable, scalable playbooks.
Sweeper: Prunes dead scripts and poor-fit segments; maintains pipeline velocity.
Grower: Iterates on strategy against real-world performance; drives deal velocity and expansion.
Maintainer: Builds and sustains a complete sales system (pipeline discipline, account coverage).
Scout and Editor are highly relevant; Risk Steward is particularly important given the tendency of sales motions to pursue revenue at any cost.

5. Applying the Archetypes to Marketing

Scout: Reads audience, culture, and competitors; feeds signals into the organisation.
Prototyper: Tests new narratives, campaigns, and channels.
Editor: Uses taste and brand judgment to select which stories and angles to pursue.
Builder: Converts sparks into full campaign machines.
Sweeper: Kills weak messaging, prunes underperforming channels, simplifies funnels.
Grower: Data-driven optimisation of conversion, growth, and cost; outputs also feed the next scout cycle.
Maintainer: Upholds brand consistency and marketing system infrastructure (CRM, lifecycle systems).

6. Applying the Archetypes to Back Office (Finance, Ops, HR)

These functions are inherently maintenance-oriented; the Maintainer archetype dominates naturally.
Sweeper applies clearly: removing redundant tools, zombie budgets, bad metrics.
Risk Steward and Orchestrator are highly relevant.
Scout and Grower map less cleanly because these functions are internally focused.
However, agentic tools may cause the Prototyper archetype to infiltrate back office: e.g., a finance employee building a small custom tool for expense-reporting exceptions rather than filing a ticket and waiting a quarter.

7. Strategic Implication: When Making Gets Cheap, Every Function Grows a Maker

As the cost of building drops, product-style thinking spreads across all organisational functions.
Becoming the “maker” for your function — adopting the prototyper mindset — is presented as a near-term strategy for individuals to future-proof their roles.
Building things allows workers to expose unseen opportunities and drive organisational change, placing themselves at the centre of how the job itself is redefined.

Key Concepts

Agentic AI / Agents: AI systems that autonomously execute multi-step tasks; the assumed operational substrate for all role changes discussed.
Prototyper: Archetype focused on rapidly generating and first-versioning new ideas.
Builder: Archetype that converts prototypes into production-grade, reliable systems.
Sweeper: Archetype focused on optimising, pruning, and simplifying existing systems or processes.
Grower: Archetype that iterates a built product or system against real-world feedback to improve fit and scale.
Maintainer: Archetype responsible for the long-term reliability, security, and efficiency of mature systems.
Editor: Externally-facing archetype that selects which prototypes or ideas merit investment of resources.
Scout: Archetype that monitors and aggregates external signals (market, culture, competition) to feed internal work.
Evangelist: Archetype that shapes external perception and builds community alignment with internal vision.
Orchestrator: Archetype that coordinates across role archetypes and agent bundles at organisational scale.
Conductor: A specialised orchestrator focused specifically on managing coherent outputs from teams of AI agents.
Risk Steward: Forward-looking archetype that anticipates and mitigates risks created by high-velocity agentic operations.
Product-market fit (PMF): The degree to which a product satisfies strong market demand; used as a lifecycle marker to indicate which archetypes a team needs.
Claude Code: An AI coding agent built by Anthropic; Boris Cherney is identified as its creator.

Summary

The talk argues that the rise of agentic AI is dissolving traditional, function-specific job descriptions and replacing them with a new vocabulary of cross-functional archetypes defined by a person’s orientation toward work and the world. Drawing on Boris Cherney’s five-archetype framework — Prototyper, Builder, Sweeper, Grower, Maintainer — the host affirms that these categories capture real dispositional differences that track a product’s lifecycle, and that they apply meaningfully across engineering, sales, and marketing. However, the host contends that Cherney’s framework is incomplete because it is almost entirely inward-facing; a second tier of externally-facing archetypes — Editor, Scout, Evangelist, Orchestrator, Conductor, and Risk Steward — is necessary to account for the roles that interpret market signals, select which work to pursue, align the outside world with internal vision, coordinate increasingly complex agent-driven output, and prevent accelerating momentum from generating unmanageable risk. The overarching message is that as building becomes cheaper and agents handle more execution, every function in an organisation gains the capacity for maker-style thinking, and individuals who adopt prototyper and maker mindsets within their existing functions will be best positioned to shape — not merely survive — the organisational transformation ahead.