Trigger: Three senior design roles posted September 2–3 across separate verticals: Director, Customer & Partner Experience; Sr. Staff, Security and Risk; Principal, SalesCRM. High confidence this is a coordinated headcount release. Three reqs spanning different business units, posted within 24 hours, queued to go live the week before Labor Day rather than after. Someone approved a design investment tranche and wanted it in market before the holiday. The gate that held this card — no identified buyer — is resolved. Carly Price, Senior Director of Customer & Partner Experience Design, posted publicly about the Director role.
Window: Ten days old. Enterprise design searches run 6–10 weeks. The first full post-holiday business week just ended. You are early. Act within five business days if you have bandwidth — but read the verdict first.
What the cluster tells you
Amy Lokey, ServiceNow's Chief Experience Officer for nearly seven years, left recently. No successor announced. Dantley Davis holds SVP of Design. Three simultaneous senior design hires across different verticals, with no CXO backfill, reads like design leadership being pushed downward into product verticals rather than replaced at the center. Moderate confidence — pattern inference, not confirmed. If correct, this Director role carries more autonomy than the title suggests, because the vertical is getting its own design authority instead of borrowing it from a central function.
ServiceNow rebranded its AI experience layer in August. Now Assist, Moveworks, and AI Experience are now ServiceNow Otto. The portal ecosystem this Director owns — ServiceNow University, Product Documentation, partner portals — is where users encounter Otto. The mandate is making these surfaces AI-native.
Why this role, not the other two. The Sr. Staff Security and Risk role sits in a domain you have no published proof for. The Principal SalesCRM role is closer (enterprise platform, AI-native CRM), but it's a deep IC in a CRM-specific vertical where your portfolio doesn't show domain experience. The Director, Customer & Partner Experience is the strongest fit: cross-surface platform coherence maps to Alibaba, the AI-native portal mandate maps to your Trust essay and TinyFish production experience, and Price's public language about the role describes the problem you've already solved.
Rubric
| Dimension | Score | Rationale |
|---|---|---|
| Company | ||
| AI centrality | +2 | Primary strategic bet, not core product |
| Stage & equity window | 1 | ~$200B market cap, post-IPO, no meaningful equity window |
| Design influence ceiling | 2 | SVP Design exists; unclear how much strategic authority reaches this vertical |
| Trajectory | 2 | Stable, growing, mature |
| Company total | 7 | |
| Role | ||
| Comp potential | 2 | Base $221K–$387K plus RSUs and bonus; cash clears $250K at upper range, but post-IPO equity is stock appreciation, not a wealth event |
| Scope expandability | 2 | Defined vertical, some ceiling |
| Craft depth | 2 | Director with team; Price's language emphasizes craft and execution, but management-weighted |
| AI exposure | 2 | Making portals AI-native, not designing the core AI product |
| Portfolio value | 2 | Solid enterprise work, incremental for junochen.com |
| Role total | 10 |
Company 7, role 10. Both clear Watch thresholds. Neither reaches Act (needs company 9+ AND role 12+). Worth pursuing if your Act queue is clear this week. Don't displace Act-tier targets for it.
Your angle
Lead with Alibaba. Price's LinkedIn post about this role names the problem you solved: connecting multiple products into a cohesive end-to-end journey. Alibaba.com's B2B platform had grown fragmented across homepage, search, and product detail pages serving 25M+ desktop sessions. You named the structural gap, built the research case, secured the mandate, redesigned every major surface. The outcome — +20% daily transactions, +2.2pt NPS across a $50B+ GMV platform — is proof that cross-surface coherence at enterprise scale produces measurable results. That maps directly to what Price is hiring for.
Secondary: Trust essay and TinyFish production experience give you the AI-native credibility Price is asking for when she writes "AI-native experiences and new ways of working." You shipped an agentic platform from 0 to 1 at TinyFish. The Trust essay's five handoffs framework maps to how Otto should surface in portal experiences. Enterprise platform coherence plus AI-native practitioner depth is a combination most candidates in this pipeline won't have — enterprise design directors who've never built with agents, or AI-native candidates who've never redesigned a platform at this scale.
Who to contact
Carly Price, Senior Director of Customer & Partner Experience Design. A conference biography describes her as Head of Design for Customer and Partner Experiences, leading teams responsible for portals and self-service experiences. She posted about this role publicly. She is the buyer.
Public fingerprint: Price's hiring post prioritizes systems thinking, content-rich complexity, cross-product coherence, team building, AI-native working methods, and "vision, craft, and execution at scale." A conference account from May 2026 reports her team encoding their design system into Claude Code as a rules layer to produce clickable prototypes faster. She values AI in the design process, not only in the product.
Warm path: No public overlap found. Price's background — Walmart, JPMorgan Chase, Ford, IDEO, Casper — doesn't intersect BCG DV or Alibaba networks on reviewed surfaces. Check your LinkedIn graph. If you have 3+ mutual connections, reference them in the close. If cold, her own post is the hook.
Channel: Apply through the official posting first — Price explicitly asked candidates to do this because of volume. Then send a cold LinkedIn DM to Price within 24 hours of applying.
Routing note: Does this Director report to Price, to David Hoare (Group VP, Digital Content & Design), or directly to Davis? Price owns the scope and is recruiting for it, but the org chart above her isn't publicly confirmed. This doesn't block outreach — Price is the right first contact regardless. Ask the reporting structure in your first conversation.
Outreach
Subject line: Cross-surface coherence in ServiceNow's portal ecosystem
Cold message to Price:
Your post about the Director, Customer & Partner Experience role caught me — specifically "connecting multiple products into a cohesive end-to-end journey." That's the problem I solved as Head of Design and Research at Alibaba.com: a $50B+ B2B platform where homepage, search, and product pages had grown fragmented across years of siloed development. I led the cross-surface redesign that produced +20% daily transactions and +2.2pt NPS. I'd welcome 20 minutes to discuss how that architecture thinking applies to ServiceNow's portal ecosystem, particularly as you bring Otto into those experiences. My work is at junochen.com.
If warm path exists (adapt):
[Mutual connection] suggested I reach out — I saw your post about the Director, Customer & Partner Experience role and the mandate maps closely to work I led at Alibaba.com, where I redesigned a fragmented $50B+ B2B platform into a cohesive cross-surface experience (+20% transactions, +2.2pt NPS). I'd value 20 minutes on how that kind of architectural coherence applies to ServiceNow's portal ecosystem as it becomes AI-native. My published work is at junochen.com.
What not to say:
- Don't reference Amy Lokey's departure or speculate about CXO succession. It reads as opportunistic.
- Don't use "Now Assist" or "Now Intelligence" — legacy branding. The current AI experience is ServiceNow Otto, the platform is ServiceNow AI Platform.
Cover letter
The hardest design problem in ServiceNow's portal ecosystem right now is the seams between surfaces. ServiceNow University, Product Documentation, and the partner portal each serve different users at different moments, but the journey across them is where coherence breaks down. Making those seams invisible while bringing Otto into the experience is an architecture problem before it's a visual design problem.
I led this kind of cross-surface redesign as Head of Design and Research at Alibaba.com, where a $50B+ B2B platform had grown fragmented across homepage, search, and product detail pages serving 25M+ desktop sessions. I named the structural gap, built the research case to secure the mandate, and led three cross-functional sprints that redesigned every major surface — resulting in +20% daily transactions, +2.2pt NPS, and a 47% reduction in buyer security concerns. The work required the same combination your posting describes: strategic thinking, systematic design, and execution at enterprise scale.
Most recently as Head of Product at TinyFish, I shipped an AI-native enterprise platform from 0 to 1 in three months, working daily with agent traces, auditability, and governance challenges in production. That practitioner depth in agentic AI is what I'd bring to making ServiceNow's portal experiences genuinely AI-native. I moved to product to build with AI from zero; I'm returning to design because I want to apply that technical depth to a specific, high-stakes design problem and I miss the creative impact of leading design teams.
I'd welcome the chance to discuss how cross-surface coherence and AI-native design thinking apply to your team's current mandate. My published work — including the Trust essay on designing for agentic systems and three live enterprise AI demos — is at junochen.com.
Resume emphasis
Craft depth 2, AI exposure 2. Enterprise platform leadership leads.
- Lead: Alibaba.com — Head of Design and Research, North America. $50B+ GMV, cross-surface platform redesign, +20% transactions, +2.2pt NPS. Direct match for Price's stated priority.
- Follow: Thermo Fisher mySupply (Product Design Director, BCG Digital Ventures) — $20M+ margin, 6 pharma partners, 100% adoption. Enterprise complexity, regulated environment, 0→1 build.
- AI credibility: Agentic Labs — Brand Pulse, Retail Velocity, Carrier IQ. Live enterprise AI demos at junochen.com.
- TinyFish as bridge — "Most recently, Head of Product at TinyFish (enterprise web agent platform, Series A). Shipped agentic platform 0→1 in 3 months." One line in the header.
- Trim or move down: Red Cross, Equinox+, Allē — wrong domain for this role.
The non-obvious thing
Price's team is encoding their design system into Claude Code as a rules layer to generate clickable prototypes. When she writes "AI-native experiences and new ways of working," the evaluation bar covers the design process itself, not only the product. Your TinyFish experience building with AI tools in production is relevant here in a way most enterprise design directors can't match. If you get to a conversation, ask Price about the Claude Code workflow. It signals homework and opens a thread where your practitioner AI experience becomes visible.
Competitive landscape
Enterprise design directors (Salesforce, Adobe, Google pedigree): They'll match or exceed you on enterprise org size and may outperform on content and documentation design experience — this role is content-heavy, and your portfolio is product-design weighted. Few will have shipped agentic AI in production or published frontier design thinking. Price is asking for AI-native fluency alongside enterprise scale. Moderate confidence.
Internal candidates: ServiceNow's design org is large enough to produce contenders who know the product and the politics. Your Alibaba case counters this directly — you walked into a complex platform cold, identified the structural gap, and shipped a redesign that moved metrics. That's the argument for an external hire.
Content design specialists: People with deep documentation and portal design backgrounds will speak Price's "content-rich complexity" language natively. They likely lack cross-surface platform architecture experience and AI-native credibility. Your Alibaba case is a platform coherence story, but be prepared for questions about content design experience specifically. Your portfolio doesn't demonstrate it, and if Price weights content expertise heavily, that's where you're thinnest. Speculative — depends on how her evaluation criteria actually break.
Warning signs
Post-IPO equity ceiling. RSUs appreciate with the stock. They won't create wealth-changing upside at a $200B company.
Scope could feel infrastructure-adjacent. Documentation, university, portals — this is the learning and support layer. If you want to design the AI product itself, this role designs how people learn about and adopt it. That distinction matters for portfolio value and daily satisfaction.
CXO departure with no successor. Lokey's exit and the absence of a replacement could mean design authority is being distributed — good for this role's autonomy — or that design is losing its executive seat. Watch for which interpretation Davis's tenure confirms.
Post-outreach signals
Enterprise archetype timing:
- Response within 5–7 business days from Price or a recruiter is normal.
- Silence past 10 business days: follow up once, referencing a new signal — a Price post, a product update. Don't "check in."
- Recruiter screen scheduled within the first week is fast for enterprise. Prioritize prep immediately.
- If Price responds and engages the cross-surface coherence framing, respond within 24 hours and deepen.
- Two unanswered follow-ups is the ceiling. Redirect energy to Act-tier targets.
- Otto replacing Now Assist: ServiceNow's August 6 release notes document the full rebrand from Now Assist, Moveworks, and AI Experience to ServiceNow Otto across product labels, icons, and documentation — worth scanning before any conversation so you speak their current language.
- Semantic search in Product Documentation: ServiceNow's Q3 2026 documentation release introduced meaning-and-intent-based search while listing chatbot and agentic features as upcoming, which tells you exactly where the AI-native portal mandate currently sits versus where it's headed.
- Dantley Davis on AI and taste: The June 17 ServiceNow Insights podcast has Davis arguing that rapid AI concept generation still requires a human "tastemaker" for discernment — useful framing if your conversation escalates above Price.
- Autonomous Security context: ServiceNow's August 4 announcement of six Autonomous Security solutions describes prevention-first, AI-native defense with rollback and continuous audit logging — not your target role, but understanding the company's broader autonomous-agent vocabulary will sharpen how you talk about Otto in the portal context.