Portfolio Playbook — Issue 1 | On Deck

Portfolio Playbook — Issue 1 | On Deck

OpenAI Triage

Skip the posting, keep the door

Skip the posting, keep the door

The OpenAI Product Design Manager role is still live. It was posted April 15. That's 76 days ago, 34 days past the freshness window, with no reposting evidence. The URL resolving does not mean the search is active.

The portfolio fit is real. Payments and Identity & Access maps cleanly to Alibaba's trust architecture. Developer tools maps to the essay and Agentic Labs. Cross-surface coherence is your Alibaba story told three ways. You would be strong in this room.

But the room may not exist anymore. And "Product Design Manager" scoped to 5–10 designers is a leveling question you'd need to resolve before investing contact capital here.

Your five primary rooms are fresher and level-matched. Spend there first.

What OpenAI warrants right now is the essay, not an application. If you have a warm intro to anyone on the design team, use it. The hook is the framework. "I published a piece on the human-agent trust problem. I'd value hearing how your team thinks about the same questions." That kind of conversation doesn't depend on any single Ashby link staying open.

Watch for a fresh Head of Design or Senior Director posting. When it appears, move same-day. You already have a first-contact position most candidates at that level won't.

OpenAI Triage

Skip the posting, keep the door

Skip the posting, keep the door

The OpenAI Product Design Manager role is still live. It was posted April 15. That's 76 days ago, 34 days past the freshness window, with no reposting evidence. The URL resolving does not mean the search is active.

The portfolio fit is real. Payments and Identity & Access maps cleanly to Alibaba's trust architecture. Developer tools maps to the essay and Agentic Labs. Cross-surface coherence is your Alibaba story told three ways. You would be strong in this room.

But the room may not exist anymore. And "Product Design Manager" scoped to 5–10 designers is a leveling question you'd need to resolve before investing contact capital here.

Your five primary rooms are fresher and level-matched. Spend there first.

What OpenAI warrants right now is the essay, not an application. If you have a warm intro to anyone on the design team, use it. The hook is the framework. "I published a piece on the human-agent trust problem. I'd value hearing how your team thinks about the same questions." That kind of conversation doesn't depend on any single Ashby link staying open.

Watch for a fresh Head of Design or Senior Director posting. When it appears, move same-day. You already have a first-contact position most candidates at that level won't.

TAKE NOTE

Posted: April 15, 2026. 76 days old.

Freshness threshold: 42 days. Exceeded by 34. No repost, no recruiter signal.

Title: Product Design Manager, 5–10 designers. Below Head of Design targeting.

Portfolio match: Strong on content. Alibaba trust architecture, Trust essay, Agentic Labs all map. Fit is not the issue.

Problem: Staleness + leveling + opportunity cost. Five fresher rooms open.

Do not: Cold-apply or cold-outreach to this posting before exhausting Suno, Capital One, Headway, Ramp, Gusto.

Do: Use the Trust essay as a warm-intro opener to OpenAI design leadership, independent of this role.

If you act anyway: Essay first, Alibaba second. Name Payments and Identity & Access specifically. Under 100 words. Do not lead with Thermo Fisher or Red Cross for this audience.

Watch for: Any new OpenAI design leadership posting. Respond same-day.

PART ONE

CS-01 Alibaba Teaser — What Ramp and Capital One Buyers See in 30 Seconds

Juno's Alibaba teaser has the structural prerequisites: mandate-forward tab title, four outcome metrics before scroll, gated CTA. Three problems are still working against it. A massively oversized OG image is breaking every Slack and LinkedIn unfurl. The hero H1 uses narrative language where it needs mandate language. And a 16-row component rack is consuming half the scroll depth, quietly reclassifying the candidate from "trust-architecture leader" to "component-library builder." We audit each layer through two specific buyer lenses — a Ramp design director scanning for trust at transaction scale, and a Capital One leader scanning for org-transformation evidence — because they pattern-match differently against the same page. Hiring managers clear tabs before long weekends. Fix the metadata today.

CS-01 Alibaba Teaser — What Ramp and Capital One Buyers See in 30 Seconds

PART TWO

