This article is for anyone who works at a big‑tech firm or aspires to join one—especially those in stable positions who consistently meet expectations but lack a standout “wow” factor. It answers a crucial question: why do competent, well‑behaved, on‑target performers often become the first casualties during a contraction?

Many assume layoffs are simple “bottom‑of‑the‑barrel” cuts—whoever has the lowest performance goes first. In reality, big‑tech operates the opposite way: the first people to be let go are rarely the weakest; they are usually the “most ordinary.” They follow the rules, make no errors, have a good attitude, and deliver reliably, yet when resources tighten they become the easiest to replace.

This piece dissects the plight of the “ordinary employee,” uncovers the decision logic behind big‑tech layoffs, and offers concrete tactics to build genuine career security in a complex organization.

1. The Typical Profile of an “Ordinary Employee”: Do You See Yourself Here?

“Ordinary” isn’t a pejorative; it denotes a low‑visibility status within the organization. Such employees usually exhibit:

  • Clock‑in/out on time, deliver on schedule
  • Consistently steady output, no major mistakes
  • Annual performance rating of Consistently Meets Expectations
  • Peer feedback: “reliable,” “easy to work with”
  • No self‑promotion, no troublemaking

These traits are prized during growth phases—they act as the organization’s “stabilizers,” keeping day‑to‑day operations humming smoothly.

When the company enters a contraction cycle, however, those very strengths no longer guarantee safety.

2. The Underlying Logic of Layoff Decisions: From “Can Do the Work” to “Must Stay”

During expansion, managers focus on maximizing output, so they need a large pool of capable executors. “Ordinary employees” become the backbone of the team.

When the tide turns and the firm starts shrinking, the managerial mindset flips: the question changes from “who can do the work?” to “who must stay?”

Every role now has to answer:

“If I can keep only five people, is this person one of those five?”

The answer is no longer based on day‑to‑day performance but on two core criteria:

1. Irreplaceability: The work stalls without you

“Doing a poor job” and “being unable to do the job” are completely different.

  • If you leave and the team can re‑allocate tasks and keep moving, you are a key executor.
  • If your departure brings a project to a halt or creates a serious risk, you are a critical role.

Irreplaceability usually stems from deep ownership of a system, process, technology, or set of relationships.

2. Memorability: Did you do something in the last six months that sticks?

Organizational memory is short. In layoff deliberations, managers tend to remember only those with high‑impact moments:

  • Led a pivotal product launch
  • Turned around a client crisis
  • Delivered a solution that dramatically improved efficiency
  • Offered a strategic insight that reshaped the team’s direction

If your name never appears in these stories, even silent, steady contributions may label you as “replaceable.”

3. Real‑World Example: Why the “nicest” person got cut first

A ten‑person team had to shed three members. The conversation between the manager and HR revealed the brutal reality:

“He’s the most liked person on the team, diligent, never complains—everyone likes him.”
“But he doesn’t own any core projects; his work can be redistributed.”
“So he was the first name on the list.”

The line—“His work can be distributed to others”—is the fatal tag for an “ordinary employee.” It doesn’t deny ability; it confirms replaceability.

When resources are scarce, managers must preserve those whose loss would directly impact the business. Personal likability bows to the efficiency calculus.

4. How to Avoid Becoming a “Replaceable Ordinary Person”

Surviving cuts isn’t about pulling all‑nighters to prove you exist, nor about office politics. It’s about systematic actions that turn your career assets into non‑negotiable value.

1. Own Projects: From “Participant” to “Owner”

Being a participant versus being the owner of a project is a world apart in how the organization perceives you.

  • Participant: Contributes a piece
  • Owner: Fully accountable for outcome, represents the project externally, coordinates internal resources

Tactics:

  • Tell your manager, “I’d like to lead Module X.”
  • At project kickoff, clarify roles and capture the Owner title.
  • In status updates, say, “I am responsible for [project]” instead of “our team is working on [project].”

2. Tie Your Work to Measurable Business Outcomes

Impact must be quantifiable, or it will fade into the background during reviews.

Action Steps:

  • Set clear metrics for every initiative you lead (e.g., +15 % DAU, ‑¥300K cost).
  • Highlight those numbers in quarterly summaries.
  • Link results directly to company OKRs (e.g., “Supported Q2 user‑growth target”).

3. Create “Story‑Ready” High‑Impact Moments

Organizational memory lives on narratives. Manufacture stories that can be told.

Examples:

  • Speak up in critical meetings with data‑backed insights.
  • Step up during a crisis and leave a “fire‑fighting” record.
  • Codify learnings into docs, training, or frameworks that spread beyond your immediate team.

4. Build Cross‑Team Visibility

Being “reliable” only inside your direct team isn’t enough—layoff decisions often come from higher‑level leaders.

Ways to raise your profile:

  • Join cross‑functional initiatives.
  • Publish best‑practice posts on the internal network.
  • Ask thoughtful questions or share ideas