Employees vs. Contractors: Why Companies Pay for Dependability, Not Just Work

The economics of employment puzzles people who think about it carefully. Contractors are usually cheaper than employees for the same work. They're more flexible. You can scale them up and down. You're not paying for benefits, employer taxes, or the long-term compensation structures that employment requires. Why would any rational company prefer employees to contractors?

Taleb's answer: companies pay for a specific form of skin in the game. The employee's skin is in the game in a way the contractor's usually isn't.

The Asymmetry That Creates Dependability

An employee has far more to lose from being fired than a contractor has from terminating a contract.

The contractor calculates: what is the penalty for walking away or underperforming on this engagement? There's usually a cost — reputation, a penalty clause, an awkward exit. But it's bounded. The contractor can model it, calculate it, and decide whether breaking the engagement is worth the cost.

The employee faces a different calculation. Being fired isn't a cost they can easily bound and calculate. It affects their financial security across a longer horizon. It raises questions about their reliability that follow them to subsequent employers. In professional contexts, it can affect their professional license, their career trajectory, and their social standing. The exposure is open-ended in ways the contractor's isn't.

This asymmetry is what produces the difference in behavior. The employee is more reliable because they have more to lose. The value of employment is buying that specific exposure — the employee's skin in the game — for the duration of the relationship.

The Signaling Function of Employment

There's a second function that employment serves, which is distinct from reliability.

The employee, by accepting the constraints of employment — specific working hours, organizational hierarchy, dress codes, ritualized punctuality, the particular norms of the company — is demonstrating domestication in a specific sense. They're signaling a disposition toward compliance with structured authority.

This signal is valuable for certain roles. You want surgeons who will reliably show up. You want accountants who will reliably follow procedures. You want client-facing staff who will reliably represent the company in the way the company has specified. The nine-hour daily constraint and its adjacent rituals are the performance of reliability before it's tested by a specific situation.

Taleb's formulation: the employee has become a dog rather than a wolf. Dogs are more reliable for certain purposes. They're domesticated. They've accepted constraints in exchange for security and food. Wolves are more free, but they're not what you want if you need reliable, repeatable behavior within a specified context.

This isn't a pejorative. It's a description of what the transaction actually is. Both parties understand it. The employee trades freedom for security and belonging. The employer trades flexibility for dependability.

The "Companies Person" Problem

There's a variant of the employment trap Taleb identifies that's worth noting: the "companies person" — someone who isn't loyal to any single firm but is deeply dependent on remaining generally employable.

This person appears free in one sense: they'll move to wherever the best opportunity is. But their actual freedom is essentially zero. They must never meaningfully offend a potential future employer. They must maintain a professional presentation that makes them continuously hireable. Their opinions on controversial topics must remain safely within the range that doesn't create professional risk. Their public persona is optimized for employability rather than for their own views.

The companies person is more constrained than the old company man, who at least had the security of a single employer willing to absorb some rough edges. The companies person has to perform reliability for the entire market of potential employers at all times.

This is the employment relationship made universal — skin in the game toward a diffuse audience rather than a specific employer — and it produces a particular kind of person: high-performing, predictable, never genuinely offensive to anyone in a position to affect their career.

When Contractors Are the Right Choice

Taleb isn't arguing that employment is always superior. The analysis applies in the other direction too.

For genuinely discrete projects with clear deliverables — build this system, write this report, analyze this data — the contractor relationship is appropriate. The work is scoped. The skin in the game is the contractor's reputation on that engagement and the straightforward contract terms. There's no benefit to the employment relationship's open-ended exposure if the scope is well-defined.

The employment relationship adds value proportional to the open-endedness of the role. If you need someone to respond to situations you can't fully specify in advance, to represent the company's interests in unpredictable circumstances, to make judgment calls that reflect the company's values rather than the letter of a contract — employment creates the incentive structure that produces this behavior.

The contractor who walks if the engagement gets complicated is rational. The employee who handles the complication because their exposure is open-ended is also rational. You're just buying different things.

The Practical Test

When deciding whether to hire an employee or contractor, the real question isn't "which is cheaper?" It's: how much do I need this person to have more to lose from failure than the immediate cost of breaking the engagement?

The more open-ended the role, the more unpredictable the situations they'll face, and the more the company's interests depend on reliability under pressure — the more you're buying the employee's skin in the game, not just their labor hours.

For the full framework, read Skin in the Game Explained.