At the AI-native company Cursor, roles are "really muddy." Team members contribute based on individual strengths—like visual design or systems architecture—and use AI agents to bridge skill gaps and tie work together. This creates a more fluid and efficient team structure.
Related Insights
The traditional, linear handoff from product (PRDs) to design to dev is too slow for AI's rapid iteration cycles. Leading companies merge these roles into smaller, senior teams where design and product deliver functional prototypes directly to engineering, collapsing the feedback loop and accelerating development.
AI will make the traditional "product pod" structure obsolete for design. Designers, empowered to learn contexts faster and cover more ground, will operate in a more fluid, centralized team. They will be deployed across entire user journeys that span multiple teams, rather than being calcified within a single product area.
Don't think of AI as replacing roles. Instead, envision a new organizational structure where every human employee manages a team of their own specialized AI agents. This model enhances individual capabilities without eliminating the human team, making everyone more effective.
As AI agents handle technical execution, the most valuable human skill becomes ideation. Replit CEO Amjad Massad predicts this will dissolve rigid corporate hierarchies in favor of adaptable teams of generalists who collaborate with autonomous AI tools to bring ideas to life.
AI's productivity gains mean that on a lean, early-stage team, there is little room for purely specialized roles. According to founder Drew Wilson, every team member, including designers, must be able to contribute directly to the codebase. The traditional "design artifact" workflow is too slow.
In an AI-driven world, product teams should operate like a busy shipyard: seemingly chaotic but underpinned by high skill and careful communication. This cross-functional pod (PM, Eng, Design, Research, Data, Marketing) collaborates constantly, breaking down traditional processes like standups.
The traditional tech team structure of separate product, engineering, and design roles is becoming obsolete. AI startups favor small teams of 'polymaths'—T-shaped builders who can contribute across disciplines. This shift values broad, hands-on capability over deep specialization for most early-stage roles.
Separating AI agents into distinct roles (e.g., a technical expert and a customer-facing communicator) mirrors real-world team specializations. This allows for tailored configurations, like different 'temperature' settings for creativity versus accuracy, improving overall performance and preventing role confusion.
For over a decade, software development fragmented into siloed roles (PM, Design, Eng) with their own tools. AI code editors are collapsing these boundaries by creating a unified workspace where a single "maker" or a streamlined team can build, iterate, and ship, much like in the early days of computing.
The traditional "assembly line" model of product development (PM -> Design -> Eng) fails with AI. Instead, teams must operate like a "jazz band," where roles are fluid, members "riff" off each other's work, and territorialism is a failure mode. PMs might code and designers might write specs.
