We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Atlassian: lots of people building, no one steering
Atlassian's product leader shared lessons from shipping AI across 20 apps. The biggest one is about people. Atlassian started about 10 projects staffed by "AI builders": PMs, designers and engineers who code with AI. They moved fast at first, then "slowed down terribly" after a few weeks or months. In the speaker's words, "everyone was rowing but no one was steering," and PMs and designers slipped back into their old roles to unblock decisions . Atlassian is adding an AI-builder role, but doesn't expect most PMs and designers to take it. The PM-and-design to engineering ratio is about 1:10, yet with AI it "feels like" 1:30 or 1:40, so steering matters more .
Other lessons from the talk:
- Use chat for discovery. What users typed into whiteboard chat became features, such as grouping sticky notes into themes, and new workflows, such as turning brainstorm cards into Jira tickets . Features built for humans are then exposed as tools agents can use, including through MCP or a CLI .
- Adding AI to existing products is fine. Atlassian says adding AI to existing workflows was "probably one of the best things we did." Its rule: reimagine workflows for new products, evolve them for existing ones . Agents should get the same primitives as humans: tools, context, goals, accountability, and awareness of what the team is doing .
- More junior hiring. Atlassian now hires more juniors and seniors and fewer mid-level people. It pairs juniors' willingness to experiment with seniors' eye for spotting slop, through a four-day "AI builder week" .
A r/ProductManagement post argues nearly the opposite. Teams that struggle "add AI to the workflow they already had" and end up with "a faster version of the broken process" . Atlassian's distinction between new and existing products may settle the disagreement.
Collison: agents could reward better products
Patrick Collison argues that personal agents will act as "a kind of structural subsidy for product quality." His thought experiment: imagine every buyer spent 10 hours researching each purchase. In that world, making the product better becomes a more effective strategy than winning on distribution . The other side of that change: coupons and other price discrimination work less well, and so does the cross-subsidy in which people who forget to cancel subscriptions pay for everyone else . Collison expects potentially "pretty big" changes for businesses that monetize demand routing, meaning placement fees and ranking algorithms . He also says it's open whether agents will concentrate demand on a few top products or spread it out, and that all of this assumes agents work for the consumer .
AI PM listings: no ML degree required, few entry-level roles
Aakash Gupta used AI to scan 8,354 open roles at 36 companies and found 651 unique product roles . Of the AI PM roles, 151 don't require hands-on ML experience and 15 do. Where pay was listed, the no-ML AI PM roles had a median of $262K, compared with $216K for non-AI PM roles. Only 8 of the 651 were entry-level . Anthropic and OpenAI listings asked for a grasp of model capabilities and for pairing offline evaluation with online experimentation . Gupta's caveat: these are listings, not hires .
Surge's new sudo L7 benchmark makes a related point. It has 60 tasks, mostly from private production repos, and grades architectural judgment and "should we even be doing this?" The best agents succeed on only about 45% of tasks . Lenny Rachitsky called that "half-way" to staff level .
New roles on AI-heavy teams
Sachin Rekhi sees three roles emerging on teams at the AI frontier :
- AI platform engineers, who run shared skill marketplaces, make company context machine-readable, and manage MCP connections.
- AI operations leads, who are embedded in marketing, sales and legal teams to automate their workflows.
- Forward-deployed engineers, who work inside customer organizations.
Agent safety is a product decision
Gupta retells the PocketOS incident. An agent working in staging found a domain-management token that, unknown to the team, could also delete production volumes. One API call wiped the database and the backups stored with it. The newest recoverable backup was three months old . The rules were in the agent's instructions, and it broke them anyway. The fixes all sit in the harness: narrowly scoped tokens, backups the agent can't reach, confirmation before irreversible actions, and complete separation of staging and production . His starting step: list everything your agent can destroy and put a guard in code on each item .
From the community
- Claude Code as a PM knowledge base. One two-founder team runs its whole company from a markdown git repo. They advise starting small with decision records (question, options, decision, rationale, review date) and saving nothing without a human saying yes .
- The domain-experience filter. A laid-off PM landed 4 interviews from 70 applications, and second rounds came only from companies in their own industry . A hiring-side reply defended the filter: when a role gets 300 applications in four days, domain experience is the only thing you can check in thirty seconds . Another reply countered that domain experience really matters only for infrastructure, hardware, deep ML, and compliance-heavy roles .
- LinkedIn replaced its APM program with an Associate Product Builder program . The roles differ by who builds and where: AI PMs build AI models or features into products, typically shipping specs, evaluations, and prototypes while engineers write production code ; forward deployed engineers write production code for one customer’s deployment ; Product Builders use AI to write and review code across product, design, and engineering . The post notes that most Product Builder roles today are still advertised as AI PM jobs .
- A scan of 8,354 openings at 36 companies filtered to 651 unique product roles; 151 AI PM roles did not require hands-on ML experience, 15 did, and only 8 roles were entry-level . Among postings listing pay, median listed pay was $262K for AI PM roles without an ML requirement versus $216K for non-AI PM roles, based on range midpoints across 116 and 59 postings, respectively . Anthropic and OpenAI examples emphasized understanding model capabilities, working fluently with engineering, and combining offline evaluation with online experimentation and user signals; the author notes these skills can be learned without an ML degree . The figures describe job listings, not hires .
- The post argues that as AI lowers delivery costs, product sense matters more: PMs still need to manage stakeholders, navigate organizational politics, infer underlying user needs from feedback and data, prioritize limited resources, and own decisions .
- In the PocketOS incident recounted in the post, an agent deleted a production database and its backups after a staging task, using a token whose permissions also allowed production-volume deletion; the newest recoverable backup was three months old . The practical lesson is to enforce safety in the agent harness—not just prompts—with narrowly scoped tokens, backups the agent cannot access, confirmation for irreversible actions, and separation between staging and production; inventory destructive capabilities and guard them in code .
- Buffadhd’s family onboarding funnel shows a sharp drop at the child-invite handoff: of 25 families who signed up, 16 created a child profile, 3 sent an invite, 2 children opened it, and none were active after the first week; its builder is seeking ways to improve the handoff in this two-sided signup flow.
- Wisibl’s founder describes a PM context-retrieval problem—decisions and answers get scattered across meetings, Slack, and docs—and positions the early-beta product as an alternative to meeting-by-meeting notes: it organizes decisions, discussions, and open questions by product area, connects context across time, and answers questions with source attribution.
- Listd lets users turn a social video into an organized list before signing up; its builder is seeking feedback on value clarity, first-use experience, and whether to support varied saved-video use cases or focus on a vertical such as food or travel.
- Lathe’s creator differentiates its Mac media app around working directly in existing folders, keeping data on-device, and automating repetitive batch workflows with “Recipes”; most features are free, while pro features use a one-time $49.99 unlock.
- One PM’s 2026 search yielded interviews with 4 companies from 70 applications; second rounds occurred only with same-industry employers, and the PM ultimately found a better-paid role with a strong team in that industry. This is a firsthand account, not a market-wide hiring rate.
- Replies debate how much domain experience PM hiring should require: one commenter argues core product skills transfer across industries, with domain expertise most justified for infrastructure, hardware, deep ML, some APIs, and risk/compliance-heavy roles; another says domain screening can be a practical filter when a role gets 300 applications in four days and prior in-domain shipping may reduce ramp time.
- Job-search tactics raised include using AI for CV and job-description review; one commenter reports using Claude and Jobscan to align a resume with a JD for ATS, while another says PM hires in their network commonly had an existing connection at the company.
- In established SaaS products, use in-product chat as a discovery surface: observe what users try, then turn recurring requests into native features, AI workflows, or deliberate handoffs between chat and the product UI. Atlassian’s examples include grouping whiteboard cards and turning brainstorms into backlog tickets.
- For existing products, add AI to established workflows and evolve them through customer learning; for new products, reimagine the workflows. A useful default is to support agents with the same core primitives as people—tools, context, goals, accountability, and awareness of team activity—while allowing justified exceptions.
- Treat capabilities built for people as potential agent skills and tools too; Atlassian says its capabilities can be exposed to external agents through MCP or its CLI.
- Preserve explicit product and design direction as AI speeds implementation: Atlassian’s AI-builder projects initially moved quickly but later stalled when nobody was steering decisions. The company also describes pairing AI experimentation from junior staff with senior staff’s quality control, and running four-day AI-builder weeks for tool-sharing and quality practices.
Lenny Rachitsky described Surge’s sudo L7 benchmark as showing AI is “half-way” to staff-level engineering; it tests 60 tasks, mostly from private production repos, with rubrics covering correctness, engineering craft, architectural judgment, thought partnership, and complexity, and the best agents succeed on only about 45% of tasks. The benchmark distinguishes agents’ ability to handle well-defined L3 tickets from staff-level work such as deciding what to build, anticipating production failures, and questioning whether work should be done at all—a useful caution against equating ticket-level coding ability with broader engineering judgment.
A session was announced to review three AI product-marketing tests run on one B2B product, including their outputs, failure points, and which the presenter would trust.
Shreyas Doshi asks whether someone on a team appears to be using AI performatively while colleagues recognize it but avoid saying so aloud.
- Start an AI-assisted PM knowledge base small: begin with the recurring problem of losing decision rationale, record the question, options, decision, rationale, and a review date, then add commands or skills when work repeats.
- Keep the knowledge base trustworthy with maintained canonical docs and a human gate: one setup used a reviewed ingest queue and routing table, while another required a person to approve AI suggestions before anything was written.
- Reported PM uses include summarizing meeting notes and linking them to past decisions for later retrieval, and periodically capturing work communications so an agent can draft stakeholder replies using accumulated context.
Dan Shipper’s AI-era team-structure thesis is framed as moving from “two-pizza teams” to “two-slice teams”; the post does not explain the model and points to his full 20-minute talk for details.
A shared company story can act as a decision filter: it helps product, sales, and marketing make consistent choices instead of repeatedly negotiating from different assumptions. For roadmap decisions, test whether a feature advances the customer outcome the story promises; features that do not fit can be cut even if they are technically interesting. The founder should own and repeatedly communicate the story across internal and external settings; marketing can amplify it but cannot substitute for the founder’s strategic clarity.
A startup founder working in product ops recommends building one or two products while practicing ideation, user interviews, root-cause analysis, and persona creation; document the process as a portfolio, using AI tools to help even without coding experience. Another transition suggestion is to turn problems already solved into product case studies that show user work, prioritization, and measured results.
For digital-media PMs, commenters recommend the Prof G pod network as a model: its content builds an audience that buys its products, feeding a sales funnel rather than only attracting podcast listeners .
A founder proposes an AI-native vertical roll-up as an alternative to selling software into tech-averse sectors: acquire an operating company, then build AI workflows around its ontology. The post frames this as a theoretical strategy, with PE expertise, a strong engineering team, and potentially a staged approach—first selling agents or products to a vertical—as prerequisites, not as a validated playbook. A commenter flags the upfront acquisition multiple and the risk that customers leave if their systems are replaced; the founder acknowledges greater risk and says the approach could be more profitable if it works, without claiming it is cheaper.
An Indian PM student launched PM Job Getaway, a free job board that he says lists 80 verified entry-level PM roles, refreshes every 12 hours, and requires no signup or ads; he built it to address boards dominated by roles requiring 5+ years’ experience and links that do not work.
Agent-oriented infrastructure may need a distinct design target from human-oriented VMs: the discussion highlights agent-driven product selection, lower complexity, and faster startup, while humans set policies, guardrails, and dashboards. Pat Gelsinger frames security, performance, abstraction, and migration as core requirements for agent-serving virtualization and management.
A product-management takeaway from the poster’s observations: setting aside time for prompts or adding AI to existing workflows can be mistaken for adoption; without redesigning processes around AI’s strengths, teams may end up with only a faster version of a broken workflow.
- A solo-app operator is exploring business and government customers alongside the consumer market, proposing $36 per licensed phone annually while considering annual, six-month, or monthly terms; the consumer offer is $7.95 monthly or $39.95 lifetime.
- A commenter recommends planning 12–18 months of cash flow, checking whether increased advertising can keep growing customer acquisition or will hit a constraint, and reserving resources for product maintenance, growth, and possible support or development staff. They also suggest conservative, status-quo, and aggressive revenue/cost scenarios that account for premium enterprise/government pricing or lower pricing to gain market share.
Sachin Rekhi reports three roles emerging on frontier teams as they transform with AI:
- AI platform engineers centrally build and maintain shared AI infrastructure, such as a skill marketplace, machine-readable company context, and MCP connections; some teams build an internal AI harness rather than customize off-the-shelf tools from OpenAI or Anthropic.
- AI operations leads embed in functional teams—often nontechnical functions such as marketing, sales, GTM, and legal—to partner with team leads and automate workflows.
- Forward deployed engineers work with customers to build AI solutions using their company’s products; Rekhi says the role is becoming more popular in the AI era.
A product manager described conceptualizing an AI assistant for relocation logistics that helps customers choose household or office items based on moving requirements, with aims to address user pain points, simplify booking, and improve website engagement and conversions; the post reports goals, not measured outcomes.
- Patrick Collison argues that consumer agents could make product quality a more effective competitive strategy: by researching purchases more thoroughly, agents may help better products overcome distribution advantages and direct more rewards toward companies that improve their products.
- As agents aggregate product-quality information, those signals may become more influential; whether agents concentrate demand on superstar products or better match varied individual preferences remains an open question.
- Agents may also weaken some price discrimination and subscription models that benefit from consumer inattention, while changing attention-based demand routing and placement economics; Collison flags the net effects and whether agents will reliably act for consumers as uncertain.