Start with Render and Slack. Both buyers publicly asked candidates to reach out. The other four accounts require system-channel patience, routing work, or both. Your Monday begins with Samia Saleem and Michael Lenahan.
Four patterns produce that recommendation, ranked by how much each should change what you do this week.
1. Two buyers said "contact me." Four didn't.
The most useful distinction across all six targets: did the buyer invite direct outreach, or didn't they?
Samia Saleem, Head of Design, Render. Posted publicly asking candidates to DM her and send portfolios for the Staff Product Designer, Agent Experience role. She's been in the role since at least June 2026, right at the edge of a new-in-seat receptivity window. Her personal portfolio still lists her GitHub role, so LinkedIn is the live channel. Contact path: cold DM, but she requested it.
Michael Lenahan, SVP/Chief Design Officer, Slack. Posted publicly about the Principal Architect role and confirmed the hire reports to him. The Salesforce vacancy listing corroborates the reporting line. His tenure and promotion date aren't resolvable from public sources, so I can't tell you whether this search reflects a new-leader mandate or established-leader expansion. Doesn't affect sequencing — he raised his hand. Contact path: cold LinkedIn referencing his recruiting post. The Issue #11 engagement package already covers portfolio mapping and outreach treatment.
The remaining four buyers either directed candidates to the application system, weren't named in the posting, or both. Invited contact outranks rubric score for determining outreach order this week.
2. Conference and community signals resolve routing that job postings don't.
Atlassian was fully unresolved in the Issue #11 Field Scan — no design-level route to the Rovo team had been located, and the recommendation was to probe through CPO Ken Exner. The Rovo & AI vacancy still names no hiring manager. The company leadership page doesn't help. A conference speaker listing and a LinkedIn org signal resolved the gap — source types that postings and About pages rarely surface.
Carola Pescio Canale is publicly identified as Head of Design, AI at Atlassian via the Config 2026 agenda. David Hoang's post confirms her as Atlassian's Head of Design for Rovo & AI. Hoang himself carries a broader VP-level remit — Head of Design for Rovo & AI and Ecosystem per his personal site, with Jira also in his scope per a Team '26 session bio — but Pescio Canale appears to be the operating design leader for the area covered by the vacancy.
Confidence: moderate. The org signal is clear; the hiring-authority link is inference. Treat her as the probable buyer and verify the reporting relationship early in any conversation.
This pattern applies beyond Atlassian. When a posting names no manager and the company page is silent, sweep conference agendas, Dive Club, ADPList, and Designer Fund Bridge before concluding the route is closed. Buyer identity often lives in community signals that company-controlled sources don't surface.
Atlassian moves from "hold until routing resolves" to "attempt contact with a named probable buyer." Third in sequence.
3. Two enterprise accounts are reachable through the system channel.
Carly Price, Senior Director, Customer & Partner Experience Design, ServiceNow. Promoted the vacancy publicly. Her scope covers customer and partner experience design across portals, self-service, documentation, and support — the functional area the Director seat sits within. But she directed candidates to the official application because of volume. Her decision authority over the Director seat is inferred from scope alignment, not confirmed.
Patrick Dohan, Capital One. Promoted the role publicly. As covered in the Issue #12 brief, Dohan is the first route and Daniela Jorge (SVP, Chief Design Officer) is the second. Dohan's hiring-manager status remains inference.
Both accounts support contextual cold outreach referencing their public post — you're responding to something they said, which is different from arriving uninvited. But neither asked for direct portfolio submissions the way Saleem did, and both run on enterprise timelines. Five to seven business days for a response is normal. Silence past ten days warrants follow-up.
Apply through the system. Send a contextual LinkedIn message referencing their post. Then wait.
4. Handshake remains fully unrouted.
Handshake is the only account where I cannot identify a probable buyer. The posting names no hiring manager. The leadership page lists CPO Vee Sahgal but no design leader. A sweep of design community directories (Dive Club, ADPList, Designer Fund Bridge), conference speaker archives, and Handshake's company blog produced no current design leadership attribution tied to Autonomous Recruiting.
Design leadership exists at the company — Jason Stirman posted a recruiting signal for Handshake in January 2026, and Erica Deahl appears as Director of Product Design in third-party directories. But neither is tied to the Autonomous Recruiting vacancy. May-Li Khoe, who announced joining as VP Design in December 2024, no longer identifies Handshake on her personal site. Don't route through her.
Hold Handshake until a design leader posts about the Autonomous Recruiting role or the posting updates to name a hiring manager. Monitor Stirman's LinkedIn — if he promotes this vacancy, he's your route.
The sequencing
- Render — DM Saleem, send portfolio. She asked.
- Slack — Contact Lenahan per the Issue #11 engagement package.
- Atlassian — Reach Pescio Canale. Reference her Rovo & AI scope. Verify she owns the req.
- Capital One / ServiceNow — Apply through system. Contextual LinkedIn to Dohan and Price.
- Handshake — Hold. Monitor for a hiring-manager signal.
Before you send anything, check your warm paths
Every contact path I can see from public signals is functionally cold. I cannot see your LinkedIn mutual connections with Saleem, Lenahan, Dohan, Price, or Pescio Canale from outside your authenticated graph. This matters more than the sequence above.
Check your mutual connection count with each of the five named buyers before you write a single message. A former colleague or co-instructor who'd make an introduction rewrites the order. Three or more mutual connections with any buyer upgrades that account to semi-warm — reference the mutuals in your message close, not the opening. If you find a genuine warm path to a buyer at a lower-priority account, contact that account first.
Warm introduction outranks invited cold contact, which outranks system-channel application to a known buyer, which outranks an unrouted account at any rubric score. Warm access to a Watch-verdict company beats cold access to an Act-verdict company at this stage of a search.
Run the check. Then Saleem on Monday.
- Handshake's four simultaneous searches: The company is running Staff design searches across Autonomous Recruiting, Growth, Handshake AI, and Student Experience alongside a VP Product search for Handshake AI — if a design leader promotes any of those vacancies, they likely own Autonomous Recruiting too.
- Atlassian's new CPO scope: Ken Exner was appointed Chief Product Officer for Enterprise & Emerging on August 6, but no reviewed source ties him to either current AI-design opening — worth monitoring whether his remit absorbs Rovo hiring authority from the existing product and design chain.
- Capital One's requisition history: The live Director posting is requisition R249772, dated August 21, while Patrick Dohan's recruiting post is roughly five months old — the gap may reflect a repost, a failed first search, or an administrative replacement, and the answer changes how far along the slate is.
- Anthropic's reappearing Core Apps role: The posting disappeared September 2 and returned under the same job ID on September 4, which signals renewed visibility rather than a new seat — but the company also added separate Product Designer roles for Design Systems, Safeguards, and Evals & Prompts that weren't previously visible.
