Client and Employer Obligations
You'll learn how to balance your duty of loyalty to employers with your ethical responsibilities and professional integrity.
The Dual Duty Dilemma
As a software engineer, you owe your employer competence, diligence, and loyalty—but these obligations are not absolute. Your professional responsibilities extend beyond the employment contract: you have duties to the public, to your profession, and to ethical standards that sometimes conflict with what your client or employer asks you to do.
Think of it like being a doctor: you work for a hospital, but your duty to "do no harm" transcends your employment agreement. If your employer asks you to falsify medical records, your professional ethics override employer loyalty.
Navigating the Balance
Competent Work: You must deliver quality work using your best professional judgment. If your employer insists on cutting corners that would create security vulnerabilities or data loss risks, you have an obligation to advocate against it—even if it's inconvenient.
Honesty and Transparency: You should provide accurate assessments of project feasibility, timelines, and risks. Telling your boss what they want to hear rather than the truth violates professional integrity.
Confidentiality with Limits: Respect proprietary information and trade secrets, but this duty has boundaries. If you discover your employer is violating laws, harming users, or creating dangerous systems, whistleblowing may be ethically required despite confidentiality agreements.
When Loyalty Ends: Your obligation to your employer stops when asked to do something illegal, unethical, or harmful. You're never obligated to write code that violates privacy laws, discriminates against users, or knowingly ships unsafe systems.
Key Takeaway: Your loyalty to employers is important but subordinate to your ethical duties to the public, users, and your profession—advocate internally first, but be prepared to refuse unethical directives or escalate when necessary.