As a Lead Engineer, I was once given a task to add a feature that blatantly violated FCC regulations.
The product team wasn't malicious; they were simply unaware. But as I vetted the requirements, the red flags became impossible to ignore. The feature created a vulnerability where anyone could be sent mass SMS messages with no verification, no controls, and no ability to opt out.
It didn't require a hacker to exploit this. The design itself was an open door for harassment and anonymous spam.
"Don't Worry About It"
When I raised these concerns, I came prepared. I brought the specific FCC regulations and historical context. I pointed out that this wasn't just annoying; it was a harassment tool waiting to happen that, if legally pursued, could result in potentially millions in fines.
The organization’s response was chilling in its casualness: "Even if it turns out to be illegal, the company will take the liability and not you, so don't worry about it."
This is the Liability Lie. It is a common deflection used to pressure engineers into compromising their standards. It is a not a respectable answer, and it is factually dangerous. Research reveals multiple instances where individual developers have faced legal consequences for their direct role in creating illegal systems.
The Engineer as Gatekeeper
I refused the task. I made it clear that I would not put my name on code that I knew to be harmful and non-compliant.
The story doesn't have a fairy-tale ending where I saved the company from itself. I didn't convince them to abandon the idea. Another engineer, perhaps less experienced or more pliable, eventually agreed to build it.
I left the company within a year for a significantly better opportunity.
Don't Outsource Your Conscience
Do not place your personal trust in a company and believe them blindly when they say they will protect you. They are not there to protect you; they are there to protect the business.
Stay true to your principles. When ethical boundaries are crossed, make it known. Effective leadership is not always the easiest path, and it sometimes means walking away. But having the resolve to hold firm builds the necessary character to excel, and ensures that when you look back at your career, you can stand by every line of code you wrote.