Used to do IT (helpdesk) for one of the many local networks that got acquired by Sinclair around 2013. Company I worked for owned about a dozen stations across

Used to do IT (helpdesk) for one of the many local networks that got acquired by Sinclair around 2013. Company I worked for owned about a dozen stations across the region, when Sinclair bought us they owned around 200 at the time. In spite of this, our IT operations were way more advanced. For example, Sinclair had only started using AD and Exchange less than a year before acquiring us, they had been on some ancient Novell installation before that. Most entertaining memory I have of their incompetence: after the acquisition my boss no longer had permission to approve payment of bills, it had to go through corporate. So my boss called and emailed for months to get payments approved for our internet, phone service, etc., keeping a thorough record of all of the times he had asked to get our bills paid. Fast foward to about 4 months after the aquisition and suddenly our long distance phone service stops working. We contact the phone computer and find it's because of non-payment (we already suspected as much thanks to all the late notices we received). Corporate flips their lid, attempts to blame my boss for it, and he just sends them the dozens of emails and refers them to the dozens of calls he made record of. No idea who (if anyone) took the heat for it at corporate after that. Second story, we hired a new senior network engineer. Turns out he knew even less about networking than me and the other guy on the helpdesk. But the technical competency part of the interview process was administered by, you guessed it, someone in corporate IT. At least we were able to get the guy fired within a few weeks of him starting, and the guy at corporate who passed him had some major egg on his face. This was shortly before I left though so I don't know if anything more came of it. I only stayed for about a year after the merger.