I Worked With A Murderer!
When I was a kid back in the early 1980’s, a teenager killed another teenager and hid the body in the foothills. The disappearance at that time, and the remains found several years later, was big news in the San Francisco Bay Area, one of several high-profile kidnappings and murders that prompted parents to keep their children indoors. Fast forward nearly 40 years later, a friend sent me the link to an old news article about the suspect arrested for that crime. The suspect in the perp walk photo was a former coworker whom I worked with for several years before he got fired, I thought, for being a douche bag. That wasn’t the whole story on his firing.
Unfortunately, I can’t share the article link to the article or the person’s name.
Although arrested and charged for the murder over a decade ago, the suspect was never tried as the case got thrown out of court for a lack of evidence—the murder weapon was never recovered—despite having a body and a confession. A person arrested but not convicted of a crime has a reasonable expectation to privacy despite the news media coverage. Or, maybe not. A recent court ruling for police taking DNA samples have implied that an arrestee has “diminished expectations for privacy” as legal proceedings are public. Since I’m not familiar with intricacies of true crime writing (i.e., how to avoid being sued by someone who holds a grudge), I’ll be deliberately vague on the details to protect the innocent and the guilty.
The suspect and I started working together in IT support at the same time. Almost immediately he tried to put himself ahead of everyone else in a “Me! Me! Me!” attitude to impress the client—the company that hired the contracting agency to provide tech workers—in meetings, conference calls and emails. This insecurity, he told me, came from a deep need to avoid being unemployed again, which was understandable as everyone was still skittish years after the Great Recession. Except the “Me! Me! Me!” attitude never got dialed back as time went on and he never took the obvious hints from management to drop it.
Our first bump came when he accidentally rebooted the server that everyone logged into from our workstations. During the early days of the project, almost everyone rebooted the sever by accident while trying to reboot a remote system since the server wasn’t then properly configured to prevent admin users from rebooting it by accident. But he did it twice in one day. He never came forward to own his mistake. When the server owner checked the logs and fingered him in IM, he made excuses for why it happened—and those excuses went on for days. Everyone, including yours truly, roundly jeered him whenever the topic of accidental rebooting came up.
When I accidentally rebooted the server from a double-clicking mouse a month later, I contacted the server owner during the one-minute delay before the server rebooted, admitted my mea culpa to the team in IM (instant messenger), and replaced the double-clicking mouse. No one gave me grief for rebooting the server. The suspect complained loudly that he got treated unfairly because what I did was much worse than what he did. No one bought his story. That was the beginning of his reputation of being a douche bag.
When a team lead asked his group for volunteers to work with the suspect on an assignment a year-and-half later, no one wanted to work with him and everyone confessed that they didn’t like him. I felt compelled to write a long email to the project manager about all the problems I had with him. Two weeks later, he got fired. The funny thing was that no one told him that he got fired. According to coworkers on his team, he figured it out when his regular and admin Windows accounts got deactivated, his badge stopped working, and the client refused to return his phone calls. Never did hear if security showed up to escort him out of the building.
The real reason he got fired, I recently learned, was an unknown coworker googled his name, came across the decade-old story about his arrest, and took the story to the client. The coworker got written up by the contracting agency for going to the client, but the coworker felt strongly enough that the client had to know who the suspect was. The client had a felony checkbox on the background check form (i.e., “Have you ever been arrested and/or convicted of a felony?”). The suspect, who didn’t live in a state like California with felony checkbox protections, failed to check the box and didn’t mention his arrest. That was enough to terminate his employment.