Project Communications Officer

Days tend to involve drafting status updates, designing stakeholder briefings, writing newsletters or change comms, and coordinating with project teams on what to say and when. You might prep a town hall slide deck Monday, draft a community FAQ Tuesday, and write a stakeholder email Thursday. The work tends to live in comms platforms, project schedules, and conversations with subject-matter experts.

The harder part is often balancing transparency against the things the project team isn't ready to commit to publicly. Stakeholders want certainty; projects rarely have it. Diplomatic clarity — saying enough to be useful without overpromising — is the daily craft. Variance across employers is real — large public-sector projects run with formal media protocols and political sensitivity; internal IT projects move faster with less external scrutiny. Tone calibration across audiences is a steady skill.

People who tend to thrive here are clear writers, calm communicators under pressure, and comfortable working with technical content they don't fully own. They tend to enjoy being the bridge between project teams and the people watching them. The trade-off can be bearing the message when news isn't good — communications people often deliver the difficult updates.