Scan: September 6–12, 2026
The post-Labor Day restart shows up in the data: four signals cleared the rubric this week, two of them new postings that went live once committees were back at their desks. Replit and Suno are the moves. Stripe has been sitting in route-find for three cycles and the recommendation changes today. Anthropic scores Act on the rubric and still isn't actionable — the Python requirement is a capability gap, explained in the Watch section.
Window Status Changes
Upgraded: Replit Watch → Act Now · Handshake new → Act Soon
Downgraded: Anthropic Evals & Prompts Act → Watch (capability gate) · Brex removed (pre-acquisition equity thesis retired)
Deprioritized: Adobe/Frame.io · Kong · Pinterest · Ramp · Maven — bottom of the piece
Act Now
Replit — Director of Product Design
What changed: Replit posted a Director of Product Design reporting to co-founder Haya Odeh, Head of Design. Base range disclosed at $275–350K. A named decision-maker, a named reporting line, and published comp from a single primary source — that's unusual.
Why it matters: Replit is a $9B AI-native company — Series D, $400M raised in March 2026, valuation tripled in six months, 60M+ users. The posting asks the Director to "operate two or three layers deeper in active initiatives" while Odeh holds strategic and quality authority. That's a real craft seat. Your trust ladder from "Trust Is the New Interface" — Watch, Verify, Delegate — maps onto the central UX problem of an AI writing code on someone's behalf.
Read the authority structure before you get excited. A co-founder who keeps creative authority and hires a Director to run operations can mean two very different jobs. The rubric scores a design-invested founder as a growth signal, and that holds when the Director has genuine input into what gets built. It stops holding when the Director exists to execute a vision they can't shape. Test which one this is before you're deep in process.
Opportunity verdict:
- Company: AI centrality 3 · Stage/equity 3 · Design ceiling 3 · Trajectory 3 = 12
- Role: Comp 3 · Scope 3 · Craft depth 3 · AI exposure 3 · Portfolio value 3 = 15
- Verdict: Act
Next-move type: Contact (Haya Odeh) + test the authority gate in conversation. The gate question: does the Director shape what gets designed, or only how it gets executed?
Confidence: High (posting, comp, reporting line, and funding all confirmed from primary sources)
Window: First 21 days. Act this week.
Move:
(a) Who: Haya Odeh, Co-Founder & Head of Design, Replit. She co-founded the company. The posting confirms she retains critique and quality authority while the Director manages day-to-day operations.
(b) Warm path: Cold.
(c) Multi-channel outreach plan:
- Engage with Odeh's recent content — a substantive interaction, not a like
- Connection request with tailored note (below)
- Full message after acceptance (below)
- Apply directly via Ashby in parallel
- One follow-up after 5 business days if no response
(d) Connection request (~285 chars): "Haya — I've been designing trust frameworks for agentic systems (junochen.com/trust-is-the-new-interface) and most recently shipped an enterprise agent platform as Head of Product at TinyFish. Your Director posting describes the design problem I want to solve next. Would love to connect."
(e) Full outreach message (260 words):
Haya,
The design problem at the center of Replit's agent experience is one I've been working on from two directions.
The first is conceptual. I published "Trust Is the New Interface" earlier this year, a framework for the handoff points where users decide how much agency to give an AI system. The five-handoff model came directly from watching enterprise users calibrate trust in agentic tools. Replit's agent faces the same calibration: when does a user review every line of generated code, when do they scan the diff, and when do they let the agent ship?
The second is operational. 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 the governance questions that surface when an AI acts on behalf of a user.
Before that, I spent seven years as a Product Design Director at BCG Digital Ventures building products in regulated, high-consequence domains: pharma supply chain (Thermo Fisher, $20M+ margin, 100% adoption), disaster relief disbursement (American Red Cross, $847K disbursed nationally), and consumer platforms at scale (Allē, 30M members, 3.2× redemption).
Your Director posting describes a role that runs the design function day-to-day while you hold strategic and quality authority. That division is one I've operated in before and want to operate in again, with an AI-native product that's changing how software gets built.
Portfolio and essay at junochen.com. Happy to share more over a call.
Juno
(f) What not to say: Don't position yourself as someone bringing design maturity or raising the bar for the function. Odeh built this org from founding. She wants an operational leader who can go deep in the work, not someone to teach the company what design is.
Interview prep flags:
- What to expect: Portfolio review weighted toward craft judgment. The posting values whiteboarding and implementation-level involvement, so expect a design exercise or critique session rather than a strategy presentation.
- Portfolio lead: "Trust Is the New Interface" to frame the conversation, then the Agentic Labs apps (Brand Pulse, Retail Velocity, Carrier IQ) as shipped proof.
- Key question to ask: "How do you and the Director divide decision authority on product direction versus execution quality?" That's the gate test. If the answer is "I set direction, you execute" with no room for the Director to influence what gets built, the scope score drops. An answer that describes shared influence at different altitudes means the role is what the posting says.
- Co-founder dynamic: Position as the operational leader who extends Odeh's reach into the work. Don't compete with her vision.
- Competitive differentiator: Production AI agent experience from TinyFish plus a published trust framework for agentic systems. Most candidates at this level have one or the other, and almost none have the conceptual frame that connects them.
Tier Playbook: Read AI-native playbook before outreach
Battlecard status: Battlecard needed — flag as candidate
Suno — Senior/Staff Product Designer
What changed: Suno launched v6 on September 9. The Senior/Staff Product Designer role remains posted at $215–324K plus equity. The Head of Product Design role Jack Brody posted roughly four months ago is gone from the public board. Filled quietly or paused — no public confirmation either way.
Why it matters: Two things to act on, decaying at different rates. The v6 launch is a product-specific outreach hook with about ten days of currency left, so use it now. The disappeared Head posting is the more durable intelligence: if it was filled, there's a new design leader you need to identify; if it was paused, Brody remains the route and the org-building mandate has probably changed shape. Either way the Senior/Staff seat at a company where the AI is the product holds its portfolio value.
Opportunity verdict:
- Company: AI centrality 3 · Stage/equity 2 (growth-stage, funding details unconfirmed this cycle) · Design ceiling 2 (leadership status unresolved) · Trajectory 3 = 10
- Role: Comp 2–3 ($215–324K disclosed; top of range clears the $250K threshold but equity terms are unconfirmed) · Scope 3 · Craft depth 3 · AI exposure 3 · Portfolio value 3 = 14–15
- Verdict: Act
Next-move type: Contact (Jack Brody) using the v6 trigger + route-find (confirm whether the Head of Design seat was filled)
Confidence: Moderate (role confirmed live, comp disclosed, Brody confirmed as the product-side route, design leadership status unresolved)
Window: The v6 hook is the constraint. Act by September 19.
Move:
(a) Who: Jack Brody, who publicly owned the Head of Product Design search and invited direct contact. Best available route until a new design leader is confirmed.
(b) Warm path: Cold.
(c) Multi-channel plan:
- Engage with Brody's content if something recent warrants a genuine reply — his feed runs mostly to hiring announcements rather than design thinking, so if nothing does, skip to step 2
- Connection request with the v6-specific note (below)
- Full message after acceptance (below)
- Apply directly via Suno careers in parallel
- Follow up in 5 business days
(d) Connection request (~275 chars): "Jack — v6 shifts the design problem at Suno toward how much creative control users retain versus delegate to the model. I've been designing trust frameworks for exactly this kind of human-AI handoff (junochen.com). Would love to talk about the Senior/Staff role."
(e) Full outreach message (215 words):
Jack,
The v6 release shifts the design problem at Suno in a direction I've been working on for two years.
As AI-generated music improves, the core design question moves from "can the model produce something good" to "how does the user decide what to keep, what to modify, and what to let the model handle." I wrote about this in "Trust Is the New Interface" (junochen.com), a framework for the handoff points where users calibrate how much agency to give an AI system.
I've shipped this kind of work in production. At Agentic Labs I built three AI products (Brand Pulse, Retail Velocity, Carrier IQ) where the design challenge was the same: how much does the human direct versus delegate? As Head of Product at TinyFish, I shipped an enterprise agent platform from zero to production in three months.
Before that, seven years building high-stakes products as a Product Design Director at BCG Digital Ventures, including Equinox+ (0→MVP in 3 months) and Allē (30M members, 3.2× redemption).
I'd love to hear how the design org is evolving and whether the Senior/Staff role is the right conversation.
junochen.com
Juno
(f) What not to say: Don't lead with enterprise or B2B framing. Suno is a consumer product. Lead with creative AI.
Interview prep flags:
- What to expect: Portfolio review with a product-thinking component. Suno is small and fast (66 open roles company-wide) and Staff designers own end-to-end surfaces, so prepare for an exercise about creative tools rather than enterprise workflows. Panel composition is uncertain given the unresolved leadership status; you may meet Brody, a recently hired Head of Design, or both.
- Portfolio lead: "Trust Is the New Interface," then the Agentic Labs apps, then Equinox+ for consumer 0→1 speed.
- Key question: "With the Head of Product Design search — is there a design leader in place now, or is this team still reporting into product?" That resolves the routing question and surfaces the org structure in one move.
- Leadership dynamic: Brody publicly owned the Head of Design search, which means he held hiring authority over the function. If someone has since been hired, you'll be interviewing with a person whose evaluation criteria you couldn't research. Say so directly and ask about their vision for the team. If the search was paused and Brody still runs design, position as someone who strengthens the function without needing the leadership title to do it.
- Competitive differentiator: The trust and delegation framework applied to creative AI. Most candidates will talk about interface craft; you can talk about the structure of human-AI co-creation and point to production work behind it.
Tier Playbook: Read AI-native playbook before outreach
Battlecard status: Battlecard needed — flag as candidate
Act Soon
Stripe — Senior Staff Product Designer, Data & AI
What changed: The posting has been live for three cycles with no new information. The posting remains at $210–377K, and the design buyer for Data & AI is still unresolved (Issue 8, Issue 9, Issue 10).
The posting is crossing the 21-day threshold. Three cycles of route-find with nothing to show means the approach was wrong. Stop waiting for the design buyer to surface and apply directly.
Reach Eeke de Milliano, product leader for Data Products and publicly recruiting for her area, with a product-informed message. Reach Yuliya Gorlovetsky on the design side. Both in parallel with the application.
Opportunity verdict:
- Company: AI centrality 2 · Stage/equity 2 · Design ceiling 3 · Trajectory 3 = 10
- Role: Comp 3 · Scope 3 · Craft depth 3 · AI exposure 2 · Portfolio value 3 = 14
- Verdict: Act
Next-move type: Apply directly + contact the product-side route (de Milliano) + contact the design-side route (Gorlovetsky). What's blocking you now is posting age, not missing routing intelligence.
Connection request to de Milliano (~290 chars): "Eeke — I see you're building the Data Products org at Stripe. I led design for Alibaba.com's B2B platform ($50B+ GMV) and most recently shipped an enterprise agent platform at TinyFish. The Senior Staff Data & AI role maps to problems I've been solving. Would love to connect."
Full outreach to de Milliano (175 words):
Eeke,
The Data & AI scope at Stripe — Sigma, Data Pipeline, and how agents interact with business data — combines two areas I've spent the last several years on.
At Alibaba.com, I led design and research for a B2B platform serving $50B+ in GMV, where the core challenge was making complex data legible and actionable for business users across markets. As Head of Product at TinyFish, I shipped an enterprise web agent platform from zero to production in three months, including the data attribution and auditability surfaces that enterprise buyers require.
My published work at Agentic Labs (junochen.com) shows three AI products where the design problem was how users supervise, correct, and trust automated decisions — the same problem that surfaces when agents query and act on financial data.
I'd welcome the chance to talk about how the Data & AI design team is structured and what the Senior Staff role looks like day to day.
junochen.com
Juno
Gorlovetsky — design-side route: Yuliya Gorlovetsky was identified in Issue 8 as a senior product-design contact at Stripe. I could not confirm her current title, LinkedIn URL, or tenure from public sources this cycle. If you can locate the profile, use this:
Connection request to Gorlovetsky (~280 chars): "Yuliya — I'm looking at the Senior Staff Product Designer role in Data & AI at Stripe. I led design for Alibaba.com ($50B+ GMV) and have been building AI products at Agentic Labs (junochen.com). Would love to learn more about the team and how the role fits the design org."
Interview prep: Lead with Alibaba for enterprise scale and data complexity, then Agentic Labs for AI-native product work. Ask how the Data & AI design team interfaces with Stripe's broader design system.
Tier Playbook: Read Enterprise platform playbook before outreach
Battlecard status: Battlecard exists (updated through Issue 10)
Handshake — Staff Product Designer, Student AI Agent
New addition. It clears on AI exposure quality — human-agent handoff is the stated design problem — and on active design leadership investment, with a VP of Design confirmed hiring.
What changed: Staff Product Designer, Student AI Agent posted with explicit human-agent handoff language. May-Li Khoe, VP of Design, is the confirmed senior design leader and is actively building the team. Whether she's the hiring manager for this particular requisition is unresolved; the posting names no manager, and a Design Director layer may sit between Khoe and the seat.
Opportunity verdict:
- Company: AI centrality 2 · Stage/equity 2 · Design ceiling 3 · Trajectory 2 = 9
- Role: Comp 2 ($190–240K disclosed; the top of the band only just reaches tier 2) · Scope 2 · Craft depth 3 · AI exposure 3 · Portfolio value 2 = 12
- Verdict: Act (borderline — company 9, role 12)
This clears the threshold and sits right on the line. The AI exposure is real: a "Student AI Agent" with handoff language in the posting is a genuine design problem, not a bolted-on feature. Portfolio value is moderate. One outreach to Khoe, aimed at resolving the routing question and testing whether the scope matches the language. Don't build a campaign around it.
Next-move type: Route-find (confirm Khoe is the hiring manager or identify who is) + apply directly via Ashby in parallel.
Connection request to Khoe (~275 chars): "May-Li — the Student AI Agent role caught my attention. I've been designing trust frameworks for human-agent handoffs (junochen.com/trust-is-the-new-interface) and shipped an enterprise agent platform at TinyFish. Are you the right person to talk to about this role?"
Full outreach to Khoe (165 words):
May-Li,
The Student AI Agent role describes a design problem I've been working on across several products: how users build trust in an AI system that acts on their behalf, and where the handoff points between human judgment and agent action should sit.
I published a framework for this in "Trust Is the New Interface" (junochen.com), and I've shipped it in production — three AI products at Agentic Labs where the core design challenge was calibrating user control over automated decisions, and an enterprise agent platform at TinyFish that I took from zero to production in three months as Head of Product.
I'm curious whether this role reports into your office directly or through a Director in the student-product org, and whether the scope is as agent-forward as the posting language suggests.
Portfolio at junochen.com. Happy to talk further.
Juno
Interview prep: Lead with "Trust Is the New Interface" and Agentic Labs. The handoff language in the posting is your entry point.
Tier Playbook: Read Growth-stage platform playbook before outreach
Battlecard status: Battlecard needed — flag as candidate
Watch
Anthropic — Product Designer, Evals & Prompts. $305–385K. Company 12, role 14, which is Act by the rubric. The posting requires production Python and evaluation pipeline experience, and that's a capability gap rather than a portfolio gap — the experience doesn't exist, so there's no artifact you can build to close it. Anthropic has no other Product Designer roles on the public board right now. Check weekly; a product design posting without the engineering gate is an immediate Act Now.
Tier Playbook: AI-native (when a qualifying role appears)
Deprioritize
- Adobe / Frame.io: Filled. Remove.
- Kong: Posting stale, 43+ days. Remove.
- Pinterest: Posting stale. Remove.
- Ramp: No new design leadership signal, posting stale. Revisit if a Head of Design posting or a design-leader hire surfaces.
- Maven Clinic: Posting stale. Remove.
- Brex: Pre-acquisition equity thesis retired. Remove unless a post-acquisition design leadership role surfaces with confirmed scope and comp.
- Suno's label deals and litigation risk: Axios reported that Suno's v6 launch reflects a shift toward licensed, revenue-sharing arrangements with Warner, Believe, and Merlin, which changes the product's legal exposure and may reshape the design mandate around provenance and rights attribution.
- Cognition's $2B raise with no design seat: Cognition reportedly raised over $2 billion at a $48 billion valuation on September 9, but no Director+ or Staff design role has surfaced — worth monitoring weekly because a company at that scale will eventually need one.
- OpenAI's product reorg changes the routing: WIRED reported that Greg Brockman took product-strategy responsibilities while Thibault Sottiaux assumed ownership of core product and platform work including Codex, which means the Codex design-lead route may have shifted away from the previously identified path.
- ServiceNow's design hiring cluster: Four senior design roles posted within a week — the September 6 ITSM Director plus three September 2 openings across Security, CRM, and Partner Experience — suggests a coordinated design-org expansion worth watching for a leadership-level posting.