Computer Engineering Laws and Ethics Practice Reviewer

So, you’ve studied Republic Act 9292 and memorized the Code of Ethics. But memorizing definitions is easy; applying them to real-world engineering nightmares is hard. Let’s test your knowledge with situations you might actually face in your career.

Practice Questions: The “Real World” Edition

---

1. The “Moonlighting” Dilemma

Scenario: You work full-time for TechCorp. A small startup approaches you to design a system on weekends. It pays well. According to the Code of Ethics, what must you do before saying “Yes”?

1. Ask for payment in cash to avoid taxes.
2. Inform TechCorp (your current employer) about this new engagement.
3. Resign from TechCorp immediately.
4. Accept it secretly; what they don’t know won’t hurt them.

2. The “Conflict of Interest” Trap

Scenario: Your company is bidding to supply computers to a university. You are the lead engineer evaluating the bids. Turns out, your brother owns the company that is bidding. What is your ethical duty?

1. Give your brother the project because family comes first.
2. Reject his bid immediately to look impartial.
3. Disclose the relationship to your boss and recuse yourself from the decision-making process.
4. Tell your brother to lower his price so he wins “fairly.”

3. The “Blueprint Sign-Off”

Scenario: You are a Registered Computer Engineer (CpE). Your boss hands you a set of electronics plans for a building permit and says, “Sign and seal these so we can submit them to City Hall.” What do you do?

1. Sign it proudly; you are an engineer!
2. Refuse. Only a Professional Electronics Engineer (PECE) can sign and seal plans for building permits.
3. Sign it but use a red pen to show it’s unofficial.
4. Ask a Master Electrician to sign it instead.

4. Safety vs. Savings

Scenario: Your client wants to save money by removing a safety redundancy in a server room cooling system. They say, “It rarely overheats anyway.” Who is your primary obligation to?

1. The Client (because they pay the bills).
2. Your Employer (who wants to keep the client happy).
3. The Public Safety and Welfare (preventing fires/system failures).
4. Yourself (avoiding an argument).

---

Answers & Explanations (The “Why”)

1. Answer: B (Inform TechCorp)
Why? Professional ethics demand transparency. Your employer pays for your energy and time; moonlighting might affect your performance or create a conflict (e.g., using TechCorp’s secrets for the startup). Always get permission.

2. Answer: C (Disclose and Recuse)
Why? Even if you are honest, the appearance of bias destroys trust. By disclosing it and stepping aside (recusing), you protect your professional integrity and the validity of the bidding process.

3. Answer: B (Refuse – PECE Only)
Why? Under RA 9292, not all licenses are equal. While CpEs and ECEs are licensed, the authority to seal plans for government permits is reserved for the “Professional” grade (PECE). Signing it yourself constitutes illegal practice.

4. Answer: C (Public Safety)
Why? This is the Golden Rule of Engineering. Engineers possess technical knowledge the public does not. It is our duty to protect people, even if the client wants to cut corners. If a fire starts because you removed a safety feature, you are liable.