Digital Content Coordinator

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule as appropriate. Must not repeat job title. Must not include Job ID etc. Must include only sections with real specific content. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like EEO, legal, application instructions, cookie/navigation, duplicated lines. Also remove travel mention? Travel is a detail; maybe include in Responsibilities? It's a detail about travel percentage. Could be part of Responsibilities or a separate note. The instruction: include a section ONLY when posting has real, specific content for it. Travel is specific: "Travel: 5 – 10%." Could be placed under Responsibilities or maybe a separate "Travel" but not in list of allowed headings. Allowed headings are only those listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to fit travel into one of those, maybe Responsibilities. We need to parse the posting. Key info: - Organization: ALPA, largest airline pilot union, etc. - Position: Digital Content Coordinator, office in Memphis, Tennessee. - ALPA represents >79k pilots at 42 airlines. - Role description: provides digital content strategy, execution, product development, project coordination including continuous improvement of digital communications products, workflows, member engagement to advance and support FedEx MEC’s Communications Committee and Association’s Communications Department’s digital goals through digital and print design, content editing, posting, maintenance of MEC websites, email communications, social media channels, other ALPA platforms. - Supports mission, vision, values of MEC and Association, seeks to enhance image. - Day-to-day: amplify and deliver communications on behalf of MEC, LECs, MEC-based committees by regularly updating content on MEC websites, assisting in sending mass emails to members, assisting in social media promotion, while working collaboratively with MEC Officers, MEC Communications committee leadership, IT staff, colleagues in other offices. - Recurrent responsibilities include, and are not limited to: content and digital strategy, email design, maintenance, digital and print design from concept to execution, project management. - Exercise independent judgment to identify opportunities for improvement, recommend solutions, develop innovative communications products, advance MEC’s Communications Committee’s strategic objectives. - Interested applicants requested to submit online portfolio link(s) showing previous work. - Travel: 5 – 10%. - ALPA is equal opportunity employer etc (remove). - This position is covered by a collective bargaining agreement. - ALPA is a member-driven, staff supported, union with two internal professional unions. - Minimum Requirements: Bachelor's degree in relevant area, e.g., Digital Media, Communications, Marketing, Public Relations, or related field, preferred, from an accredited college or university; or, the equivalent combination of education and practical experience. - Minimum three (3) years of experience and demonstrated expertise in digital content strategy, website development, and/or digital design, five (5) or more years strongly preferred. - Experience with CMS and controlling page content to communicate goals digitally. - Experience designing within Adobe Creative Cloud: Photoshop, InDesign, Illustrator, and XD. - Experience designing for print and digital media with a proven record of success. - Proficiency in HTML, CSS, Responsive Web Design (W3.CSS), CMS and familiarity with other markup and/or programming languages preferred. - Experience with email platforms and Microsoft Office suite strongly preferred. - Excels in working independently to both initiate and produce products and team projects. - Ability to quality control text documents for distribution on web and email platforms. - Solid interpersonal and communication skills, oral and written, for effective interaction with internal staff, external contacts, and pilots. - Ability to manage multiple projects at once, take direction from multiple sources, and meet deadlines. - Strong writing and proofreading skills with command of grammar, syntax, and usage. - Ability to understand and decipher information and documents of a technical nature. - Experience working with audio and video editing software a plus. - Ability to test and troubleshoot software. - Familiarity with new technologies and software for enhancing text, photographs, and graphics strongly preferred. - Knowledge of labor-related issues preferred. - Ability to facilitate project work with vendors and consultants, as needed. - Software: Proficiency in CMS. Proficiency with Adobe Suite for web publishing and graphic design including Photoshop, Illustrator, InDesign, Acrobat, Premiere Pro, After Effects, Audition, and Dreamweaver. Microsoft Word, Excel, Outlook, PowerPoint, and SharePoint. - Physical Demands: description (we can include maybe under Requirements? but it's not a heading; we could include under Requirements as a paragraph? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to decide which sections to include. We have substantive content for: - About the role: overview of position, organization, purpose. - Responsibilities: day-to-day tasks, recurrent responsibilities. - Requirements: minimum education/experience. - Qualifications: maybe similar to Requirements? The posting lumps Minimum Requirements and then a list of experience/skills. Could treat Requirements as education/experience, Qualifications as skills/competencies. But we must not create thin sections. We could combine Requirements and Qualifications into one section? But headings are predefined; we can choose to include both if they have substantive content. The posting has both education/experience and a list of specific skills/experience. So we can have Requirements (education/experience) and Qualifications (skills). Or we could treat the list as Skills. The instruction says use headings as e.g., but not required to use all. We'll include About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Schedule: not mentioned (no schedule info). So omit Schedule. Benefits: described in detail (401k, health care, vacation, etc). Pay: projected annual salary range $73,625 – $105,108. We need to include travel detail somewhere; maybe under Responsibilities as a bullet. We need to remove boilerplate: EEO, equal opportunity, application instructions (please apply online link), duplicated lines, cookie/navigation/legal. Also remove "This position is covered by a collective bargaining agreement." That's substantive? It's a detail about employment terms; could be included maybe under Benefits or Requirements? It's not a benefit but a condition. Could be placed under Requirements as a note. But we need to preserve all substantive information. So we should keep that statement somewhere. Perhaps under Responsibilities or a separate paragraph after Requirements. Since we don't have a heading for "Employment Terms", we could put it in a

  under Requirements or Benefits. I'd put it under Requirements as a note. Also "ALPA is a member-driven, staff supported, union with two internal professional unions." That's organizational detail; could go under About the role. Physical Demands: substantive; could be included under Requirements or maybe a separate section but not in allowed headings. Could be placed under Requirements as a paragraph. We must not invent or summarize away detail; we need to preserve all substantive info. So we need to include all those details, but we can embed them in paragraphs under appropriate headings. We must not include application instruction link; remove that. We must not include EEO boilerplate; remove. We must not include duplicated lines (like repeated "Experience with CMS"). We need to use

  • for any list of duties/requirements/benefits. So for responsibilities list, we should use
    . For requirements list (education/experience) maybe also list. For qualifications list (skills) also list. For benefits list also list. We need to use

    for prose. We must not repeat job title as heading. We must not include markdown fences. We must output only HTML fragment. Let's structure:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Requirements

    ...

    maybe also list for education/experience. But we need to use
    • for any list of duties/requirements/benefits. So if we have a list of requirements (education/experience), we should use
      . Similarly for qualifications (skills) and benefits. Thus:

      Requirements

      • Bachelor's degree in relevant area (Digital Media, Communications, Marketing, Public Relations, or related field) preferred, or equivalent combination of education and practical experience.
      • Minimum three (3) years of experience and demonstrated expertise in digital content strategy, website development, and/or digital design; five (5) or more years strongly preferred.
      • Position is covered by a collective bargaining agreement.
      • Physical demands: constant computer/smartphone/tablet use; acute vision; regularly required to maintain stationary position, move about office/local area, sit, stand, bend, reach; occasional lifting up to 10 lbs; occasional travel may require handling luggage up to 50 lbs.
      But we need to keep the physical demands description exactly as given? We can paraphrase but must preserve all substantive info; paraphrasing is okay as long as we don't lose detail. However we should try to keep the detail. Could be a paragraph instead of list? The instruction says use
      • for any list of duties/requirements/benefits. Physical demands is not a list but a description; we could put in

        . But we already used

        for requirements; we could add a

        after list. That's fine. Similarly for Qualifications: we could list skills/experience. But we need to avoid duplication: many skills repeated across sections. We need to capture all. Let's extract qualifications/skills list: - Experience with Content Management Systems (CMS) and controlling page content to communicate goals digitally. - Experience designing within Adobe Creative Cloud: Photoshop, InDesign, Illustrator, and XD. - Experience designing for print and digital media with a proven record of success. - Proficiency in HTML, CSS, Responsive Web Design (W3.CSS), CMS and familiarity with other markup and/or programming languages preferred. - Experience with email platforms and Microsoft Office suite strongly preferred. - Excels in working independently to both initiate and produce products and team projects. - Ability to quality control text documents for distribution on web and email platforms. - Solid interpersonal and communication skills, oral and written, for effective interaction with internal staff, external contacts, and pilots. - Ability to manage multiple projects at once, take direction from multiple sources, and meet deadlines. - Strong writing and proofreading skills with command of grammar, syntax, and usage. - Ability to understand and decipher information and documents of a technical nature. - Experience working with audio and video editing software a plus. - Ability to test and troubleshoot software. - Familiarity with new technologies and software for enhancing text, photographs, and graphics strongly preferred. - Knowledge of labor-related issues preferred. - Ability to facilitate project work with vendors and consultants, as needed. - Software proficiency: CMS; Adobe Suite for web publishing and graphic design including Photoshop, Illustrator, InDesign, Acrobat, Premiere Pro, After Effects, Audition, Dreamweaver. - Microsoft Word, Excel, Outlook, PowerPoint, SharePoint. Many of these overlap with earlier bullet points; we can consolidate but must preserve all substantive info. We could combine similar items but not lose detail. However we risk summarizing away detail if we combine too much. The instruction: "Preserve ALL