Associate Director, Publishing

for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate like cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info; do not invent or summarize away detail. Remove filler like "commensurate with experience". Include a section only when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Key sections: - Role Summary (maybe "About the role"): The paragraph about Associate Director, Publishing provides strategic leadership... etc. That's prose. - Supervisory Responsibilities: bullet list. - Responsibilities: includes subsections: Portfolio Strategy and Performance, Strategic and Business Leadership, Leadership and Culture. Could combine under "Responsibilities" heading with sub-bullets. - Required Qualifications & Skills: list of qualifications. - Preferred: maybe include under Qualifications? Could be separate "Preferred Qualifications" but we can include under same heading? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "Qualifications" for required qualifications, maybe also "Preferred Experience". But we can combine. - Physical Requirements And Work Environment: maybe not needed as separate heading unless we have content. It includes prolonged periods stationary, travel, flexibility across time zones. Could be part of "About the role" or separate "Work Environment". But we have no specific heading for that; we could include under "About the role" or maybe "Requirements". However instruction: include a section only when posting has real, specific content for it. There is content, but we don't have a standard heading for Physical Requirements. Could we put under "Requirements"? Probably better to include under "About the role" as prose. - Pay: The base salary range given: US $145,000- $157,000 or UK £90,000- £104,000. That's specific. So we need a Pay section. - Benefits: detailed list for US and UK. So Benefits section. - Schedule: Not explicitly given; only mention fully remote, some flexibility across time zones. Not a schedule like full-time/part-time. Could we infer? Probably not enough specific schedule info. So we should NOT create Schedule section. - Requirements: maybe we can have a "Requirements" section for required qualifications? But we already have Qualifications. The instruction list includes Requirements as possible heading. Could we split required qualifications under "Requirements" and preferred under "Qualifications"? But we need to avoid thin sections. Perhaps combine required and preferred under "Qualifications". However we have "Required Qualifications & Skills" heading in original. So we can use "Qualifications" for that. - Skills: maybe separate? But we can include skills within Qualifications. Thus sections: About the role (role summary + supervisory responsibilities?), Responsibilities (portfolio strategy, strategic business leadership, leadership and culture), Qualifications (required qualifications & skills + preferred), Benefits, Pay. We need to use

for each section heading. Inside sections, use

