The Credential That Never Licensed Anyone
Software engineering never built a licensing board. Lawyers have the bar. Doctors have boards that can pull a license over a single bad decision. Structural engineers who stamp a drawing carry a PE number that a state can take back. The field that writes the software those boards run on has none of that. Anyone can call themselves a software engineer the moment they decide to, and plenty of people with the title have never had anyone formally check.
Into that gap grew two substitutes, and they're worth separating because they work differently. Portfolio is what you built: the commit history, the shipped product, the before-and-after of a system you redesigned. Pedigree is where you've been: the companies on the resume, the team you were on, the name that functions as a reference even when nobody ever calls it. Neither one is a credential in the licensing sense. Both get treated like one anyway.
A license is binary. You pass or you don't, on a specific day, administered by a body with the authority to revoke it later if you do something bad enough. Portfolio and pedigree have no such gate. They're continuous: more is always nominally better, there's no failing score, and nobody is checking the claims against reality before they go on the page. You write "led a team of twelve" and that's the record, unless someone happens to know otherwise and cares enough to say so.
They're also unrevocable in a way a license isn't. If a project you point to turns out to have been mostly someone else's work, or the company implodes six months after you left, the line on your resume doesn't get struck. It just sits there, true in the sense that you were there, misleading in the sense that matters. A license can be pulled the day the malpractice is confirmed. A resume line only fades, and fading isn't the same mechanism as revocation. It's decay, not enforcement, and it happens on nobody's schedule but the reader's attention span.
This is why both signals work fine inside a network that already trusts you and next to nothing outside it. A hiring manager who's worked at a similar company can read "principal engineer, forty-person org" and translate it correctly, discount the parts that always get inflated, and weigh the rest against what they already know about how that title gets used at that kind of place. A client who found you through someone they already trust isn't actually evaluating your portfolio cold, they're borrowing a judgment that's already been made. The portfolio and the pedigree aren't doing the verification work there. The network is. The documents are just the shape the trust takes once it's already been extended.
Take the same resume to a stranger with no calibration and no way to check it, a cold application to an unfamiliar company, a loan officer, an immigration form, and it buys almost nothing. Not because the claims are necessarily false, but because there's no enforcement arm standing behind them. A license means a regulator looked and can take it back if they were wrong to approve. A portfolio means you looked, and you got to decide what to include. Those are different kinds of promises wearing the same font.
It explains why hiring in fields that never licensed anything runs so hard on referrals. "Who do you know" isn't a failure of meritocracy, it's the actual verification mechanism standing in for the one that never got built. A warm introduction stakes somebody else's reputation on the claim, which is the closest thing an unlicensed field has to a board that can revoke something. Everything else, the GitHub, the title, the list of logos, only means anything once that first piece of trust is already in the room.