Rubric
Company: 8 (AI centrality +2 · Stage/equity 1 · Design influence ceiling 2 · Trajectory 3) Role: 12 (Comp potential 2 · Scope expandability 2 · Craft depth 3 · AI exposure quality 3 · Portfolio value 2) Verdict: Watch. Company misses Act by one point on the equity drag of a $200B+ public company. Role score hits Act on its own. Worth the outreach because the mandate is the closest structural match to the Trust essay in the current scan.
I told you to skip this. Wrong frame. I said you lacked published proof for the security domain — but the design problem here is consequential-action trust, which Issue 12 named as a distinct mandate type and paired with the Trust essay and Carrier IQ. I missed the mapping. Here it is.
Trigger
Three AI-design roles posted Sep 2–3 across Security and Risk, Customer Experience, and Sales CRM. Security and Risk (JB0075102) is a Senior Staff Product Designer role covering SOC automation, threat intelligence, exposure management, and incident response. Confidence: high — employer-confirmed, active as of research cutoff.
Window
Four weeks old. Enterprise Senior Staff IC searches run 8–14 weeks. Pipeline is forming but not late. Several of the autonomous capabilities this role would design — the Tier 2 SOC AI Specialist and Vulnerability Resolution AI Specialist — ship in December 2026. The designer hired here sets conventions for pre-release products, which means you'd define the interaction model rather than inherit one.
Submit the formal application this week. Contextual LinkedIn message within 48 hours of submitting.
What this means for the design org
Amy Lokey left ServiceNow before these roles posted. Dantley Davis is now SVP of Design. Leadership transition plus a three-role cluster across different product areas reads as org-wide AI-design investment, not backfill. Security and Risk is the growth engine management keeps naming — $1B+ ACV, nearly 40% of net-new ACV growth per the job posting, appearing in 16 of the company's top 20 deals last quarter. Of the three mandates, this one has the strongest business case for design investment.
The design problem underneath the posting: ServiceNow is building autonomous security agents that construct multi-stage response plans, execute containment actions, and patch vulnerabilities with human analysts reviewing only higher-risk decisions. The designer owns three surfaces:
- Deciding which actions an agent may perform independently
- Making its reasoning and evidence inspectable
- Preserving accountable human approval for consequential actions
That maps to the Trust essay's five handoffs in a production security context. A SOC analyst sets the mandate, monitors agent activity, reviews the agent's constructed response plan, authorizes or rejects containment actions, and the system learns from the outcome. You've already published the framework. This role applies it to a specific domain.
Your angle
Lead with Trust essay + Carrier IQ. Support with Alibaba for enterprise scale.
Carrier IQ's provenance chain — where a user inspects agent-produced context before authorizing a consequential commitment — is the same interaction shape as an analyst reviewing an agent-constructed incident response before authorizing a blocking action. The artifact is the same; the framing sentence changes: one authorizes a policy bind, the other authorizes network containment. Both require the user to see what the agent found, evaluate whether the reasoning holds, and decide whether to let the action proceed.
Alibaba ($50B+ GMV, +20% daily transactions, -47% buyer security concerns) proves you operate at enterprise scale. It's credibility, not the lead.
Thermo Fisher (Product Design Director, BCG Digital Ventures; $20M+ margin, 6 pharma partners, 100% adoption) strengthens the angle if compliance and governance come up. Keep it in reserve.
Forward-looking artifact check: The Human-Agent System Design and Intent-Based Interaction artifact domains map to this mandate. Check the Build Queue. If either domain has a published or near-published artifact, link it in your outreach alongside the Trust essay. If neither is ready, move now with what you have. The Trust essay and Carrier IQ carry the positioning on their own, and the window is forming. Waiting for an artifact that isn't close risks missing the pipeline.
Who to contact
Primary: Basil Jose — leads product design for enterprise risk and operational sustainability at ServiceNow. His remit overlaps the risk portion of this role. He has posted about a "Build–Design–Ship–Learn" loop where teams supply AI with reasoning frameworks and design guardrails before building. That vocabulary is your hook. Confidence that he's the hiring manager: moderate. His scope covers risk but may not extend to the full Security Operations surface.
Secondary: Dantley Davis — SVP of Design. Has posted about building "professional-grade AI-native experiences" and Flow, ServiceNow's conversational service-desk experience. He's the global design executive. The purpose of a message to Davis is routing insurance. In a design org this large, your application can sit in a recruiter queue without the hiring manager knowing it exists. A message to Davis doesn't replace the Jose outreach — it ensures that if Jose isn't the decision-maker, or if the requisition routes through a different design leader, someone at the executive level has seen your name and the Trust essay link. Send it the same day as the Jose message, not as a follow-up.
Business-side reference: John Aisien — SVP and GM for Security & Risk. Do not contact for a design role. Know his name for interview prep.
Warm path: unconfirmed. Check your LinkedIn for mutual connections with Jose or Davis. The Issue 13 buyer sweep found that direct contact with a ServiceNow design leader (Carly Price, Customer Experience) resulted in a redirect to the formal application process. Expect the same here.
Route: formal application first. Contextual LinkedIn messages to Jose and Davis within 48 hours.
Outreach messages
Warm message to Basil Jose (use if a mutual connection surfaces):
I've been thinking about the trust architecture problem your Security and Risk team is designing — how an analyst evaluates an agent-constructed response plan before authorizing containment. I published a framework for exactly this class of problem: five handoffs that determine whether a user trusts an autonomous agent enough to let it act (junochen.com/trust-is-the-new-interface), and I built the decision-gate pattern in production at Agentic Labs for regulated-industry workflows. I applied for the Sr. Staff Product Designer role (JB0075102) and would welcome 20 minutes on how you're approaching the autonomous security surfaces. [Mutual connection] suggested I reach out.
Cold message to Basil Jose:
Your post about supplying AI with reasoning frameworks and design guardrails before building — that's the sequence I've been working through in production. I published a framework for it: five handoffs that determine whether a user trusts an autonomous agent enough to let it act (junochen.com/trust-is-the-new-interface). The decision-gate pattern maps to what your Security and Risk team is designing — an analyst reviewing an agent-constructed response plan before authorizing containment. I applied for the Sr. Staff Product Designer role (JB0075102) and would welcome 20 minutes on how you're thinking about the trust architecture for autonomous security workflows.
Cold message to Dantley Davis:
Your framing of professional-grade AI-native experiences is the right bar for what Security and Risk is building — autonomous agents that triage, contain, and remediate with human approval only at high-risk decision points. I've published a trust framework for this class of problem (junochen.com/trust-is-the-new-interface) and built regulated-industry agent workflows in production at Agentic Labs. I applied for the Sr. Staff role on the Security and Risk team and wanted to flag the application with your office.
ServiceNow's Horizon design system describes trustworthy AI as "transparent, traceable, and contestable." Those three words map to the Trust essay's output review and decision gate. Mirror them when adapting any message.
What not to say:
- Do not reference Amy Lokey or the leadership transition. It signals you're tracking internal churn rather than the design problem.
- Do not position yourself as a security-domain hire. You don't have security UX credentials. The angle is trust architecture for autonomous systems that happens to operate in a security context.
Cover letter draft
The hardest design problem in ServiceNow's autonomous security portfolio is the trust surface. When a Tier 2 SOC AI Specialist constructs a multi-stage response plan, executes containment, and escalates only higher-risk decisions, the designer owns three questions: what can the agent do without asking, how does the analyst inspect its reasoning, and where does accountability live when something breaks. Horizon calls this "transparent, traceable, and contestable." I've published a framework that operationalizes it.
"Trust Is the New Interface" (junochen.com/trust-is-the-new-interface) defines five handoffs — Intent-Setting, In-Progress, Output Review, Decision Gate, and Loop Feedback — that determine whether a user trusts an autonomous agent enough to let it act on their behalf. At Agentic Labs, I built Carrier IQ (junochen.com), an InsurTech quote-automation system where a user inspects agent-produced context before authorizing a policy bind — the same interaction pattern as an analyst reviewing an agent-constructed incident response before authorizing a blocking action. At Alibaba.com, I led the redesign of a $50B+ B2B platform as Head of Design and Research, North America, delivering +20% daily transactions and reducing buyer security concerns by 47%.
Most recently as Head of Product at TinyFish, I shipped an enterprise web agent platform from 0 to 1 within three months, working daily with agent traces, auditability, and governance challenges in production deployments. I moved to product to build AI-natively from zero. I returned to design because the problems I care about — consequential-action trust, human-agent decision surfaces, mandate maintenance in autonomous systems — are design problems, and I want to solve them in a vertical domain where the stakes justify the rigor.
The Security and Risk mandate is that domain. Portfolio and published work at junochen.com.
Resume emphasis guidance
- Lead: Trust essay + Agentic Labs (Carrier IQ). Published trust framework for autonomous agent systems + production proof in regulated-industry agent workflows.
- Second: Alibaba.com — Head of Design and Research, North America. $50B+ GMV, +20% daily transactions, -47% buyer security concerns.
- Third: Thermo Fisher mySupply (Product Design Director, BCG Digital Ventures). $20M+ margin, 6 pharma partners, 100% adoption. Regulated 0→1.
- TinyFish: Header line only — "Most recently, Head of Product at TinyFish (enterprise web agent platform, Series A). Shipped agentic platform 0→1 in 3 months."
- Trim: Move Equinox+ and Allē below the fold. Neither maps to this mandate.
- Red Cross: Keep if space allows — 6-system consolidation has a structural parallel to ServiceNow's platform thesis. Third-tier.
The non-obvious thing
ServiceNow's Horizon design system has already codified trust principles that map closely to the Trust essay's framework. Horizon describes agents as "planners, workers, and communicators." The communicator "explains activity, requests input, and returns to a person when the system cannot proceed safely." Its tool-output guidance says the interface should expose what the agent is reasoning about, doing, and finding, and anticipates an explicit supervised mode where a user tells the agent to confirm before acting. Its broader AI guidance names trustworthy AI as "transparent, traceable, and contestable."
Most candidates applying for this role will frame around security dashboards and SOC workflows. You can frame around the trust architecture in ServiceNow's own vocabulary, grounded in a published framework that extends where Horizon points. That's difficult to replicate in a portfolio walkthrough.
Warning signs
Equity ceiling. ServiceNow is $200B+ public. The posted base range is $190,900–$334,100 with equity, variable comp, and benefits. Levels.fyi reports ~$370K total comp for IC5 Senior Staff (crowdsourced, directional). Clears the $200K+ cash floor. The equity is RSUs in a mature public company. If pre-IPO upside is a gate for you, this role doesn't clear it.
Buyer opacity. Basil Jose is the closest public match but his confirmed scope is enterprise risk, not the full Security and Risk surface. You may be applying into a process where the decision-maker stays invisible until interview stage.
Pure IC scope. The posting has zero management language. That fits your craft-depth preference but confirm scope expandability in the first conversation.
Competitive landscape
Enterprise security UX specialist (confidence: moderate): They bring domain knowledge you lack. Unlikely to have a published trust framework for autonomous agent systems or production agentic AI experience. Your counter: the hard problem here is trust architecture for consequential-action delegation, not security domain expertise. Dashboard design is well-understood. The decision surface — where an analyst evaluates an agent's recommendation before authorizing action — is the new problem, and you've published a framework for it.
AI-native design leader (confidence: moderate): Stronger AI brand pedigree. A name from Anthropic or OpenAI carries weight with a hiring panel that wants credibility. But brand pedigree rarely comes with published framework-level thinking mapped to the hiring company's own design vocabulary. The Trust essay's five handoffs operationalize what Horizon calls "transparent, traceable, and contestable." That specificity — published, mapped to the mandate, using ServiceNow's own terms — is unlikely to walk in with a brand-name candidate.
Enterprise design director from ServiceNow's peer set (confidence: moderate): Platform familiarity and proven enterprise scale. They've designed for this buyer before. But scale credentials don't address the autonomous security mandate on their own. It requires agentic AI production experience and a framework for consequential-action delegation, and an enterprise director without production agent experience would be learning the problem on the job while you've already published the framework and shipped the pattern.
Post-outreach signals
Enterprise archetype. Expect 5–7 business days for initial response. Silence past 10 business days is normal — follow up at day 10 with a new signal hook (a product announcement, a Horizon blog post, a Davis post). Follow up again at day 20 if nothing. Enterprise silence is process.
If a recruiter screen lands within the first week, that's unusually fast — prioritize prep immediately. If the recruiter asks for a portfolio walkthrough, frame it as Trust essay → Carrier IQ → Alibaba, in that order, with Horizon vocabulary throughout.
If the role goes dark after an initial screen: one follow-up at day 7 referencing the conversation. No reply means the search is likely paused or filled. Move to Watch and monitor for a posting refresh.
- Horizon's supervised mode guidance: ServiceNow's agentic tool-output documentation anticipates an explicit supervised mode where users tell agents to confirm before acting — study this before any interview to speak their design vocabulary fluently.
- December autonomous capabilities launch: The Tier 2 SOC AI Specialist and Vulnerability Resolution AI Specialist are announced for expected availability in December 2026, which means the designer hired now is setting conventions for products that haven't shipped yet.
- Paul Hong's internal reach: A public post about ServiceNow's Threat Intelligence Security Center thanked Hong alongside Basil Jose as design leaders on that work — if Jose doesn't respond, Hong may be a secondary route into the Security Operations design surface.
- Armis and Veza integration scope: ServiceNow's $7.75 billion Armis acquisition and Veza acquisition connect assets, identities, and vulnerabilities through a common data graph — ask in conversation how this changes the design surface for Security and Risk workflows.