Media Relations Officer (Marketing Communications Professional III)
Fowler College of Business at San Diego State University · San Diego, CA · 1 mo ago
Marketing$7k–$10k/moFull-time
We need to output only HTML fragment, using for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info. Include sections only when posting has real specific content. So we need to parse the posting.
Let's extract sections:
- About the role: The "Position Summary" and description of role. Could be "About the role". We'll include a
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info. Include sections only when posting has real specific content. So we need to parse the posting.
Let's extract sections:
- About the role: The "Position Summary" and description of role. Could be "About the role". We'll include a About the role
with paragraphs summarizing.
- Responsibilities: The "What You’ll Do" section with bullet points. We'll make Responsibilities
with - items.
- Requirements: The "What We’re Looking For" maybe qualifies as Requirements. Also "Education And Experience" and "Key Qualifications". Could combine. We'll have
Requirements
with paragraphs and list.
- Qualifications: Could separate "Key Qualifications" and "Preferred Qualifications". But we need to avoid thin sections. Maybe combine into one Qualifications section? However we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to include those that have content.
We have:
- Skills: maybe from "Key Qualifications" includes writing, editing, storytelling, media relations, etc. Could be separate Skills section.
- Benefits: definitely present: "Compensation And Benefits" with details.
- Pay: present: compensation step placement, salary range.
- Schedule: present: "Standard SDSU work hours are Monday – Friday, 8:00 a.m. to 4:30 p.m., but may vary based on operational needs. The position is approved for partial telecommuting with onsite work at the San Diego Campus on Monday and Wednesday."
Thus we can include sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
But we must avoid filler like "commensurate with experience". Not present.
We need to preserve all substantive info, not invent or summarize away detail. So we need to include specifics like salary numbers, benefits list, etc.
We need to be careful not to duplicate content. We'll extract.
Let's parse the posting text.
First, "Position Summary" paragraph: "SDSU is seeking a Media Relations Officer with experience in media relations and journalistic science writing — identifying newsworthy research and translating complex findings into clear, accurate, and engaging stories for general audiences. To help tell the stories emerging from the university’s research enterprise, with a particular focus on the College of Engineering, the media relations officer will help tell the stories emerging from the university’s research enterprise. Under the direction of the senior director of media relations and deputy chief communications officer, work directly with researchers, faculty, university leaders, reporters, and fellow communicators to translate complex ideas into compelling stories and help those stories reach audiences locally, nationally, and internationally. This is a hands-on communications role with plenty of variety. One day, you may be interviewing a researcher, writing about a new discovery and pitching the story to national media; another, you may be developing a communications plan as part of a college-wide initiative, preparing a faculty member for an interview, responding to a media inquiry, or creating multimedia and social media content. You will also monitor news and online conversations, assess emerging issues and reputational risks, and recommend messaging and communications strategies."
We'll put that in About the role.
Responsibilities: The "What You’ll Do" section with subheadings: Research Storytelling & Content, Media Relations, College of Engineering Communications, Issues & Emerging Communications. Each has bullet points.
We'll combine into a list of responsibilities.
Let's extract bullet points:
Research Storytelling & Content:
- Find compelling stories across SDSU’s research enterprise, particularly in engineering, science, and technology.
- Translate complex research into clear, engaging stories for SDSU NewsCenter, SDSU Magazine, websites, social media, external media pitching, and other channels.
- Develop multimedia and short-form content that expands the reach of research stories.
Media Relations:
- Develop targeted pitches, news releases, media advisories, and communications plans.
- Build relationships with regional, national, and international reporters and identify opportunities to connect SDSU experts with the news.
- Coordinate interviews and prepare faculty and staff for media engagement.
- Respond to media inquiries and develop recommended messaging and statements.
College of Engineering Communications:
- Serve as a key communications partner to College of Engineering faculty and leadership.
- Identify stories, develop communications strategies, and coordinate media relations, editorial, and social media efforts.
- Develop the College of Engineering newsletter
- Collaborate across StratComm and with campus communications partners to keep messaging aligned.
Issues & Emerging Communications:
- Monitor news and social media for emerging issues, misinformation, and reputational concerns.
- Draft holding statements, FAQs, reactive messaging, and communications recommendations.
- Balance proactive storytelling with the real-time communications needs of a large public research university.
We'll put these as - items.
Requirements: This could include "What We’re Looking For" paragraph plus Education And Experience plus Key Qualifications maybe.
What We’re Looking For paragraph: "We’re looking for an experienced communicator who can move comfortably between journalistic science writing, media relations and strategic communications. You should be able to interview researchers and translate complex scientific and technical information into clear, accurate and compelling stories for general audiences. This is not a grant writing or technical writing role. You should be able to make complicated subjects accessible, recognize a strong story, build relationships with reporters, manage competing priorities, and exercise good judgment when issues move quickly. Above all, this role is for someone who is curious enough to dig into a complicated subject, confident enough to ask the follow-up question, and adaptable enough to switch gears when the story changes."
Education And Experience: "Equivalent to a bachelor’s degree in a related field and four years of relevant experience. Additional experience which demonstrates acquired and successfully applied knowledge and abilities shown above may be substituted for the required education on a year-for-year basis. An advanced degree in a related field may be substituted for the required experience on a year-for-year basis."
Key Qualifications list:
- Demonstrated experience in strategic communications, media relations, and science or research communications, preferably within a large organization.
- Exceptional writing, editing, and storytelling skills, with the ability to translate complex scientific, engineering, and technical information into clear, compelling content for broad audiences.
- Proven success developing media strategies, building relationships with reporters, and securing earned media coverage at the regional, national, or international level.
- Experience advising executives, faculty, researchers, or subject-matter experts on media engagement, strategic messaging, issues management, and reputational considerations.
- Ability to develop and execute integrated communications across earned media, digital, social, editorial, and multimedia channels.
- Demonstrated ability to independently manage complex, cross-functional communications projects, balance competing priorities, and collaborate effectively with a wide range of stakeholders.
- Experience using media analytics, audience insights, and performance data to evaluate communications efforts and inform strategy.
- Strong knowledge of communications and editorial best practices, including AP Style.
Preferred Qualifications:
- Experience supporting science, research, engineering, or technology communications within higher education, a research institution, public agency, or similarly complex organization.
- Knowledge of higher education communications and the research environment, particularly within a public research university.
- Professional proficiency in Spanish is desirable.
Licenses/Certifications Required: "Valid California Driver’s License or the ability to obtain one within 30 days of hire."
We could include Licenses under Requirements or maybe separate but not in headings list. Since not in headings list, we could incorporate into Requirements.
We need to decide sections: Requirements (education/experience), Qualifications (key qualifications), Skills (maybe from key qualifications?), but we have overlapping.
Better to follow the headings list strictly: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Thus we need to map content:
- About the role: Position Summary paragraph.
- Responsibilities: What You’ll Do bullet points.
- Requirements: Education And Experience + What We’re Looking For? Actually "What We’re Looking For" is more about desired attributes, could be Requirements. We'll include Education And Experience and maybe Licenses.
- Qualifications: Key Qualifications (maybe also Preferred Qualifications). We'll list them.
- Skills: Could be the specific skills like writing, editing, storytelling, media relations, etc. But we already have those in Qualifications. To avoid duplication, we could put Skills as a subset: maybe list of skills like "writing, editing, storytelling, media strategy, media relations, interview preparation, multimedia content development, social media, crisis communication, AP Style". But we must not invent. We can extract from Key Qualifications: exceptional writing, editing, storytelling skills; ability to translate complex scientific...; proven success developing media strategies; building relationships with reporters; securing earned media; advising executives; ability to develop integrated communications; manage projects; experience using media analytics; strong knowledge of communications best practices including AP Style. Those are skills. So we could put Skills section with those bullet points.
- Qualifications could then be the experience and education requirements? But we already used Requirements for education/experience. Hmm.
Alternative: Use Requirements for education/experience, Qualifications for key qualifications (including preferred), Skills for specific skillset (maybe from key qualifications). But that may cause duplication.
Given instruction: "Prefer a few substantive sections over many thin ones." So we might combine Qualifications and Skills into one section? But headings list includes both; we could still include both if they have substantive content. However we risk thin sections.
We could make Qualifications include both key and preferred qualifications, and Skills could be omitted if we think it's thin. But we need to follow instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if we think Skills section would be thin (just a list of skills already covered), we could omit it. But we need to decide.
Let's see if there is distinct skills content separate from qualifications. The posting includes "Exceptional writing, editing, and storytelling skills..." etc. That's skills. Could be placed under Skills. Meanwhile Qualifications could be education/experience and licenses. But we already have Requirements for education/experience. Hmm.
Maybe we treat:
- About the role: Position Summary.
- Responsibilities: What You’ll Do.
- Requirements: Education And Experience + Licenses/Certifications.
- Qualifications: Key Qualifications + Preferred Qualifications.
- Skills: maybe we could omit because it's covered in Qualifications. But we need to see if there is any explicit "Skills" section in posting. Not really; they talk about skills within qualifications. So we could omit Skills section to avoid thin.
- Benefits: Compensation And Benefits details.
- Pay: Compensation details (salary range, step placement).
- Schedule: Work hours and telecommuting details.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
We need to use
for each heading.
Now we need to preserve all substantive info. Let's extract exact phrasing.
About the role: We'll use the Position Summary paragraph(s). Might need to keep as is, maybe split into multiple
but we can keep as one
with the text.
Responsibilities: We'll create
- for each bullet point. We'll keep the bullet text exactly as in posting.
Requirements: Include Education And Experience paragraph(s) and Licenses/Certifications. Also maybe "What We’re Looking For" could be considered Requirements but we already used that for Responsibilities? Actually "What We’re Looking For" is more about desired attributes; we could put it under Requirements as well. But we need to avoid duplication. Let's decide: We'll put Education And Experience and Licenses under Requirements. We'll put "What We’re Looking For" under Qualifications? Hmm.
Better: Requirements = Education And Experience + Licenses. Qualifications = Key Qualifications + Preferred Qualifications + What We’re Looking For (since that's about desired attributes). That seems logical.
Thus:
Requirements
Requirements
with paragraphs and list. - Qualifications: Could separate "Key Qualifications" and "Preferred Qualifications". But we need to avoid thin sections. Maybe combine into one Qualifications section? However we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to include those that have content. We have: - Skills: maybe from "Key Qualifications" includes writing, editing, storytelling, media relations, etc. Could be separate Skills section. - Benefits: definitely present: "Compensation And Benefits" with details. - Pay: present: compensation step placement, salary range. - Schedule: present: "Standard SDSU work hours are Monday – Friday, 8:00 a.m. to 4:30 p.m., but may vary based on operational needs. The position is approved for partial telecommuting with onsite work at the San Diego Campus on Monday and Wednesday." Thus we can include sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we must avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info, not invent or summarize away detail. So we need to include specifics like salary numbers, benefits list, etc. We need to be careful not to duplicate content. We'll extract. Let's parse the posting text. First, "Position Summary" paragraph: "SDSU is seeking a Media Relations Officer with experience in media relations and journalistic science writing — identifying newsworthy research and translating complex findings into clear, accurate, and engaging stories for general audiences. To help tell the stories emerging from the university’s research enterprise, with a particular focus on the College of Engineering, the media relations officer will help tell the stories emerging from the university’s research enterprise. Under the direction of the senior director of media relations and deputy chief communications officer, work directly with researchers, faculty, university leaders, reporters, and fellow communicators to translate complex ideas into compelling stories and help those stories reach audiences locally, nationally, and internationally. This is a hands-on communications role with plenty of variety. One day, you may be interviewing a researcher, writing about a new discovery and pitching the story to national media; another, you may be developing a communications plan as part of a college-wide initiative, preparing a faculty member for an interview, responding to a media inquiry, or creating multimedia and social media content. You will also monitor news and online conversations, assess emerging issues and reputational risks, and recommend messaging and communications strategies." We'll put that in About the role. Responsibilities: The "What You’ll Do" section with subheadings: Research Storytelling & Content, Media Relations, College of Engineering Communications, Issues & Emerging Communications. Each has bullet points. We'll combine into a list of responsibilities. Let's extract bullet points: Research Storytelling & Content: - Find compelling stories across SDSU’s research enterprise, particularly in engineering, science, and technology. - Translate complex research into clear, engaging stories for SDSU NewsCenter, SDSU Magazine, websites, social media, external media pitching, and other channels. - Develop multimedia and short-form content that expands the reach of research stories. Media Relations: - Develop targeted pitches, news releases, media advisories, and communications plans. - Build relationships with regional, national, and international reporters and identify opportunities to connect SDSU experts with the news. - Coordinate interviews and prepare faculty and staff for media engagement. - Respond to media inquiries and develop recommended messaging and statements. College of Engineering Communications: - Serve as a key communications partner to College of Engineering faculty and leadership. - Identify stories, develop communications strategies, and coordinate media relations, editorial, and social media efforts. - Develop the College of Engineering newsletter - Collaborate across StratComm and with campus communications partners to keep messaging aligned. Issues & Emerging Communications: - Monitor news and social media for emerging issues, misinformation, and reputational concerns. - Draft holding statements, FAQs, reactive messaging, and communications recommendations. - Balance proactive storytelling with the real-time communications needs of a large public research university. We'll put these asfor each heading. Now we need to preserve all substantive info. Let's extract exact phrasing. About the role: We'll use the Position Summary paragraph(s). Might need to keep as is, maybe split into multiple
but we can keep as one
with the text. Responsibilities: We'll create
- for each bullet point. We'll keep the bullet text exactly as in posting. Requirements: Include Education And Experience paragraph(s) and Licenses/Certifications. Also maybe "What We’re Looking For" could be considered Requirements but we already used that for Responsibilities? Actually "What We’re Looking For" is more about desired attributes; we could put it under Requirements as well. But we need to avoid duplication. Let's decide: We'll put Education And Experience and Licenses under Requirements. We'll put "What We’re Looking For" under Qualifications? Hmm. Better: Requirements = Education And Experience + Licenses. Qualifications = Key Qualifications + Preferred Qualifications + What We’re Looking For (since that's about desired attributes). That seems logical. Thus: Requirements