Communications Specialist
- for any list of duties/requirements/benefits. So responsibilities list: we have many bullet-like sentences. We'll convert each line into
- . Similarly requirements list: bullet points. Benefits list: bullet points.
We need to ensure we don't create sections with filler text. All sections have content.
We must not include markdown fences. Just raw HTML.
Let's craft:
About the role
Starting Salary Range: $75,518 - $90,621. GGRC is looking to hire a Communications Specialist for our San Francisco Office, also open to our offices in San Mateo, and San Rafael, CA. The Communications Specialist for GGRC serves as a go-to resource for quality, accessibility, and inclusive communications across all of GGRC’s internal and external channels. This role supports the implementation of communications strategies, manages workflows, and helps build and maintain the internal systems and practices that enable effective communication across the organization. Working in partnership with GGRC leadership and program teams, the Communications Specialist focuses on project management, coordination, and execution of communications across departments. The role ensures that communications are clear, consistent, timely, and aligned, while keeping complex, multi-stakeholder projects on track. At the center of this role is a commitment to accessible, inclusive, person-centered and disability-forward communication. The Communications Specialist helps ensure that all communications reflect dignity, clarity, and respect, and that accessibility is embedded as a standard across all of GGRC internal and external channels. This position will require local travel within the Counties of San Francisco, San Mateo and Marin. Periodic travel to Sacramento and throughout the state. Access to reliable transportation permitting travel to and between many different locations throughout the day to perform the outlined responsibilities of the position. GGRC values diversity, we believe in creating an environment where people of all backgrounds can collaborate to find solutions to complex problems. We are community minded and passionate. GGRC values each person as a full, robust, and unique individual and interacts with each person in a manner that is respectful and responsive. We endeavor to place each person at the center of his, her or their own life. We approach each person as an expert on his, her or their own life and identity with a clear and attentive inquiry into what is important to, as well as important for, that one person (whether coworker or person-served, family member or other stakeholder).
Then Pay section? Actually we already included salary in About the role. But the instruction: "Prefer a few substantive sections over many thin ones." Could combine salary into About the role. However they said: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text ... and never create Pay/Schedule/Benefits sections unless the posting actually states them." They didn't forbid including salary in About the role. But they also said usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have a Pay section separate. But we already placed salary in About the role; we could still have a Pay section with just the salary range. That would be thin but still substantive (salary range). It's okay. However they said prefer a few substantive sections over many thin ones. Having both About the role and Pay might be thin Pay but still specific. Could embed salary in About the role to avoid thin Pay. I'd lean to embed salary in About the role to keep fewer sections. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's just examples, not mandatory to use all. So we can omit Pay heading if we include salary elsewhere. That seems fine. Thus sections: About the role, Responsibilities, Requirements, Benefits. Now responsibilities: need to extract list items from the responsibilities block. The block includes multiple paragraphs each starting with a bold heading? Actually the text: Responsibilities Communications Coordination & Implementation Implement communications strategies and tactics aligned with GGRC’s mission and priorities Maintain communication planning tools, calendars, and coordination systems Coordinate editorial calendars, cross-team content workflows, and messaging across teams to ensure consistency and alignment Track deliverables, timelines, and dependencies across multiple projects Ensure that requests that come through the website contact and elsewhere are routed to the appropriate department Channel Management & Quality Serve as a quality control lead across all communications, ensuring clarity, consistency, and alignment with established standards Ensure all communications meet accessibility and inclusion standards (plain language, ADA compliance, multilingual access where appropriate) Manage and maintain communications channels, including website, social media, newsletters, and publications. Make sure information is accurate and current, especially on the website Use analytics, feedback, and community input to spot gaps or inconsistencies and drive continuous improvement Identify when to leverage external consultants or additional resources Communications Culture & Capacity Building Implement an/or Support department teams in developing and delivering clear, consistent communications; maintain feedback loops that surface staff insights; and ensure materials are accurate, timely, and aligned with organizational priorities Serve as a resource and partner to staff, helping them communicate clearly and effectively Develop and maintain templates, tools, and guidance for consistent communications Support trainings and coaching to strengthen staff and board communication skills at all levels of the organization Reinforce best practices in accessible, inclusive, and respectful communication Help build a culture of clarity, responsiveness, and accountability in communications Support storytelling efforts by helping staff identify and capture compelling stories that reflect GGRC’s impact Identify growth areas and bring in third party experts as needed to strengthen the team’s communications skills External Communications Coordinate communications to priority audiences, including individuals with developmental disabilities, families, providers, policymakers, and community partners Support development and distribution of external communications (e.g., announcements, updates, press releases) Ensure materials reflect dignity, clarity, and lived experience of the communities GGRC serves Coordinate media inquiries, public statements, and outreach logistics as needed Coordinate communications for events, including timelines, materials, and outreach, ensuring clear, consistent, and accessible information for all audiences Issues Response & Leadership Support Support coordination of communications for time-sensitive or high-visibility issues Draft and refine messaging, talking points, and materials for leadership as needed Help track external developments (policy, media, community context) and flag implications Coordinate internal workflows to ensure timely and consistent responses Support preparation of leadership and board-facing materials Support special event planning and implementation as needed We need to turn each line after the headings into
- . The headings themselves (like Communications Coordination & Implementation) are not list items but could be considered subheadings; but we are not to create extra headings beyond h3. Could we treat them as plain text within
- ? Probably better to keep them as part of list items? Actually they are section titles within responsibilities; we could keep them as plain text (not heading) but they'd be lost if we just list items. However we could include them as
- with bold? But we cannot use markdown; we can use . The instruction didn't forbid using . It only said use
for section headings,
- for any list,
for prose. So we can embed inside
- . That's acceptable. Thus we create
- with each responsibility as
- . We'll include the subsection titles as maybe.
Similarly Requirements: list items.
Requirements block:
Education/Experience
Master’s degree preferred.
Require BA (Communication, marketing, Business, literature, or related
5–8+ years of experience in communications, public affairs, or a related field
Experience managing social media for similar organizations
Experience coordinating communications across teams or departments
Demonstrated experience supporting disability inclusion, accessibility, and respectful representation
Preferred Experience in disability services, healthcare, statewide government or regulatory agencies
Familiarity with legislative and public policy processes
Experience working in multi-stakeholder or highly regulated environments
Experience with content management systems and video/visual storytelling tools
Multilingual skills (e.g., Spanish, Chinese, Tagalog)
We need to treat each line as
- . The first line "Education/Experience" maybe a heading; we could make it inside
- . Or we could treat as separate
but they said use
- for any list of duties/requirements/benefits. So we should put all requirement lines in a
- . We'll include the "Education/Experience" as a
- with .
Benefits block:
Benefits
What are the benefits to working with GGRC? We offer a comprehensive benefits package including Medical and Dental benefits with a generous employer contribution and additional employer paid Life, Disability and Vision coverage
10% employer contribution to a 403(b) retirement account to help you save for the future!
GENEROUS TIME OFF BENEFITS!!! No Really, We Mean Generous 13 vacation days, 15 sick days, 11 paid holidays, 6 personal holidays, and up to 5 paid days for continuing education
We need to make list items: maybe each sentence as
- . The first sentence is a description; we could keep as
- . Then the 10% line as
- . Then the time off line as
- . Could also split time off into separate items but it's okay as one. We must not include boilerplate like "How To Apply", EEO, etc. Now construct HTML. We'll start with
About the role
... include salary and description.
ThenResponsibilities
- ...
Requirements
- ...
Benefits
- ...
- with .
Benefits block:
Benefits
What are the benefits to working with GGRC? We offer a comprehensive benefits package including Medical and Dental benefits with a generous employer contribution and additional employer paid Life, Disability and Vision coverage
10% employer contribution to a 403(b) retirement account to help you save for the future!
GENEROUS TIME OFF BENEFITS!!! No Really, We Mean Generous 13 vacation days, 15 sick days, 11 paid holidays, 6 personal holidays, and up to 5 paid days for continuing education
We need to make list items: maybe each sentence as
- . The first line "Education/Experience" maybe a heading; we could make it inside
- . That's acceptable. Thus we create
- for any list,