Your Thermo Fisher Teaser Is Hiding the Diagnosis That Both Buyers Need to See

The Thermo Fisher case study has a structural diagnosis that maps cleanly to two live regulated-platform roles. Exceptions caught at the delivery gate instead of upstream. That insight transfers directly to a Gusto payroll buyer and a Headway insurance-platform buyer. But the page title says "Pharma Supply Chain," the H1 makes the buyer do the translation, and a thirteen-group component grid buries the CTA under teaser-inappropriate density. Six fixes, sequenced by impact, with a hard deadline: most hiring managers go dark for the Fourth after Wednesday evening.

Your Thermo Fisher Teaser Is Hiding the Diagnosis That Both Buyers Need to See

PART THREE

CS-03 Red Cross Teaser Page Audit — Mandate Before Mission

Juno's Red Cross teaser page has the right evidence: GM-level role line, six-system consolidation, national deployment in six months, $847K processed. The problem is where it fires. The H1 sets a humanitarian frame before any platform signal arrives, and a healthcare-platform hiring manager scanning for regulated-environment leadership will file the case study as a nonprofit impact story and move on. The metrics, the multi-role architecture, the deployment speed — all present, all buried. Six fixes, three of them under fifteen minutes. The page needs a new first sentence. The evidence is already there.

CS-03 Red Cross Teaser Page Audit — Mandate Before Mission

PART FOUR

CS-04 Equinox+ Teaser Audit — Suno Buyer Lens

The Equinox+ teaser page has the architectural insight Suno would hire for: instructor loyalty driving navigation architecture, five brands unified in 90 days, retention data shaping core product decisions. Every one of those signals lives below a fitness-consumer frame that registers as domain mismatch before any of them land. Six audit dimensions, each with specific replacement copy you can implement tonight. The highest-leverage fix takes five minutes and zero design changes.

CS-04 Equinox+ Teaser Audit — Suno Buyer Lens

CS-06 Allē Teaser Audit — The Page Does Its Job, the Homepage Card Doesn't

The Allē teaser page is fixed. Meta title, dual-surface architecture, outcome metrics — all resolved. But the homepage card still describes a consumer-loyalty case with a "Dual Surface" tag doing all the structural work. A Headway buyer scanning for provider-surface experience never clicks. A Ramp buyer looking for systems thinking sees a single-surface case and moves on. The page tells the right story, but nobody gets to the page through a card that undersells it. With Independence Day compressing this week to two usable outreach days, the card is the only fix that matters before Thursday.

PART ONE

CS-01 Alibaba Teaser — What Ramp and Capital One Buyers See in 30 Seconds

Juno's Alibaba teaser has the structural prerequisites: mandate-forward tab title, four outcome metrics before scroll, gated CTA. Three problems are still working against it. A massively oversized OG image is breaking every Slack and LinkedIn unfurl. The hero H1 uses narrative language where it needs mandate language. And a 16-row component rack is consuming half the scroll depth, quietly reclassifying the candidate from "trust-architecture leader" to "component-library builder." We audit each layer through two specific buyer lenses — a Ramp design director scanning for trust at transaction scale, and a Capital One leader scanning for org-transformation evidence — because they pattern-match differently against the same page. Hiring managers clear tabs before long weekends. Fix the metadata today.

CS-01 Alibaba Teaser — What Ramp and Capital One Buyers See in 30 Seconds

PART TWO

Your Thermo Fisher Teaser Is Hiding the Diagnosis That Both Buyers Need to See

The Thermo Fisher case study has a structural diagnosis that maps cleanly to two live regulated-platform roles. Exceptions caught at the delivery gate instead of upstream. That insight transfers directly to a Gusto payroll buyer and a Headway insurance-platform buyer. But the page title says "Pharma Supply Chain," the H1 makes the buyer do the translation, and a thirteen-group component grid buries the CTA under teaser-inappropriate density. Six fixes, sequenced by impact, with a hard deadline: most hiring managers go dark for the Fourth after Wednesday evening.

Your Thermo Fisher Teaser Is Hiding the Diagnosis That Both Buyers Need to See

PART THREE

