Communicating Professionalism
Communicating Professionalism was a ten-week professional-skills general education course, and I want to be honest about its scope up front. It was a soft-skills requirement rather than anything technical, and I went in expecting to check a box. What I came away with was a clearer sense of how much of my actual job is communication, not configuration.
What the course covered
The course moved through the pieces of professional presence one at a time. Early units looked at professional image in IT, dress, behavior, and reliability, and I made the case that in my field appearance matters less than being responsive, dependable, and clear. From there it worked through personal branding: building out a LinkedIn profile, writing a video resume script, and thinking about how social media shapes how employers see you.
The back half leaned into communication itself. I studied the difference between hearing and active listening across different settings, presentation skills and managing the anxiety that comes with them, and how to handle office politics and logical fallacies without letting a disagreement become personal. A unit on professional ethics had me analyze the ACM Code of Ethics, which lined up neatly with the compliance work I already do. The course closed on teamwork, evaluating a group scenario for conflict, leadership, and what makes a team actually productive.
Takeaway
The honest value here is that most of my technical work depends on explaining things to people who do not share my background. Presenting a patch status or an outage report to leadership is a communication problem before it is a technical one. This course did not teach me anything I could point to on a diagram, but it did make me more deliberate about writing clearly, listening before responding, and framing technical detail for the person on the other side of it.