Professional Ethics, Communication, and Teamwork
What this domain tests
Professional Ethics, Communication, and Teamwork tests judgment in IT practice: confidentiality, conflicts of interest, intellectual property, privacy, accessibility, clear communication, and constructive team behavior. Expect scenario questions, not definitions alone.
Core rules and concepts
- Professional codes such as ACM/IEEE prioritize public safety and the public interest, avoid harm, be honest, respect confidentiality, and maintain competence.
- Confidential data should be accessed only on a need-to-know basis and never forwarded to personal accounts or discussed in public channels.
- Cite code, data, and text you did not create. Paraphrasing without attribution is still plagiarism.
- Conflict of interest: disclose it and recuse yourself when a personal interest could bias a technical decision.
- Good communication adapts to the audience: users need impact and action; developers need reproducible detail. Active listening includes paraphrasing and confirming.
Worked example
You find a teammate’s commit containing a hardcoded database password. Ethical response: do not exploit it or post it publicly; report it privately to the teammate and the security lead, recommend rotating the credential and using a secret manager, and document the fix. This respects confidentiality, protects users, and follows the duty to avoid harm. Public shaming or silent deletion both create risk.
Traps that cost marks
Equating legal with ethical. Forwarding confidential data “just to get help.” Copying code without a license check. Treating teamwork as agreeing with everything; healthy teams test ideas and resolve conflict with evidence.