Titles get sloppy in software and game workplaces. "Lead," "manager," "staff-plus," "people lead," and similar labels do not tell you enough by themselves. What matters is the authority attached to the role.
The plain-English version
The NLRA's Section 2(11) definition says a supervisor is someone who has authority, in the interest of the employer, to do things like hire, transfer, suspend, lay off, recall, promote, discharge, assign, reward, or discipline other employees, responsibly direct them, adjust grievances, or effectively recommend those actions, and who does so with independent judgment.
The NLRB's own basic guide adds an important plain-English point: supervisory status depends on actual authority over employees and not merely a title.
That is why this question matters early. If your role is ambiguous, you may not be in the same legal lane as the coworkers around you.
Where workers get confused
In software and game workplaces, authority often hides inside systems instead of looking like old-school shop-floor supervision.
Common examples:
- a lead who assigns work but cannot really change status, pay, or discipline
- an incident commander who directs work during outages but only under set procedures
- a manager title that means people administration in one org and senior individual contribution in another
- a staff engineer whose technical influence is real but whose personnel authority is weak or nonexistent
What to compare
- do you have authority to recommend discipline that is usually followed?
- do you assign work in a way that changes pay, hours, status, or evaluation?
- are you conducting formal reviews, or just giving technical guidance?
- can you effectively recommend hiring, firing, promotion, or layoff decisions?
- when you direct work, are you exercising independent judgment or just following routine instructions?
Why remote and hybrid work can blur this
Distributed workplaces hide authority inside workflow tools, staffing allocation, approval queues, incident command, and async sign-off. A worker may feel like a peer while still exercising real supervisory functions. The reverse can also be true.
That means workers should look at the practical power in the role, not just how collegial the culture feels on Slack or in code review.
Safer next steps
- separate your title from your actual day-to-day authority
- do not assume you should play the same public role as non-supervisory coworkers
- get clearer on your status before taking visible action on behalf of others
- stay on personal systems when comparing notes about this
What not to do
Do not guess. Do not pull other workers into a risky plan while your own role is unclear. Do not use privileged access to subordinate information in ways that could expose them.
What this does not settle
This page does not decide your legal status. It does help you avoid one common mistake: treating title inflation, workflow authority, and real supervisory power as if they were the same thing.
Move carefully if "lead" and "manager" authority is being used inconsistently, if your title seems inflated to stretch management coverage, or if the company appears to be using role ambiguity to weaken worker relationships.