• for any list of duties/requirements/benefits, and

  for prose. We must not repeat job title as heading. The job title is Associate Director, Publishing. Not to be used as heading. We must not include Job ID/requisition numbers. We must remove boilerplate: EEO, equal opportunity, privacy notice, etc. Also remove duplicated lines. We need to preserve all substantive information. Let's extract content. Role Summary paragraph: "This position is fully remote/home based. Applications will be accepted from candidates based in the UK and the following US states: FL, IL, MA, MD, NY, PA, TX, VA. Role Summary The Associate Director, Publishing provides strategic leadership for the PLOS journal portfolio, ensuring that portfolio priorities, publishing investments, and journal development strategies align with organizational goals and advance PLOS's mission. Reporting to the Director, Publishing & Publishing Operations, the Associate Director leads and develops a team of Publishers responsible for the performance and strategic development of journals portfolios. The Associate Director serves as the primary steward of portfolio-wide publishing performance, translating organizational strategy into clear priorities and ensuring effective coordination across the organization. The Associate Director uses publishing data, financial information, market intelligence, and research community insight to guide strategic decisions, establish priorities, identify opportunities for growth and innovation, and manage risks. Working in partnership with the Director, Publishing & Publishing Operations, the Associate Director ensures that journal-level strategies collectively support a sustainable PLOS portfolio with a strong value proposition." We need to keep that. Supervisory Responsibilities bullet list: "Lead, develop, and support a team of senior publishing professionals responsible for journal and subject portfolio performance. Establish clear goals, priorities, and measures of accountability that align with organizational and portfolio strategy. Provide coaching, professional development, succession planning, and performance management for direct reports. Foster a culture of collaboration, inclusion, accountability, innovation, and continuous improvement. Work with Publishers to ensure effective leadership and development of Journal Development Managers and other publishing staff." We can put under a subheading? But we only have h3 headings allowed. Could we embed as a list under About the role? Probably better to have a separate section for Supervisory Responsibilities? But we don't have a standard heading for that. Could incorporate under Responsibilities or About the role. Since we have a Responsibilities section, we could include supervisory responsibilities there. However the posting separates Supervisory Responsibilities as its own heading. We could still include it under Responsibilities as a list. Responsibilities sections: - Portfolio Strategy and Performance: bullet list of duties. - Strategic and Business Leadership: bullet list. - Leadership and Culture: bullet list. We can combine all under Responsibilities heading with sub-lists maybe using nested lists? But instruction: use

  • for any list of duties/requirements/benefits. Could have multiple
    inside section. We'll produce:

    About the role

    ... (role summary paragraph)

    Responsibilities

    • Lead, develop, and support a team of senior publishing professionals responsible for journal and subject portfolio performance.
      • Establish clear goals, priorities, and measures of accountability that align with organizational and portfolio strategy.
      • Provide coaching, professional development, succession planning, and performance management for direct reports.
      • Foster a culture of collaboration, inclusion, accountability, innovation, and continuous improvement.
      • Work with Publishers to ensure effective leadership and development of Journal Development Managers and other publishing staff.
    • Portfolio Strategy and Performance
      • Develop and implement a portfolio-wide publishing strategy aligned with PLOS's mission and organizational objectives.
      • Ensure that journal and subject portfolio strategies collectively support a clear and differentiated value proposition for the PLOS portfolio.
      • Lead regular portfolio reviews and develop recommendations regarding journal positioning, growth opportunities, performance, and future direction.
      • Balance the needs of individual journals and research communities with broader portfolio and organizational objectives.
      • Support Publishers in identifying and responding to changes in research communities, funding policies, scholarly communication, and the publishing market.
      • Develop consistent approaches and decision-making frameworks for evaluating proposals, opportunities, and performance across the portfolio.
      • Guide the evaluation and development of new journals, products, services, publishing models in line with PLOS’s strategic direction.
    • Strategic and Business Leadership
      • Translate organizational strategy into clear portfolio priorities, objectives, and plans for the publishing team.
      • Oversee publishing budgets and forecasts in partnership with the Director and Publishers, ensuring responsible decision-making and effective resource allocation.
      • Act as a thought partner to, and deputize for, the Director, Publishing & Publishing Operations when appropriate.
      • In close collaboration with colleagues in Editorial, Sales and Global Publishing Development, support publishers in developing impactful relationships with Editors-in-Chief, Editorial Board members, researchers, institutions, societies, and partner organizations.
      • Build productive partnerships across Editorial, Publishing Operations, Sales & Global Publishing Development, Product, Technology, Marketing, Finance, Research Integrity, and other organizational teams.
      • Work with Editorial and Publishing Operations leaders to ensure that journal strategies are supported by effective policies, processes, services, and quality standards.
      • Partner with Marketing and Communications to strengthen journal positioning, audience engagement, portfolio visibility, and demand generation.
    • Leadership and Culture
      • Model the culture and behaviors PLOS is seeking to build, actively driving the culture change the organization needs through this transformation.
      • Serve as a collaborative leader across PLOS, fostering strong cross-functional partnerships and organizational alignment that enable shared organizational priorities to be delivered successfully.
      • Lead change effectively by ensuring a clear strategic rationale, defined outcomes, appropriate measures of success, realistic resource requirements and clear accountability and decision-making.
    But we have nested lists; maybe better to keep top-level list for each major bullet and sub-items as separate
    inside
    • . That's acceptable. Now Qualifications section: Required Qualifications & Skills list: - Bachelor's degree or equivalent experience. - Business problem solver – operates with curiosity to get to the root of the business problem to ensure the ultimate solution is grounded in PLOS’s strategy and mission. - Substantial experience launching Open Access journals from proposal to publication. - Strong commercial and financial skills, including experience with budgeting, forecasting, business planning and P&L ownership. - Substantial experience in STM publishing with progressively increased responsibility. - Experience managing senior publishing professionals, or comparable portfolio leaders. - Proven ability to develop and execute strategic plans that deliver measurable business and operational outcomes. - Strong track record of leading and developing high-performing, geographically distributed teams. - Exceptional communication, relationship-building, and stakeholder management skills across cultures, disciplines, and organizational functions. - Dedication to open access and transforming scholarly communication, with a genuine interest in engaging productively with the scientific community. Preferred: - Experience leading high-volume journal portfolios and/or megajournals. We can combine required and preferred under Qualifications heading, maybe separate subheadings? But we only have h3 headings; we could have a

      for required and then a

      for preferred? Or we could have two
      lists: one for Required Qualifications, one for Preferred Experience. But we need to avoid thin sections; we can keep both under Qualifications. We'll output:

      Qualifications

      Required

      ... but we cannot use h4? The instruction only mentions h3 for section headings. It didn't forbid other headings, but to be safe we can just use

      for required heading and then list. However we need to preserve structure. Could do:

      Required Qualifications & Skills:

      ...
      But we must not invent headings beyond h3? The instruction: "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but to be safe we can avoid other heading levels. We'll just use

      for subsection labels. Thus:

      Qualifications

      Required Qualifications & Skills:

      • Bachelor's degree or equivalent experience.
      • Business problem solver – operates with curiosity to get to the root of the business problem