Sources: Ashby, Greenhouse, Lever, Workday, LinkedIn Jobs, Built In, company career pages, VC portfolio boards. Every previously cited signal re-verified against its decay window.
Sequencing logic this cycle: Decision-rights density is the tiebreaker when posting age and rubric scores run close. That means: how explicitly does the posting language name trust, override, approval, correction, or reversal surfaces? Not inferred from a product blog or extrapolated from a roadmap slide. In the posting itself.
Three signals approaching decay thresholds. Two new or newly clarified. Three done.
Act Now
Amplitude — Head of Product Design
Act | Day 17 | Confidence: High (Ashby publishedAt confirmed, CPO tenure-to-posting gap mapped in prior analysis)
Decision-rights surface: Wave surfaces agent-generated growth opportunities to product teams. Someone has to decide whether to act on what the system found. That commitment point is the design problem this role owns.
What changed: No repost, no language revision since day 12. That's a positive signal. The committee hasn't recalibrated. The original mandate holds.
Why it matters: Conviction is stable. The hiring committee knows what it wants. Four days remain in the 0–21 day hot band. After July 28, the competitive field fills and your timing edge erodes.
Status movement from July 19: Was day 12. Advancing through hot window on schedule.
Tier Playbook: Read Growth-stage platform playbook before outreach.
HackerOne — Director, AI Product Design
Act / Verify | Day ~10–14 (estimated; no canonical first_published date) | Confidence: Moderate (aggregator age evidence only; status conflict flagged)
Decision-rights surface: The strongest in this scan, and it isn't close. The posting names agent-to-agent interaction, human-in-the-loop oversight, transparency, and accountability for AI-native security products. Concretely: a security team receives continuously monitored evidence from an automated system. Can they trust it enough to act, escalate, or dismiss? False negatives here aren't UX friction. They're breaches.
What changed: New entry. LinkedIn shows "2 weeks ago." Built In shows "5 days ago" with $243K–$300K comp. Reports to CPO. But the role does not appear in HackerOne's current Ashby board API, while the direct Ashby URL remains indexed. Status conflict: delisted for revision, quietly filled through pipeline, or mis-indexed. I can't tell which from public signal alone.
Why it matters: If live, this is the best decision-rights match in the queue. Director level, CPO buyer, and the language doesn't gesture at AI trust generically. It specifies the interaction model and the accountability structure.
Window: If live, estimated 7–11 days remaining in hot band.
Verification step: Check whether the direct Ashby URL resolves to an active application flow. If yes, treat as day 10–14 and move. If closed or filled, retire immediately.
Tier Playbook: Read Growth-stage platform playbook before outreach. HackerOne is a security platform building AI product capabilities, not an AI-native company. The role is deeply AI-focused, so the AI-native playbook has relevant interview prep, but company-level preparation follows the growth-stage pattern. Battlecard candidate.
Vanta — Head of Design
Verify | Day 18 | Confidence: High on posting, Moderate on mandate (Ashby publishedAt July 6 confirmed)
Decision-rights surface: Continuous compliance monitoring. Vanta's automated systems tell a customer they're compliant or flag a gap. The design of that surface determines whether the customer trusts the finding, investigates, or ignores it. Binary. High-consequence.
What changed: The succession question remains unanswered. Vanta's design careers page still lists Deb Kawamoto as VP of Design while the VP-level Head of Design role stays live. Three readings: successor search (Kawamoto departing, page not updated), parallel track (Head of Design reports to Kawamoto), or restructuring. Each implies a different mandate and a different buyer.
Until you know which, you're positioning blind.
Window: Three days remain in hot band. Verify this week or accept the extended-window penalty. One warm-intro conversation resolves this.
Status movement from July 19: Was day 13 with succession ambiguity flagged. Ambiguity unresolved.
Tier Playbook: Read Growth-stage platform playbook before outreach.
Act Soon
Capital One — AI in Experience Design (Director-level)
Verify | Day ~29 (estimated; first surfaced late June, exact first_published unavailable) | Confidence: Moderate
Decision-rights surface: When Capital One's AI systems recommend a financial product, adjust a credit decision interface, or automate a customer service flow, the approval, correction, and reversal surfaces determine whether customers and regulators trust the outcome. Regulated financial services.
What changed: The visibility question from prior cycles is resolved. Role confirmed live. What remains open: is this an org-transformation mandate (redesigning how design works across Capital One's AI initiatives) or a product-ownership mandate (owning specific AI product surfaces)? That distinction determines which version of your background to lead with.
Window: Extended window, estimated ~13 days remaining before the 42-day threshold. Enterprise cadences justify continued investment past the standard 21-day mark, but the clock is real.
Status movement from July 19: Upgraded from ambiguous visibility to confirmed live. Verb shifted from Act to Verify because the mandate question needs answering before you commit full preparation effort.
Tier Playbook: Read Enterprise platform playbook before outreach.
Maven Clinic — Design Leadership
Act | Day 38 (carried forward from prior cycle tracking; original posting evidence not independently re-verified this cycle) | Confidence: Moderate
Decision-rights surface: Clinical decision support. Maven surfaces care recommendations, matches patients to providers, flags health risks. The design of those surfaces determines whether clinicians and patients trust the system's judgment. Under-trust means the system gets ignored. Over-trust means errors propagate into care decisions. Healthcare, regulated, high-consequence.
What changed: Nothing. No repost. The signal continues aging without refresh.
Window: The 42-day decay threshold hits around July 28. This is the last Act window. After this cycle, the signal degrades to Watch or Retire unless a repost refreshes it. Move now or let it go.
Status movement from July 19: Continued aging. No new signal.
Tier Playbook: Read Healthcare/Regulated playbook before outreach. Battlecard candidate.
Watch
Brex — Staff Product Designer, AI | Watch | Day 16 | Confidence: High (first_published July 8 confirmed). Posting names delegation, supervision, review, and correction for AI doing real financial work. Staff IC, strong AI centrality, still in hot band. IC track warrants monitoring over immediate investment. Brex's current corporate status and equity structure need Battlecard-level verification before escalation. Escalation trigger: evidence that the role reports into a design leader with strategic influence, or scope expansion beyond a single product surface. Tier Playbook: Read AI-native playbook. Battlecard candidate.
Adobe — Director of Product Design, GenStudio | Watch | Day 30+ (Workday reports "30+ Days Ago"; exact first_published unavailable). Posting describes AI-first agentic workflows where marketers interact with chat, editor, and agent surfaces. The design problem is autonomy boundaries: when does the agent act versus when does the marketer retain control? LinkedIn repost activity suggests active sourcing despite age. Enterprise cadences run longer. Escalation trigger: language revision (first search failed, committee recalibrated) or new VP/CPO hire resetting the evaluation window. Tier Playbook: Read Enterprise platform playbook.
Deprioritize / Retire
Headway — Design Director, Provider Experience | Retire. Gone from Headway's careers index and Ashby API. Third-party mirrors show original posting June 4–5. Day 49–50. Was flagged as approaching staleness July 10. Disappearance from official sources confirms it. Pause. Revisit only on repost with revised language.
Ramp — Director, Product Design | Retire. Was day 32 on July 10. Now day 46+. Past the 43-day stale threshold. No repost. Remove from active queue.
Suno — Head of Product Design | Retire. Was already stale at 70 days on July 3. Day 90+. Remove.
- Abridge's auditable AI language: Their Staff Product Designer posting names "Linked Evidence" and purpose-built auditability for AI-generated clinical summaries, making it a strong healthcare trust signal worth monitoring even at IC level.
- Fieldguide's audit workflow fit: This Staff Product Designer role focuses on AI-assisted audit workflows with regulatory constraints and ambiguous decision surfaces, which maps closely to the Thermo Fisher and Alibaba proof pillars.
- Rubrik's Director repost question: The Director, Product Design role frames cyber resilience around guardrails, monitoring, auditing, and undoing agentic mistakes, but older posting evidence means it needs fresh verification before re-entering the active queue.
- Eltropy's agentic financial platform: Their Director, Design posting asks for human-AI collaboration, trust, transparency, and control in an agentic AI platform for financial institutions, though onsite Santa Clara and a small India-based team may affect fit.