CS-03 Red Cross Teaser Page Audit — Mandate Before Mission

Juno's Red Cross teaser page has the right evidence: GM-level role line, six-system consolidation, national deployment in six months, $847K processed. The problem is where it fires. The H1 sets a humanitarian frame before any platform signal arrives, and a healthcare-platform hiring manager scanning for regulated-environment leadership will file the case study as a nonprofit impact story and move on. The metrics, the multi-role architecture, the deployment speed — all present, all buried. Six fixes, three of them under fifteen minutes. The page needs a new first sentence. The evidence is already there.

CS-03 Red Cross Teaser Page Audit — Mandate Before Mission

PART FOUR

CS-04 Equinox+ Teaser Audit — Suno Buyer Lens

The Equinox+ teaser page has the architectural insight Suno would hire for: instructor loyalty driving navigation architecture, five brands unified in 90 days, retention data shaping core product decisions. Every one of those signals lives below a fitness-consumer frame that registers as domain mismatch before any of them land. Six audit dimensions, each with specific replacement copy you can implement tonight. The highest-leverage fix takes five minutes and zero design changes.

CS-04 Equinox+ Teaser Audit — Suno Buyer Lens

CS-06 Allē Teaser Audit — The Page Does Its Job, the Homepage Card Doesn't

The Allē teaser page is fixed. Meta title, dual-surface architecture, outcome metrics — all resolved. But the homepage card still describes a consumer-loyalty case with a "Dual Surface" tag doing all the structural work. A Headway buyer scanning for provider-surface experience never clicks. A Ramp buyer looking for systems thinking sees a single-surface case and moves on. The page tells the right story, but nobody gets to the page through a card that undersells it. With Independence Day compressing this week to two usable outreach days, the card is the only fix that matters before Thursday.

PART ONE

CS-01 Alibaba.com — Interview-Panel Stress Test

Juno's Alibaba case has strong research inputs, clear design moves across three sprints, and specific outcome metrics. It proves she can do the work. The cost of a decision, the path she rejected, the thing she traded away — none of that appears. A skeptical Director+ panelist will read a redesign story and keep waiting for the leadership story underneath it. Six dimensions audited against what that panelist would probe. The fix is five or six sentences distributed across the case, written before panels resume the week of July 7.

CS-01 Alibaba.com — Interview-Panel Stress Test

PART TWO

Full Case Audit: CS-02 Thermo Fisher mySupply — Regulated-Platform Buyer Lens

Your mySupply case delivers the full HTML to any requester before the password overlay runs. Same vulnerability as the essay. Worse here, because the case is about regulated access architecture and the gate protecting it is cosmetic. Fix before sharing in any interview loop — you have until Thursday if you're targeting post-holiday conversations. Beyond the access defect: a full audit of how this case reads to a Gusto or Headway panel evaluating 0→1 regulated-platform judgment. The module mapping is strong. The tradeoff reasoning is where the case leaves too much to inference.

Full Case Audit: CS-02 Thermo Fisher mySupply — Regulated-Platform Buyer Lens

PART THREE

CS-03 Red Cross Full Case Audit — What a Headway Panel Will See and What They'll Miss

Juno's Red Cross case study contains the proof a Headway panel needs: a 0→1 build replacing six legacy systems under federal constraints, shipped into active surge in six months with seven people. The problem is where that proof sits. GM-level scope hides behind a humanitarian frame. A three-role architecture that maps directly to healthcare multi-role workflows is demonstrated but never named as the hard problem. Surge-readiness is claimed without tracing which decisions produced it. Seven structural fixes, prioritized by day, with rewrite candidates for each.

CS-03 Red Cross Full Case Audit — What a Headway Panel Will See and What They'll Miss

PART FOUR

Full Case Audit: Equinox+ (CS-04) — Evaluated for a Suno Interview Panel

Juno's Equinox+ case has the right structural parallel to Suno's product problem: multiple content formats, retention driven by behavior rather than taxonomy, an IA derived from data instead of inherited. That parallel is why you'd lead with this case. But a Suno panel tests whether you can prove architectural reasoning from behavioral signal, and the case's strongest analytical move—retention data reshaping the navigation model—is under-evidenced at the exact point where evidence matters most. The July 4th window gives you three to five days to fix four things before this goes in front of a panel evaluating exactly that capability.

