Trigger
Ken Exner appointed CPO, Enterprise & Emerging on August 6. The Principal Product Designer, Rovo & AI posting (req 27204) surfaced publicly around September 15. Moderate confidence that Exner's arrival produced the requisition; high confidence the role is live and actively hiring.
This updates the Issue #11 Atlassian entry, which treated Exner as a probe target for lack of a qualifying role. The role now exists.
Window
The posting is about eleven days old, which means the slate is still forming and has not hardened around two or three finalists. That is the urgency driver. Move this week. Exner's ninety-day organizational window (day 51 now, closing around November 4) is useful framing inside the outreach, but posting age is what sets your timing.
What this trigger means for the design org
Atlassian's AI design function is further along than most candidates applying to this role will assume. The AI careers page already lists two Principal Product Designers on Rovo & AI, a Senior Design Manager for AI, and a Head of Design, AI. This req adds to an existing senior bench rather than starting one. Three simultaneous design-adjacent AI searches — this role, a Senior Design Manager for Jira AI, a Lead Design Technologist — read as a coordinated scaling push rather than backfill.
The routing question has a partial answer. Carola Pescio Canale's Config 2026 speaker bio names Rovo and Jira AI as her teams. Whether she reports into David Hoang, listed as VP of Design, AI at Team '26, or holds a parallel remit is not visible from public signal. For this role, treat Pescio Canale as the buyer.
Your angle
Lead with the Trust essay. Tamar Yehoshua's CXOTalk interview on August 28 described the design problem this role exists to solve: agents are now direct users of Atlassian software, they need organizational context to function, indiscriminate context degrades both performance and cost, and "whoever built the agent that starts is still accountable." That maps onto the five handoffs cleanly. Intent-Setting is which context to expose. In-Progress is agent visibility. Output Review is evaluation. Decision Gate is human sign-off. Loop Feedback is the accountability chain back to a named person. You published the design-side framing in June; she stated the product-side version in August. That overlap is your opening line.
Alibaba carries the second half. It proves you can redesign a $50B+ platform across surfaces that have to hold together. Together the two answer what this role is actually asking: can you design trust surfaces for agents, and can you do it across a product suite.
Secondary, one line: Carrier IQ at Agentic Labs demonstrates all five handoffs in a regulated domain. Deep-link to the live app at junochen.com rather than the homepage.
Rovo's accountability problem sits inside two artifact domains you have not published yet — Agent Infrastructure as UX and Human-Agent System Design. The Trust essay plus Carrier IQ carries the pitch without them. At eleven days on the posting, waiting for an unpublished artifact costs more than it gains. If either domain ships before you send, add the link to the cover letter.
Competitive landscape
Three archetypes will show up on this slate. The archetypes are moderate-confidence inference from the posting language and comparable Principal searches. Their relative strength against you is speculative.
-
Enterprise platform Principal (Salesforce, Adobe, Google). Comparable scale, cross-product design system depth, fluent in talking about a suite rather than a product. What they typically lack is agent-native thinking: their AI work is features added to existing surfaces, not trust architecture for agents acting as users. The Trust essay names the problem they will spend most of the first interview trying to frame. Where you are exposed is team influence footprint. Answer that with the Alibaba mandate — you named the structural gap, built the research case, and got the mandate across homepage, search, and PDP.
-
AI-native designer (Meta AI, Google DeepMind, a well-funded AI startup). Brand pedigree and daily proximity to model behavior. They design internally, so published design thinking at this level is rare among them, and enterprise platform complexity rarer still. You will not win on AI brand recognition, so do not try. Offset it by opening with Yehoshua's own language, which signals you understand Atlassian's specific problem rather than AI design in general.
-
FAANG IC-track Principal. Deep craft, strong prototyping fluency, polished case work. Agentic systems experience is usually thin and the accountability framing usually absent. Carrier IQ is a live app demonstrating all five handoffs; their portfolios more often show AI features. Where you are exposed is refined visual craft artifacts. Steer the conversation toward context and accountability, where the essay gives you the structural advantage.
Who to contact
(1) Carola Pescio Canale — Head of Design, AI, Atlassian. LinkedIn.
Public fingerprint: At Config 2026 she described the strongest AI-era designers as people who use AI "to scale their thinking, not just generate stuff," with emphasis on structured briefs, trackers, and documentation that turn AI into a working collaborator. Nothing public promoting this specific req.
Warm path: Cold. No mutual connection identified.
Channel: LinkedIn DM. Her Config talk is the hook. It is recent, it is specific, and it maps onto how the Trust essay treats structured handoffs as the design layer.
(2) Charlie Sutton — CDO, Atlassian. Escalation route only.
Public fingerprint: At Team '26 he framed the challenge as "redesigning work alongside AI agents." In a conversation with Figma's CDO he described the goal as removing friction without removing the productive mess of collaboration. In a later post he framed the craft as balancing familiar and novel, scalable and personalized, agent goals and human motivation.
Warm path: Cold.
Channel: LinkedIn DM only if Pescio Canale has not responded within 10 business days, or if you learn the role reports through Sutton's org.
Outreach messages
Warm message to Pescio Canale (use if a mutual connection surfaces):
[Mutual connection] suggested I reach out — I've been building a trust framework for agentic handoffs (junochen.com/trust-is-the-new-interface) that maps closely to what your Rovo team is working through on accountability and context surfaces. I'd welcome 20 minutes on how you're approaching the design layer for agents as direct software users.
Cold message to Pescio Canale:
Subject line (if email): Accountability surfaces for Rovo agents
Your Config talk on designers who use AI to scale thinking rather than generate stuff landed for me — it's the same distinction I've been working through in my Trust essay on agentic handoffs. Atlassian's challenge of designing for agents as direct software users (Yehoshua's framing of context, accountability, and human sign-off) is the problem the five-handoffs framework was built to address. I'd welcome 20 minutes on how your team is approaching the accountability layer for Rovo agents. junochen.com/trust-is-the-new-interface
Cold message to Sutton (escalation only):
Subject line (if email): Designing the handoff layer for Rovo agents
Your framing at Team '26 — redesigning work alongside agents rather than adding AI to products — is the clearest articulation I've seen of what makes Atlassian's design challenge distinct. I've been building a trust framework for exactly that problem: how to design handoff surfaces where agents and humans share accountability. I'd welcome 20 minutes on how the Rovo design team is approaching this. junochen.com/trust-is-the-new-interface
What not to say:
- Do not refer to Exner's Amazon background as Alexa. His documented tenure is AWS Developer Tools. Getting that wrong signals you have not done the work.
- Do not frame this as a founding or first-hire opportunity. Two Principals and a Senior Design Manager already sit on Rovo & AI. Offering to build the AI design function will read as uninformed.
Cover letter draft
The hardest design problem at Atlassian right now is making Rovo agents accountable. When Tamar Yehoshua says "whoever built the agent that starts is still accountable" and that agents need organizational context without drowning in it, she's describing a trust architecture problem: which context to expose, how to make agent reasoning visible, where humans approve or override, and how accountability traces back to a named person. That's the problem I've spent the last two years solving.
My Trust essay (junochen.com/trust-is-the-new-interface) maps five handoff surfaces — Intent-Setting, In-Progress, Output Review, Decision Gate, Loop Feedback — that define where human judgment enters an agentic workflow. I built this framework from production: as Head of Product at TinyFish, I shipped an enterprise web agent platform from zero to production in three months, working daily with agent traces, auditability, and governance in enterprise deployments. Carrier IQ, one of three live Agentic Labs apps at junochen.com, demonstrates all five handoffs in a regulated domain. Before that, I led the redesign of Alibaba.com's $50B+ B2B platform as Head of Design and Research — the cross-product complexity of that platform, where trust signals had to work across homepage, search, and product detail surfaces simultaneously, maps directly to Rovo's challenge of unifying AI experiences across Jira, Confluence, and the broader suite.
I moved from design to product at TinyFish to build AI-natively from zero. I'm returning to design because I want to apply that technical depth — agent traces, context engineering, model behavior — to a specific, high-stakes design problem in a product people depend on daily. Rovo's challenge of designing for agents as direct software users is that problem.
I'd welcome a conversation about how the Rovo design team is approaching accountability and context surfaces. Portfolio and framework at junochen.com.
Resume emphasis guidance
- Lead: Trust essay and Agentic Labs, Carrier IQ first among them. The role screens for trust architecture and agent interaction judgment.
- Second: Alibaba.com, Head of Design and Research, North America. Cross-product platform redesign at $50B+ GMV against Rovo's cross-suite mandate. Emphasize the structural gap you named and the mandate you built.
- Third: TinyFish as the bridge, one line. "Head of Product, TinyFish (enterprise web agent platform, Series A). Shipped agentic platform 0→1 in 3 months. Agent traces, auditability, governance in production."
- Fourth: Thermo Fisher mySupply, Product Design Director at BCG Digital Ventures. Regulated, multi-stakeholder, enterprise. Credibility anchor, not a lead.
- Trim: Equinox+ and Allē below the fold. Consumer and loyalty are peripheral to an enterprise AI mandate.
- Transition framing in the header or summary: one sentence on returning to design to apply production AI depth to a vertical design problem.
Post-outreach signals
Enterprise archetype, so calibrate accordingly. A response within 5–7 business days is normal. Past 10 business days, follow up once and hang it on a new signal if one exists — a Sutton post, a Rovo feature announcement, a product update. Follow up again at day 20. Silence at this tier is usually process, not rejection.
If Pescio Canale responds and engages the framework rather than acknowledging the note, that is a strong signal. Reply within 24 hours and take the thread deeper on the accountability layer.
If a recruiter responds instead, the message landed but did not reach the hiring manager. Still worth pursuing. Ask in the screen who the hiring manager is and whether the team reports through the CDO org or the AI product org. That answer tells you whether design holds structural authority on Rovo or sits embedded under product.
Two follow-ups maximum. After three unanswered messages, move Atlassian to Watch and monitor for a posting refresh or a Pescio Canale hiring post.
The non-obvious thing
Yehoshua said Atlassian has made roughly 95% of Confluence's UI actions available through MCP or the CLI — an agent can do nearly anything a person can do in the interface without touching the interface. The design surface for this role is drifting toward the agent-facing protocol layer and the oversight surfaces between agent action and human approval. Most candidates will arrive with a portfolio organized around visual interfaces for AI features. Get the conversation to the protocol layer instead. The Trust essay already operates there.
Warning signs
Existing senior bench. Two named Principals and a Senior Design Manager on Rovo & AI means the actual scope may be narrower than the posting's "set strategic vision" language implies. Ask early: what is this Principal's scope relative to the two already on the team, and what does the role decide versus influence?
Title mismatch. The posting title says Principal; the body copy says Lead Product Designer. That could be Atlassian's internal leveling, stale copy from a revised req, or a hiring committee that has not settled on seniority. Ask about level and scope directly.
Post-IPO equity. Atlassian is public, so compensation is RSUs. The role scores high on craft depth and AI exposure, moderate on total comp potential against your pre-IPO targets.
- Slack's parallel agent search: Michael Lenahan publicly confirmed he's hiring a Principal Architect role at Slack that asks the hire to define human-agent collaboration, handoffs, and control — the same Trust essay territory as Rovo, with a confirmed buyer and direct reporting line.
- Render's first Staff seat: Head of Design Samia Saleem described the Staff Product Designer, Agent Experience opening as Render's first dedicated hire in the category and explicitly invited DMs with portfolios — an unusually direct access route worth comparing against Atlassian's cold path.
- Handshake's 0→1 agent role: The Staff Product Designer, Autonomous Recruiting posting asks a designer to build an AI-native recruiter product from a blank slate, moving between conversational AI and structured workflows — a different substrate than Rovo but the same trust-architecture problem.
- Portfolio case routes still broken: The September 20 site inspection found Agentic Labs apps reachable through direct application URLs but their portfolio case-page routes returning 404 — verify and repair before sending any outreach that links to junochen.com.