Scan window: October 6–16, 2026. Treat this queue as current through October 23. After that, re-verify everything below against employer career pages before you act on it.
This cycle: Four fresh signals, none at Act Now. The strongest ones each carry one open question (I call it the swing dimension: the rubric score that moves depending on the answer), and committing before you have that answer is premature. Three score high enough for Act Soon. One sits at Watch behind a threshold question that has to clear before scoring it properly is worth the effort. Every entry ends with a single diagnostic question, the one whose answer would most change the role's score. Ask that before anything else.
What's not here: Status updates on Amplitude, Figma, and previously scored roles (Databricks and others) are in Window Status. A fuller look at Peregrine as a company is coming in New on Radar. This piece is the decision layer only.
Verify dates at the source
Aggregator "new" labels are unreliable. Verify every posting date against the employer's own career page before acting.
This week an aggregator surfaced a Stripe Risk Designer posting labeled October 13, which would make it three days old. The employer-source date on Stripe's careers page is July 8. That's 100 days, far outside any actionable window. The Columbus Day weekend probably made it worse. Some aggregators batch-process over holidays and push stale postings into their "new" feed on the way out.
I verified every signal below against the employer's own career page. If you're scanning boards on your own, do the same before you spend an evening on anything an aggregator calls "new."
Act Soon
1. Peregrine — Staff Product Designer
What changed: Posted ~October 13. Three days old.
Why it matters: Peregrine builds AI software for law enforcement and public safety: cross-system data integration, identity resolution, investigative leads, and operational intelligence across agency data. More than 400 agencies use it. The company raised $250M in June at a $6.8B valuation, so it is scaling fast. The posting talks about strategy, mentorship, and systems-level design work, which tells me this role shapes how the design function operates and goes well beyond shipping screens.
Why Act Soon and not Act Now: It's day 3 of 21 and the highest-scoring role in this queue. What holds it back is the swing dimension: whether this designer owns AI-behavior decisions. A yes moves AI exposure from 2 to 3 and turns a strong conventional opportunity into a top priority. Get the answer to the diagnostic question below before you commit.
Landscape context: Peregrine is the most aggressively valued pure-play in public-safety AI. It competes near Axon (~$1.6B ARR) and Motorola Solutions ($11.7B revenue), both with much broader product stacks. A valuation like that against incumbents like those means investors are pricing in rapid expansion of design and product. Full company analysis is coming in New on Radar.
What the posting establishes: Senior IC scope, design-systems ownership, team-level influence.
What the posting leaves open: Whether this designer decides how the AI behaves (what the system surfaces, how it communicates confidence, when it defers to a human) or works downstream of those decisions, designing interfaces for outputs engineering controls. Nothing in the posting places AI-behavior authority with design. That absence is what I'd weight most.
Rubric snapshot:
- Company: 11 (+3 AI centrality, 3 stage/equity, 2 design ceiling, 3 trajectory)
- Role: 13 (3 comp, 3 scope, 3 craft, 2 AI exposure, 2 portfolio value)
- AI exposure is the swing dimension. It goes from 2 to 3 if the answer to the diagnostic question is yes.
Confidence: Moderate. Posting and company trajectory confirmed. Role scope inferred from posting language only.
Window: Day 3 of 21.
Diagnostic question: Does this designer own decisions about AI behavior — what the system surfaces, how it communicates confidence levels, when it requires human judgment — or does the designer work downstream of AI outputs controlled by engineering?
A yes makes this a role where the designer sets the line between what the AI decides and what a human decides. A no makes it a production design role with AI nearby. Either can be a good job. Only the yes changes your score.
2. ServiceNow — Sr. Staff Product Designer, AI/ML
What changed: The posting is 8 days old. The trigger is newer. On October 15, ServiceNow launched AI Passport, a product that creates verifiable records of what AI agents do inside enterprise systems and proves each action was authorized.
Why it matters: We rated this role Watch last cycle pending two conditions: confirmation that it reports into the design org under Dantley Davis, ServiceNow's SVP of Design, and confirmation that it leads design for an AI product with real decision authority. AI Passport didn't exist when we wrote that. If this role works on AI Passport, the second condition is met decisively, and the design problem maps straight onto the authorization-surface work you shipped at TinyFish. If it sits on a different product inside ServiceNow's segmented org structure, both conditions are still open.
Landscape context: AI Passport belongs to what I've been calling the authorization-surface category: products that govern whether an AI agent's action counts as legitimate inside an organization. Behavox's acquisition of Apiax and Mitratech's of BotDojo, covered in our enterprise AI capital analysis, are in the same territory. The design problem is how an AI action becomes institutionally valid — identity, delegated authority, policy enforcement, evidence trails. ServiceNow has the distribution to make the solution matter.
Rubric snapshot:
- Company: 9 (+2 AI, 2 stage, 2 design ceiling, 3 trajectory)
- Role: 12–15 depending on product assignment (3 comp, 2–3 scope, 3 craft, 2–3 AI exposure, 2–3 portfolio value)
Confidence: Moderate on the role and company. Low on the AI Passport connection. I'm inferring that from timing, and nothing confirms it.
Window: Day 8 of 21. Reach out this week. The AI Passport launch gives you a concrete, timely reason to make contact whether or not the role turns out to be connected to it.
Diagnostic question: Is this role designing for AI Passport, or for a different AI product within ServiceNow?
The answer moves AI exposure by a full point. It also decides whether your eventual case study is authorization surfaces for enterprise AI agents — distinctive and publishable — or something much harder to set apart.
3. Stripe — Staff Product Designer, Checkout
What changed: Posted ~October 9. Seven days old. (Verified at source. This is the real posting, separate from the mislabeled Risk Designer in the provenance warning above.)
Why it matters: The posting mentions AI only as a prototyping method, meaning the designer would use AI tools to build mockups. It says nothing about designing AI-driven product surfaces. Stripe, however, has already shipped AI into Checkout: payment methods reordered per shopper, personalized checkout layouts, authentication steps that adapt to risk. There's also Adaptive Pricing and an AI assistant in Checkout Studio.
So the posting treats AI as a tool, and the product treats it as a feature surface. Which of those this designer actually works in is what you need to find out.
Rubric snapshot:
- Company: 11 (+2 AI, 3 stage/equity, 3 design ceiling, 3 trajectory)
- Role: 11–13 (3 comp, 2 scope, 3 craft, 1–3 AI exposure, 2 portfolio value)
- AI exposure is the swing. 1 if AI is only a prototyping tool for the designer. 2 if the designer works alongside Checkout's AI features without owning them. 3 if the designer owns the surfaces where AI decisions become visible to shoppers and merchants.
Confidence: High that the posting and Stripe's AI features are real. Low on whether this designer owns those features.
Window: Day 7 of 21.
Diagnostic question: Does this designer own the product surfaces where Checkout's AI decisions appear — payment method ordering, adaptive authentication, merchant-facing AI controls — or does a separate team own those?
At AI exposure 1, this is a strong conversion-optimization role at a great company. At 3, you'd be designing how AI decisions become legible to two audiences (shoppers and merchants) on one of the highest-volume payment surfaces on the internet. Know which you're interviewing for before the first call.
Watch
Axon — Staff Product Designer, Prepared / Axon 911
What changed: Posted ~October 9. Prepared is Axon's AI product for 911 dispatch: call processing, responder routing, real-time decision support.
Why it's Watch, not Act Soon: A threshold question has to resolve first.
The posting requires US citizenship or permanent residency and cites CJIS, the FBI's Criminal Justice Information Services security policy. CJIS itself doesn't impose a blanket citizenship requirement. It mandates background checks, and the specifics vary by agency, data type, and access level. That leaves two possibilities:
- This designer directly accesses protected criminal justice data in production. Then the gate is probably firm and specific to the role.
- Axon applies the requirement company-wide across all Prepared roles. Then it's reasonable to ask whether exceptions exist for roles that never touch protected data directly.
The posting describes the design team as small and resource-constrained. The only design leader I can identify for Prepared is Naama Peleg. Axon's acquisition of Carbyne may have grown the combined Axon 911 design organization, but the total size isn't public. A small team can mean outsized impact or an unsupported grind. Gather that context if the threshold question clears; until then it's secondary.
Rubric snapshot:
- Company: 9 (+2 AI, 2 stage, 2 design ceiling, 3 trajectory)
- Role: 12 (2 comp, 2 scope, 3 craft, 2 AI exposure, 3 portfolio value)
What would escalate it: Confirmation that the citizenship gate comes from this role's specific data access, not a blanket company policy.
Diagnostic question: Is the citizenship/LPR requirement driven by this role's direct access to protected criminal justice data, or is it a blanket policy applied to all Prepared/Axon 911 positions regardless of data access?
Nothing to deprioritize this cycle. Status changes on previously scored roles are in Window Status.
- Stripe Link's access window: The October 3 hiring-manager promotion of Stripe's older Staff Product Designer, Link role hits the edge of its 15-day decay window on October 17, making this weekend the last moment that access signal carries weight.
- ServiceNow's design leadership layers: Ryan Fraser is publicly identified as VP of Design Studios & Intelligent Automation at a March 2026 AI Control Tower event, a named AI-adjacent design leader whose relationship to the Sr. Staff AI/ML role remains unconfirmed.
- Amplitude's vanished posting: The Head of Product Design URL now returns 404, which proves only that the public application surface disappeared — not whether the role filled, froze, or moved private.
- Figma entering verification territory: The Director, Product Design — AI & Context posting is now 24 days old on its September 22 Greenhouse timestamp, crossing from the active band into the 22–42-day range where direct verification outweighs further posting analysis.
