Cynthia: portfolios beat CVs

Cynthia Ozumba’s argument is straightforward: in remote hiring, especially for creative and technical roles, employers trust visible work more than long resumes. In a social thread posted on May 19, Ozumba said candidates should lead with portfolios, shipped projects and proof of execution rather than rely on multi-page CVs. The post spoke to a hiring market where startups and remote teams often screen for evidence they can inspect quickly. It also landed amid broader discussion about how Bay Area and startup employers are weighing demonstrable output against pedigree. ### Why would a portfolio matter more than a CV in remote hiring? Remote hiring compresses trust. A manager who may never meet a candidate in person often wants to see what that person has already built, written, designed or deployed. Ozumba’s thread argued that a portfolio answers that need faster than a resume does. Her emphasis was not on formatting or aesthetics, but on evidence: live links, finished projects, case studies, shipped work and examples that show how a person thinks. For technical candidates, that can mean a deployed app, a GitHub repository, a product teardown or a documented workflow. For creative candidates, it can mean campaigns, writing samples, brand systems or client outcomes. That logic is not limited to designers. In startup hiring, a portfolio increasingly functions as a compressed diligence file — something a founder, recruiter or hiring manager can scan in minutes. ### What kind of work counts as “proof”? Proof of work usually means artifacts that reduce guesswork. A recruiter does not have to imagine whether a candidate can write clearly if the candidate links a published memo, landing page or product spec. For engineers, proof can include code, demos, technical documentation, bug fixes, open-source contributions or a product running in production. For operators, marketers and product people, it can include dashboards, launch plans, process docs, experiments, sales collateral or before-and-after metrics. The common thread is that the work is inspectable. Ozumba’s framing also reflects a shift in how candidates package themselves. Instead of listing responsibilities, they are being pushed to show outputs. ### Why does this resonate with startup and Bay Area hiring? Startups often hire under time pressure. A small team may not want to spend several rounds inferring whether a candidate can execute in an ambiguous environment. That is especially true in remote roles, where written communication, self-direction and independent delivery matter early. A portfolio can signal those traits indirectly. A clean case study shows judgment. A shipped side project shows initiative. A public body of work shows consistency. Recent career advice aimed at remote workers has echoed the same point: portfolios are becoming part of a wider “digital hiring ecosystem” that includes LinkedIn, personal sites, GitHub and work samples, not just a standalone PDF resume. In that setup, the resume still matters, but more as an index than as the main proof. ### Does this mean resumes no longer matter? No. A CV still helps recruiters match titles, dates, tools and experience to a role. Many companies still require one in formal application systems. But Ozumba’s point is about hierarchy, not elimination. In competitive remote and startup markets, the resume may open the file, while the portfolio closes the credibility gap. A strong CV without evidence can read as claims. A modest CV with strong work samples can read as lower-risk hiring. That distinction matters most in roles where the output can be shown. It matters less in jobs where the work is confidential or hard to display publicly, though even there candidates can often create sanitized case studies, process write-ups or mock projects. ### What should candidates do next if they agree with her? A candidate who wants to follow Ozumba’s advice would start by assembling three to five pieces of work that match the role they want next. Those samples should be easy to open, easy to understand and tied to a result. A practical portfolio usually answers four questions fast: what was the problem, what did you do, what tools did you use, and what changed because of your work. A hiring manager does not need a full autobiography. They need enough evidence to keep moving. Ozumba’s post remains on X, where readers can review the original thread. The next step for candidates is less about rewriting a summary statement and more about deciding which projects, links and work samples belong in front of the next employer.