Ninety-Second Skim

The ninety second skim is the first brutal filter every design hiring manager runs in 2026. You pour forty to eighty hours into your portfolio. They open the link hunt for three signals and close the tab after ninety seconds if anything is missing. Those signals are one shipped product with a live URL and real users one short decision log that shows your actual thinking and one piece of public writing that proves you can articulate taste. The skim replaced the old portfolio because AI now generates high polish in minutes. What matters now is judgment shipping speed and public evidence. The entire anti portfolio approach exists to pass this test before the thirty minute deep review even begins. The skim is not a thoughtful exploration of your twelve page case studies. Hiring managers do not zoom in on mood boards or scroll through persona docs. They skip the hero shots the journey maps and the wireframe galleries that dominate most Behance decks. The skim ignores six perfect Dribbble shots if they lack a shipped product behind them. It has zero interest in generic shadcn variations or Material UI tweaks that Cursor could generate while you sleep. This is not the place for process theater or bootcamp deliverables presented in a vacuum. Anything that smells like design school output dies in the first pass. The skim wants texture from real constraints ugly compromises and lessons learned in production not rendered concepts for brands you never worked with. Look at how Brian Lovin structures his site with every project living as a short decision log. Three or four sentences explain a layout choice what got cut and what he would redo. No forty hour decks just direct text that reads like senior taste in ninety seconds. Pair that with Pieter Levels approach where he ships tools like nomadlist and remoteok then points to the live products and public metrics as his entire hiring case. A hiring manager at Linear opens Levels link sees the shipped SaaS with paying users spots the linked writing about launch decisions and immediately moves him to the deep review pile. The same pattern plays out at Vercel where their recruiters check GitHub commit history an Are.na channel with annotated saves and a Threads essay on design systems before they ever look at mockups. One junior designer shipped a small Claude Skill that automates Figma component cleanup. He wrote a three paragraph log on why he prioritized speed over features and published a five hundred word post on Twitter about AI tooling tradeoffs. That combo survived the skim at Anthropic while six polished concept projects from another candidate hit the trash. Another example comes from Robin Rendle and Lynn Fisher whose personal sites function as living decision logs that hiring managers at Anysphere reference first. Build every public artifact through the lens of the ninety second skim when you are serious about landing roles or inbound opportunities in the current market. Spend your two weekends exactly as the anti portfolio blueprint demands. First ship the product get it live and in front of at least one user even if that user is you on day one. Then write the decision logs in ninety minutes total. Then publish the writing piece that shows judgment. Use this filter when deciding what to delete from your current presence. Kill the mood boards the twelve page decks and the Dribbble rows without mercy because they fail the filter at teams like Linear Vercel Anthropic and Anysphere. Apply it when choosing what to work on next by shipping a real Chrome extension that solves your own pain point with Cursor or v0 instead of redesigning a banking app for the tenth time on Behance. Write publicly about the ugly decisions you made during the build and update your Read.cv hub weekly to keep the trail warm. The skim mindset forces you to ship fast document real choices and think in public which compounds into senior opportunities faster than any portfolio template ever could. Ignore the ninety second skim only if you are targeting the shrinking pool of agencies still stuck in 2018 hiring rituals or if you have zero interest in public discourse. Those exceptions are becoming rare as even traditional shops start to value shipped evidence. Do not waste cycles on skim optimization if your work must stay confidential for NDAs in which case you need to negotiate public analogs or anonymized versions. Avoid this framework when you genuinely prefer the slow craft of forty hour polished decks over rapid shipping and writing. That path might satisfy your soul but it will not fill your pipeline in 2026. The skim does not grade on a curve. Ruthlessly optimize for the ninety second skim or watch your competition ship past you while you polish pixels no hiring manager will ever see.