Don't bother, the people you are answering to, the "engineers", are concern trolls who want to become gatekeepers that will force you to have an "software engineering license" they control to do your job, that's their ultimate goal, they are corporatists.
Imagine needing a freaking license to deploy an app, Communist China style, These people are cunning and come to every thread where somebody screws up to push their anti free market agenda. Don't waste your energy arguing with them, call them out.
The frivolity with which "Engineer" titles were co-opted by tech has always been distasteful to me. It felt intended to claim all of the prestige with none of the rigor, accountability, or social responsibility.
Broadcom exploits over the years would disagree. So would Samsung's hardware encryption. So would TPM. So would BadUSB. So would everything related to Bluetooth. Et cetera.
No matter what kind of engineering you do, don't try to predict the future. Engineer towards ease of maintenance and ease of update/deployment instead.
None of the engineers I have hired or worked with assume such liability directly.
Usually, their firms limit liability to the price of the contract. I assume insurance does otherwise.
It might be doable, but would also require (at a minimum) a lot more compensation to make up for the increased liability. Which gets to the heart of the problem, it’s a lot more expensive to produce higher quality software.
And see them evaporate from the companies that would implement something like this.
Personally I would neve take a contract where I could be held legally responsible for bugs.
And ultimately it is the owner who let the product out in a wild without spending a year testing billions of permutations first. Try holding them responsible and see how far can you get.