Full Case Audit: Equinox+ (CS-04) — Evaluated for a Suno Interview Panel

Full Case Audit: CS-06 Allē — Dual-Surface Platform Read for Headway/Ramp Panels

Allē is a dual-surface loyalty case: consumer app and provider dashboard, one pharmaceutical client, six design decisions in a clean A·01–B·03 format. It's also the case most likely to land in front of a Headway or Ramp panel this cycle. The format is a structural strength. The gaps are specific: no unified premise before the tracks split, no rejected alternatives named, no regulatory constraint treated as design material, and a metric ambiguity in the hero that a data-literate interviewer will catch before you can explain it. Six dimensions audited, prioritized for someone with a long weekend and fixes due Monday.

PART ONE

CS-01 Alibaba.com — Interview-Panel Stress Test

Juno's Alibaba case has strong research inputs, clear design moves across three sprints, and specific outcome metrics. It proves she can do the work. The cost of a decision, the path she rejected, the thing she traded away — none of that appears. A skeptical Director+ panelist will read a redesign story and keep waiting for the leadership story underneath it. Six dimensions audited against what that panelist would probe. The fix is five or six sentences distributed across the case, written before panels resume the week of July 7.

CS-01 Alibaba.com — Interview-Panel Stress Test

PART TWO

Full Case Audit: CS-02 Thermo Fisher mySupply — Regulated-Platform Buyer Lens

Your mySupply case delivers the full HTML to any requester before the password overlay runs. Same vulnerability as the essay. Worse here, because the case is about regulated access architecture and the gate protecting it is cosmetic. Fix before sharing in any interview loop — you have until Thursday if you're targeting post-holiday conversations. Beyond the access defect: a full audit of how this case reads to a Gusto or Headway panel evaluating 0→1 regulated-platform judgment. The module mapping is strong. The tradeoff reasoning is where the case leaves too much to inference.

Full Case Audit: CS-02 Thermo Fisher mySupply — Regulated-Platform Buyer Lens

PART THREE

CS-03 Red Cross Full Case Audit — What a Headway Panel Will See and What They'll Miss

Juno's Red Cross case study contains the proof a Headway panel needs: a 0→1 build replacing six legacy systems under federal constraints, shipped into active surge in six months with seven people. The problem is where that proof sits. GM-level scope hides behind a humanitarian frame. A three-role architecture that maps directly to healthcare multi-role workflows is demonstrated but never named as the hard problem. Surge-readiness is claimed without tracing which decisions produced it. Seven structural fixes, prioritized by day, with rewrite candidates for each.

CS-03 Red Cross Full Case Audit — What a Headway Panel Will See and What They'll Miss

PART FOUR

Full Case Audit: Equinox+ (CS-04) — Evaluated for a Suno Interview Panel

Juno's Equinox+ case has the right structural parallel to Suno's product problem: multiple content formats, retention driven by behavior rather than taxonomy, an IA derived from data instead of inherited. That parallel is why you'd lead with this case. But a Suno panel tests whether you can prove architectural reasoning from behavioral signal, and the case's strongest analytical move—retention data reshaping the navigation model—is under-evidenced at the exact point where evidence matters most. The July 4th window gives you three to five days to fix four things before this goes in front of a panel evaluating exactly that capability.

Full Case Audit: Equinox+ (CS-04) — Evaluated for a Suno Interview Panel

Full Case Audit: CS-06 Allē — Dual-Surface Platform Read for Headway/Ramp Panels

Allē is a dual-surface loyalty case: consumer app and provider dashboard, one pharmaceutical client, six design decisions in a clean A·01–B·03 format. It's also the case most likely to land in front of a Headway or Ramp panel this cycle. The format is a structural strength. The gaps are specific: no unified premise before the tracks split, no rejected alternatives named, no regulatory constraint treated as design material, and a metric ambiguity in the hero that a data-literate interviewer will catch before you can explain it. Six dimensions audited, prioritized for someone with a long weekend and fixes due Monday.