Audit Your Job Risk With Uber's Four Questions

If your org chart changed this quarter, you may already know which parts of your job are exposed. Uber's restructuring announcement turns that fear into a four-question audit. Uber announced on Wednesday that it would eliminate about 3,300 corporate positions, or about one-tenth of its 34,000 corporate employees, to streamline operations and reduce management layers.

Uber's announcement is a test, not a rumor

Most workers hear about layoffs and feel exposed, but they cannot say why. The announcement gives you test points: distance from the top, tiny reporting units, overlapping functions, and location rules. Each can be checked quickly.

A single flag is a warning; multiple flags mean your role needs a stronger story, a wider audience, or a different location. The audit shows where your role can be absorbed, merged, or relocated.

Do not run the audit once and forget it. Run it when your org chart changes, when a manager leaves, or when a new tool changes how work is assigned. Check it again when the structure moves.

Four flags show where your role can be cut

The cuts follow structure. The count of staff positioned at least seven levels below CEO Dara Khosrowshahi fell by 20%. Uber trimmed the count of one- or two-report micro-teams by nearly half. It is folding its separate Restaurants, Retail, and Direct delivery groups into unified teams operating at global, regional, and country levels. It will anchor global teams in New York and San Francisco while clustering regional, country, and technology staff in chosen hub locations. Only around 1% of staff will remain fully remote, while Uber's hybrid rule requiring three in-office days per week stays in place.

Run the items before you start guessing. If an item flags, use it as a prompt to make your role easier to see.

• Layers: Count the reporting lines between you and the CEO; flag yourself if you are at least seven levels below.
• Team size: Check whether you manage one or two direct reports; flag yourself if the answer is yes.
• Function merger: Name the adjacent team doing similar work; flag yourself if your work could move into a unified global, regional, or country team.
• Remote exposure: Check whether you are fully remote or tied to a chosen hub; flag yourself if you are not in New York, San Francisco, or a selected hub.

Uber is joining its Core Services Engineering and Science groups inside the technology division. If your work sits next to a sibling group, assume the boundary is negotiable.

Turn the flags into a two-week move plan

Week 1: get the answers out of your head. Write the four flags on one page. Layer or team-size flags call for work that reports to a broader audience. For function-merger flags, document the outcome you own, not the title you hold. For remote-exposure flags, ask for a written statement of your location expectation before you invest in a move.

Make the ask concrete. Tell your manager what you want to own, who should see the result, and what would make the role harder to replace. If the answer is slow, keep a private record of the work you delivered and the people who relied on it.

Week 2: make the story portable. Lead with the system you kept running, not the org box you sat in. Update your résumé with the problem you solved, the scope you handled, and the result you can defend. Ask for the next step in writing, and put the date on your calendar.

If your role is in support, operations, delivery, or engineering, the value is the system you can explain, defend, and move to a new team.

This week, send the page to a trusted colleague and ask which flags would change if your manager left. Keep it visible until you have a next step.