Hiring activity accelerates the week after Labor Day. If you're approaching Senior IC roles right now, you're likely hitting multiple tiers at once — AI-native startup, growth-stage platform, enterprise software — and encountering hiring managers who all use the same vocabulary: craft, vision, systems thinking, hands-on.
Those words describe different jobs depending on the tier. In Issue #8 I separated AI design mandates into three different roles wearing the same label. The same compression operates here. What follows is the decode for each tier: what they say, what they evaluate, the tells that reveal which frame is active, and how your hybrid profile plays in each.
Two patterns that hold everywhere
The portfolio scan precedes any conversation, and the judgment forms fast. Design recruiter Tom Scott describes 2025–2026 as an "output over everything" market. A Figma recruiter warned that hiring managers will not work to discover your relevance. Screening risk lives in the artifact and must be fixed there. Your verbal positioning is irrelevant if the artifact doesn't survive the scan.
Every tier explicitly separates IC leadership from management leadership. Atlassian, Customer.io, and Lightspeed all define Principal leadership through personal craft, prototypes, standards, and influence — explicitly not through management. The repeated clarification tells you these buyers have been burned by candidates who treated the IC role as a management role without reports.
AI-native startup
Stated frame: Craft, curiosity, systems thinking, prototyping, point of view about the future of AI interfaces.
Actual screen: Can you produce original interaction patterns for problems with no established conventions, and can you make those patterns testable now?
Ian Silber at OpenAI said prior AI background is not required. What is required: curiosity made visible through prototypes and a position on where the medium is going. Joel Lewenstein at Anthropic described the strongest designers as people who move rapidly between long-range vision and immediate progress through production code, fast mockups, and user feedback. Vision, in his usage, means a forecast plus the ability to turn it into something testable.
Jenny Wen at Anthropic added a tension you should internalize: extensive experience is valuable, but established process becomes a liability if it reduces adaptability. Her preferred hire for a deep technical role is someone who is effectively "50% software engineer." Anthropic's Core Apps posting asks designers to question fundamental UI assumptions and invent patterns native to AI. Linear expects prototypes, internal builds, and participation from project start through customer shipment.
Tells: An AI-native buyer who is genuinely interested will ask about your relationship to the model — how you've worked with it, what you've learned about its behavior, where you think the interaction paradigm breaks. A buyer going through the motions will ask about your process. If the conversation stays on process, the evaluation has already concluded.
What wins: An inspectable artifact showing original thinking about an AI interaction problem. Not a retrospective case study — a designed object (interaction model, prototype, annotated exploration) that demonstrates taste, synthesis, and technical fluency at the frontier. An independently initiated experiment with a testable point of view outperforms a polished case study from a prior employer.
What loses: Process documentation without visible output. A portfolio that reads as traditional product design with AI added as a topic. Any signal that you would need to be taught how the technology works before you could design with it.
Your positioning here: Lead with the Trust essay, then Agentic Labs — Carrier IQ demonstrates all five handoffs. TinyFish gives you technical AI currency in past tense: you built and deployed enterprise AI agents, worked through agent traces, auditability, and governance challenges firsthand. Your vulnerability at this tier is real. As I noted in Issue #10, your highest-interest AI-native targets require the most buyer inference because the forward-looking visual design artifacts aren't fully published yet. The competitive comparison is a candidate from Anthropic or OpenAI who has shipped AI surfaces and can show code. Your counter: they designed internally, not publicly. Your published framework and Labs demonstrate synthesis most AI-native candidates don't produce. But until those forward-looking pieces are inspectable on junochen.com, you're asking the buyer to infer capability from adjacent evidence. That inference cost is the single largest constraint on this tier.
Growth-stage platform
Stated frame: Craft depth, product instinct, autonomy, collaboration, systems thinking.
Actual screen: Can you operate with high autonomy in a complex product organization — and will you stay an IC?
The second question is the one they rarely say out loud. They have all hired someone with a management title who took an IC role and immediately started trying to build a team.
Thom Rimmer at Intercom brought back design tasks because polished portfolios "rarely tell us how someone actually thinks and works." Candidates get 2.5 hours to critique a shipped Intercom flow, propose improvements, and explain their thinking. This is a buyer who concluded that retrospective portfolio explanation was insufficient for the autonomy level they need.
Katie Dill at Stripe asks candidates:
"Tell me what work you are most proud of."
The question sounds open. It is diagnostic. The answer exposes what you consider good, what motivates you, and what work you naturally want to do. In a February 2026 interview, she added curiosity about AI and willingness to act under ambiguity. The screen is whether curiosity produces an independently initiated experiment, not whether you've used AI tools.
Tells: A growth-stage buyer evaluating you seriously will probe the boundary between your leadership work and your personal craft. They want to see where one ends and the other begins. If they keep asking about team outcomes and how you managed people, they're evaluating you for a management role regardless of what the posting says — or they're trying to determine whether you'd rather manage. If they drill into specific design decisions you personally made, interaction details, tradeoffs you resolved in the artifact itself, that's the IC screen and you're in the right conversation.
What wins:
- Recent, personally executed work with clear attribution — "I designed this, here's why I made this choice."
- Evidence that you've led through standards, critique, and cross-team influence without needing reporting authority.
- A live demonstration of product instinct during any bounded task.
What loses:
- Presenting team outcomes as your primary evidence.
- Talking about org design, hiring, or team-building unprompted.
- Any signal that you view the IC role as a stepping stone back to management.
One anonymous candidate account captures the objection precisely:
"Positive feedback on everything, paired with concern that the candidate might not enjoy rolling up their sleeves and executing."
The concern was about appetite, not ability.
Your positioning here: Your BCG DV portfolio is strong. Thermo Fisher, Red Cross, Equinox+, Allē all show 0-to-1 product decisions you personally drove as Product Design Director. Alibaba shows enterprise-scale impact. Lead with your strongest personally-executed case study — Alibaba or Thermo Fisher depending on domain relevance — then Carrier IQ from Agentic Labs. It's the most interaction-dense Lab you've built, with complex form flows, coverage selection, and regulated-industry logic. That's exactly the kind of detailed design decision this buyer type probes for. The competitive comparison at this tier: the FAANG or late-stage Staff IC with years of dedicated IC-track work and deeper recent portfolio proof. Your counter — they lack function-building experience and the mandate-level product judgment that comes from it. Your craft decisions carry organizational weight theirs don't. The vulnerability is the hybrid profile itself. When the bridge narrative comes up — and it will — frame TinyFish as evidence of appetite for hands-on building. You moved to product specifically to build an agentic platform from zero, shipped it in three months, and returned to design because that's the work you want to do.
Enterprise software
Stated frame: Systems thinking, cross-functional collaboration, stakeholder management, design at scale.
Actual screen: Can you show that your design judgment prevailed against real organizational resistance — that you changed what the organization was willing to do, and that the change produced a measurable outcome?
Daniela Jorge at Capital One asks candidates to show options considered and the evidence behind the decision. The emphasis on options is diagnostic: this buyer wants to see that alternatives existed, that the organization pushed back, and that your judgment won on evidence. A candidate who presents design work that was approved without friction has not demonstrated what this buyer is screening for.
Enterprise postings that emphasize "cross-functional collaboration" repeatedly are telling you that design currently lacks organizational authority and the hire is expected to earn it through the work, not through title. A posting that never mentions "team building" or "hiring" for a Director-level role means they want an elevated IC regardless of the title container.
Tells: An enterprise buyer evaluating you for craft will ask about tradeoffs — what you gave up, what you fought for, what you compromised on and why. If the conversation is entirely about how you worked with others and never about what you actually designed, the role may be organizational influence without craft authority. That's a different job.
What wins:
- Case studies that show mandate creation — you identified a structural problem, built the case, and led the work — within a complex organization.
- Metrics that connect design decisions to business outcomes.
- Evidence that you've operated in regulated or high-stakes environments where the cost of a wrong design decision is material.
What loses:
- A portfolio that only shows greenfield work without organizational constraint.
- Presenting speed as a primary virtue. Enterprise buyers are often more concerned with durability than velocity.
- Treating the enterprise context as a limitation rather than a design constraint.
Your positioning here: Alibaba is your strongest asset — $50B+ GMV, cross-functional sprints, measurable outcomes, mandate you built yourself as Head of Design and Research. Lead with it. Thermo Fisher adds regulated-industry proof with clear business impact (Product Design Director at BCG DV). Your AI currency — TinyFish in past tense, Trust essay, Agentic Labs — differentiates you from enterprise design directors who lack AI-native credibility. The competitive comparison at this tier is the enterprise design director with sustained tenure at organizational scale, someone who ran a 50-person design org through multiple product cycles. The objection they create: your BCG DV work shipped fast in venture-backed sprints, not through sustained organizational friction. Alibaba is your direct counter. That was in-house, at scale, against real organizational inertia, and it produced measurable business outcomes. Your vulnerability: a pure enterprise buyer may still read the BCG DV portfolio as consulting-speed work. Alibaba must do the heavy lifting here.
Sequence: craft first, leadership second, bridge third
The single highest-risk pattern for your hybrid profile across all three tiers: presenting leadership scope as your primary differentiator to a buyer who is screening for current craft appetite.
Leadership scope is your secondary differentiator. It explains why your craft judgment operates at a higher altitude than a pure IC's. But it only works after the craft evidence has already landed.
Personally-executed artifact first. Leadership context second. Bridge narrative third. Reversing this order with a craft buyer answers a question they weren't asking and raises one they were hoping you wouldn't.
- Intercom reversed its own guidance: Rimmer's reinstatement of design tasks directly contradicts Intercom's earlier published hiring guide, which argued that deep examination of previous work was a better indicator than an imaginary take-home exercise — the reversal itself tells you how much portfolio polish has depreciated as a signal at the growth-stage tier.
- Gusto's organizational transformation timeline: Gusto publicly documented converting its design organization from static Figma deliverables to code-based building within one quarter, including internal resistance, an MCP-connected design system, and a June 1 deadline — relevant context if Capital One's AI-in-XD mandate asks you to describe how organizational adoption actually works.
- Figma's 2026 AI report on designer roles: Figma's survey of 8,403 respondents found that designer participation in development rose from 21% to 41% year over year, directional evidence that the "50% software engineer" expectation Jenny Wen described at Anthropic is spreading beyond AI-native companies.
- OpenAI Financial Services as fresh evaluation language: OpenAI's September 10 launch of ChatGPT for Financial Services includes granular citations for source inspection alongside explicit warnings that outputs may be inaccurate, a live example of the trust-and-evidence tension your framework addresses directly.