Why Struggling in Big Tech Isn’t Always About Ability

Introduction

A former colleague who spent nearly six years at a major tech firm remained at the P6 level despite solid performance scores. After reviewing his promotion dossier, the author realized the issue was not lack of skill but the invisible position he occupied, handling essential but low‑visibility work.

Big‑Tech Ecosystem

Success in a large organization is not a simple meritocracy. Factors such as department, manager, business relevance, project budget, exposure, and promotion slots all influence outcomes. Two engineers with similar technical competence can have divergent impact: one stabilizes a core service and is directly praised by business leaders, while another patches peripheral systems and receives little recognition.

Talent Density and Queueing

High talent density creates a queue for opportunities. Even strong engineers must first secure trust, historical contributions, business familiarity, and managerial endorsement before gaining access to high‑impact projects.

Trust as a Gatekeeper

Being trusted by senior staff determines whether you receive core‑project ownership, present key designs in review meetings, or are handed risky modules. This “backing” is essential for visibility and career advancement.

Seniority, Risk, and Organizational Logic

Organizations assign critical business to seasoned staff to mitigate risk. Veteran engineers know historical baggage, fragile interfaces, and escalation paths, making them safer choices for core responsibilities. Newcomers must acquire this context, often through incident handling and deep system knowledge.

The Cost of Peripheral Work

Continuously handling low‑visibility tasks—maintaining legacy systems, cleaning dirty data, coordinating cross‑team hand‑offs, or troubleshooting after‑hours—demonstrates reliability but rarely leads to promotion because the work does not translate into clear, business‑facing results.

Self‑Assessment Checklist

Do I have clear ownership of outcomes?

Can my results be directly understood by business leaders, managers, and promotion committees?

Am I working on growth‑oriented or maintenance‑oriented domains?

Does my manager have the willingness and ability to champion me?

Do I have opportunities to own the full lifecycle of a project—from definition to delivery and post‑mortem?

If the answers are consistently negative, the limitation may be positional rather than personal.

When to Consider a Smaller Company

Big firms offer platforms, processes, and mentorship, but if you are stuck in peripheral roles with no path to core impact, a smaller organization can provide end‑to‑end ownership, faster decision‑making, and clearer visibility of contributions. However, smaller firms also bring chaotic processes and limited resources, requiring a balance between exposure and workload.

Three Factors Before Switching

Assess whether the new role involves core business problems rather than another peripheral task.

Evaluate if the prospective manager values autonomy and problem‑definition, not just execution.

Determine whether you can tolerate the uncertainty and resource constraints of a smaller environment.

Final Thoughts

Being stuck in a large company does not automatically imply personal inadequacy. Evaluate both ability and ecosystem fit. If the environment cannot provide a visible responsibility chain, consider either persisting for a core opportunity or moving to a setting where your impact can be unmistakably demonstrated.