Professional Practice, Standards, and Ethics
Professional Practice, Standards, and Ethics tests judgment: how an engineer handles safety, privacy, intellectual property, conflicts of interest, and compliance with standards. Questions are scenario-based and ask what a responsible professional should do.
Core rules
Professional codes generally prioritize public safety, competence, honesty, confidentiality, and avoidance of conflicts of interest. Intellectual property includes copyright, patents, trademarks, and trade secrets, each with different protections. Privacy principles include purpose limitation, data minimization, and lawful handling of personal data. Standards such as ISO/IEC and IEEE documents provide agreed requirements and test methods, but applying a standard does not automatically make a system safe or ethical. Whistleblowing is a last resort after internal escalation, and it should be documented and proportionate.
Worked example
An engineer finds a serious vulnerability before release and is told to hide it to protect the schedule. The defensible response is to document the finding, escalate through management and security channels, assess user impact, and insist on remediation or disclosure consistent with policy and law. Public safety outweighs schedule pressure. The engineer should not publish exploit details irresponsibly, but silence that leaves users exposed is also wrong.
Traps
Employer loyalty does not override public safety. Legality is not the same as ethics, and an approved process can still produce a harmful outcome. Do not cite a standard as proof of correctness without checking its scope. Confidentiality does not require concealing a danger from those who need to act on it.