Teen Was Waiting in His Dad’s Office Lobby — Then an Employee Tried to Have Security Remove Him

A 16-year-old waiting for his father in an office lobby said he was used to being in the building. Before COVID changed the rhythm of the office, he had spent plenty of time there after school. His dad was an executive at a media tech company, and the building was familiar to him. He knew the general setup, he knew how things usually worked, and he knew he was allowed to wait in the lobby.

That did not stop one employee from deciding he did not belong there.

The teenager explained that his mom had dropped him off because his dad was finishing a meeting and they planned to go eat lunch together afterward. The lobby was quieter than it had been before the pandemic because many people were still working from home. The teen sat there with his backpack, waiting.

Across the lobby, he noticed a man watching him.

The man was with a few other people at first. Then he came over, acting friendly, and asked if the teen worked in the building. The teen thought that was an odd question because he was clearly a teenager with a backpack, not someone dressed for work. He told the man he was waiting for someone.

That should have been enough.

Instead, the man told him only employees were allowed in the lobby because of COVID. The teenager knew that was not true. Other people came in and out of the building, and the lobby did not require someone to be an employee just to sit there while waiting for someone.

The employee would not let it go. He told the teen that “homeless people” had been coming into the building and lying about why they were there. He told him to leave. The teen stayed put.

Then the employee tried to get security involved.

The security guard at the desk told the man the teenager was allowed to be there. That should have ended it. But the man kept pushing, apparently trying to get the guard to escort the teenager out anyway. The back-and-forth went on for close to 10 minutes, and the teen grew more frustrated by the minute.

Eventually, he told the man to leave him alone. Then he told him who his father was.

The employee laughed, as if he did not believe him.

By then, the teen’s dad had texted that he was outside. The teen left, but his father could tell something was wrong as soon as he got in the car. When the teen explained what happened, his dad asked for details: the man’s name if he had it, what department he might be from, what he looked like, and what he had said.

The teen gave him what he remembered.

Later, his dad found out who the employee was and contacted the man’s supervisor. The employee was fired.

That outcome rattled the teenager. He knew the man had been rude and had escalated a situation that security had already handled, but he had not expected anyone to lose a job over it. He wondered if he had accidentally used his father’s position to get someone fired, even though he had only told his dad what happened because he was upset.

In the Reddit post, commenters quickly pushed back on the idea that the teenager had caused the firing. They pointed out that the employee had lied about building policy, ignored security, accused a kid of not belonging, and caused a scene in a professional lobby. If the company fired him over it, many suspected this was not his first problem.

That turned out to be right.

About six weeks later, the teen posted an update. He had talked to his dad again because he still felt guilty. His dad said he could not share private employee details, but he did clarify one important point: the man had already had issues at work. He had only been with the company a few months, and the dad had suspected who the teen was describing before confirming it.

The firing decision had not been the dad’s to make. The supervisor handled it. According to the dad, if the man had been fired, it was because he already had a lot of strikes.

The teenager also spoke with the head security guard, someone who had known him for years. The guard said he was sorry he had not been there the day it happened, then said he was glad the company had removed the employee because, in his words, the man was “crazy.”

That helped the teen finally let go of the guilt.

The confrontation had not started because he threw his father’s name around or tried to get special treatment. It started because an employee saw a teenager in casual clothes, decided he did not belong, ignored the person actually responsible for building security, and kept escalating even after being told to stop.

By the end, the teen understood that telling the truth about what happened was not the same thing as getting someone fired. The man’s own behavior in that lobby — and apparently other behavior before it — is what brought the consequences down.

Commenters were strongly on the teenager’s side. Many said the employee had no reason to keep bothering him after security confirmed he was allowed to be there. Even if the man had been concerned at first, the appropriate person had already answered the question.

A lot of readers also pointed out that firing someone over a single awkward lobby interaction would be unusual unless there were already problems. The update confirmed what many suspected: the employee had other issues, and this incident was likely the last straw.

Several commenters focused on the professional risk the employee created. If he treated a casually dressed teenager that way, they argued, he might do the same to a client, contractor, visitor, or executive’s family member. In a corporate building, that kind of behavior can become a serious reputation problem fast.

The strongest reaction was that the teenager did not abuse power. He reported what happened to his parent. The adult employee was the one who lied about policy, ignored security, and kept pushing a confrontation he had no authority to control.