We found something this cycle that reframes three listings on the board. Brex's careers page now identifies it as a wholly owned subsidiary of Capital One. The equity thesis doesn't hold. The role itself, designing trust and supervision for AI that touches money, is still one of the strongest mandate matches in the scan. That kind of split kept surfacing: what a company calls itself versus what's true underneath. So we scored every role by the design problem, not the brand. The portfolio section turns the same lens inward. Your surfaces have trust failures that contradict the essay you're leading with. Fix those first.

We read eight live postings this cycle and kept finding the same question underneath different language. Amplitude wants someone to "define how agents and humans work together in the same workflows." Gusto wants someone for "AI wrongness" and "exception movement." Completely different industries, same fear: who designs the moment a person decides whether to trust what an agent just did. You have that answer. What you don't yet have is packaging that lets a buyer see it in 30 seconds. That's what this issue is for.

We pulled apart eight target companies this cycle. Every one is hiring for the same problem it can't quite name: what happens when the system acts and a person has to decide whether to trust it. Ramp's posting calls it "designing memory." Headway wants it solved across clinical documentation and billing. You've been building for that moment since Thermo Fisher. The positioning is the sharpest it's been. One thing in the way: your site serves a private essay in full HTML before the password check runs. Close that, then move.

We swept every design leadership posting across your targets this cycle for one signal: does the company name who's accountable when the AI is wrong? Ramp does, describing agents handling $200B in spend and asking who verifies. Headway names clinical consequence when AI drafts a provider's session notes. Most companies don't. That gap changes your whole approach. It's the difference between answering a question the buyer already has and teaching them to ask it. The proof sequence is different for each. Battlecards are ready if you need to move today.

We pulled apart eight live signals this week and kept landing on the same word in the job copy: trust. Showing up as operational requirements, the kind you get evaluated against. Gusto's posting asks candidates to design what happens when AI gets something wrong. That is your Thermo Fisher case restated in their language. Capital One wants someone to change how 200 designers work with AI. Suno needs a design leader while an artist-rights controversy defines the product's trust problem in public. All three are live, all three map to work already published at junochen.com, and a message sent before the July 4 weekend lands in a thinner inbox.