Engineers have specific degrees and certification processes in most, but not all countries. What this legal framework entails for you will depend on where you live.
Where there are regulations, engineers often accept civil and/or criminal liability when their products hurt or kill people. They put their stamp on their work to stake their identity on the safety of their design.
Bioinformaticians wear many hats and are programmers, often, or data scientists, but I would not call them engineers in the common and legal senses of the word.
There are virtually no assurances of legal or even reputational liability when you use an open source bioinformatics package, for instance.
You might be a bioengineer at a drug company that designs and manufactures a medication, stating its efficacy based on the calculations that come out of out of one or another bioinformatics or statistics tool, and that drug may end up sickening or killing patients. There is virtually no way to hold the developer(s) of that software to account for that outcome; it is contingent on you to assure regulators of the safety of your product.
Bioinformatics is about information as the name aptly states (even though originally that was not the intent).
Initially, "informatics" meant the use of information technology (computers) to process data of biological significance. But the more we know about how the cell operates the more we understand that it is the information encoding and information processing of the cell that we measure with bioinformatic techniques. We are in the science of information interpretation first and foremost.
A cell is not a like a clock, a cell is not like a transistor, a cell is not like an engine. All of these examples are engineering products - the cell is radically different from each. So how could bioinformatics be engineering? I might even venture to say that bioinformatics is the "opposite" of engineering.