Jobs · OTHR · California

Community Experience Specialist

Fuel Cycle · Los Angeles Metropolitan Area · 1 mo ago
HybridOTHR$65k–$75k/yrFull-time
We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the posting. Sections: - About the role: The first paragraph about Fuel Cycle? Actually "About Fuel Cycle" is company description. Could be "About the role"? The posting includes "Overview" then "Key Responsibilities", "Your Success Metrics", "Who you’ll work with?", "Skills", "What You’ll Bring", "Benefits & Perks", "Compensation Overview". Also "Location: Los Angeles, CA Work Arrangement: ...". So we need to map. We need sections: About the role (maybe overview of role), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: Could be the "Overview" paragraph: "The Community Experience Specialist is responsible for executing all assigned tasks related to audience recruitment, rewards and incentives, member engagement and audience operations/administration. Projects will be deployed by Audience Experience Strategists or Managers. Community Experience Specialists may have a small book of business as determined by the Audience Experience Manager." Also location and work arrangement maybe part of About the role? But schedule section separate. - Responsibilities: "Key Responsibilities" bullet list (though not bullet but paragraphs). We'll need to convert to
  • . The responsibilities include: Audience Operations & Engagement (list subpoints), Project Support & Execution, Customer Interaction & Account Support, Quality Assurance & Administration. We'll need to extract each bullet. - Requirements: Possibly "What You’ll Bring" includes education, experience, etc. Also "Who you’ll work with?" maybe not requirements. Requirements could be education, experience, etc. Qualifications maybe similar. But we need to separate Requirements and Qualifications if distinct. The posting has "What You’ll Bring" which includes Education, Experience, Detail-Oriented, Team Player, Multi-Tasking, Customer Focus, Analytical Skills, Communication, Adaptability, Problem-Solving, Empathy, Organizational Skills. Also "Skills" section includes Core Skills & Competencies and Competencies and Attributes. So we need to map. We have a "Skills" heading already in the posting: "Skills Core Skills & Competencies:" etc. So we should create a Skills section with that content. Requirements could be the "What You’ll Bring" (education, experience). Qualifications maybe not separate; but we could treat "What You’ll Bring" as Requirements (or Qualifications). Since we need both headings only if content. We could put Requirements for education/experience, and Qualifications for the list of attributes? But the posting already has Skills separate. Let's decide: - Requirements: Education and Experience (Bachelor’s degree, 1-2 years managing audience experience). Also maybe "Detail-Oriented: Detail-oriented team members..." but that's more attribute. - Qualifications: Could be the list of attributes (Detail-Oriented, Team Player, Multi-Tasking, Customer Focus, Analytical Skills, Communication, Adaptability, Problem-Solving, Empathy, Organizational Skills). However those are also under "What You’ll Bring". Might be better to treat "What You’ll Bring" as Qualifications. But we already have Skills separate. Let's examine the posting: After "Who you’ll work with?" there is "Skills Core Skills & Competencies:" then bullet list of Core Skills & Competencies, then Competencies, then Attributes. Then after that: "What You’ll Bring Education: Bachelor’s degree in a relevant field. Experience: 1-2 years managing audience experience or an equivalent role in a B2B customer-facing capacity. Detail-Oriented: Detail-oriented team members with an eye towards execution and efficiency. Team Player: Strong team player with excellent collaboration skills. Multi-Tasking: Strong multi-tasker with excellent prioritization skills. Customer Focus: Focused on high-quality customer service and deliverables. Analytical Skills: Proficient in data analysis and reporting. Communication: Excellent verbal and written communication skills. Adaptability: Can handle diverse audience needs and challenges. Problem-Solving: Effective at addressing complex audience experience issues. Empathy: Understands audience perspectives and needs. Organizational Skills: Manages multiple accounts efficiently. Preferred, But Not Required Experience in Microsoft Office, Asana" Thus "What You’ll Bring" includes both education/experience and a list of competencies/attributes. The earlier Skills section also includes similar items. There's overlap. We need to preserve all substantive info, not invent or summarize away detail. We must not duplicate? It's okay to repeat if it's in the posting. But we should try to avoid redundancy but not lose info. We could structure: - About the role: overview paragraph (including location and work arrangement? maybe schedule separate). We'll include location and work arrangement in About the role or Schedule? Since schedule section only if posting states schedule. It does: "Work Arrangement: This is an onsite role requiring five days per week in the office." That's schedule info. So we should create a Schedule section with that sentence. - Responsibilities: extract the four responsibility headings with subpoints. - Requirements: Education and Experience (maybe also "Preferred, But Not Required Experience in Microsoft Office, Asana" could be under Requirements or Qualifications). We'll put under Requirements. - Qualifications: The list of attributes/skills from "What You’ll Bring" after education/experience? But we already have Skills section. Actually the posting has a separate "Skills" section before "What You’ll Bring". So we should have Skills section for the Core Skills & Competencies, Competencies, Attributes. Then Qualifications could be education/experience? Hmm. Better to follow the headings given in instructions: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Thus we need to map content to these headings. - About the role: overview of role (the paragraph about responsibilities? Actually that's more responsibilities). But we can put the general description: "The Community Experience Specialist is responsible for executing all assigned tasks related to audience recruitment, rewards and incentives, member engagement and audience operations/administration. Projects will be deployed by Audience Experience Strategists or Managers. Community Experience Specialists may have a small book of business as determined by the Audience Experience Manager." plus maybe location? But location maybe not part of About the role. We'll keep location maybe in About the role as extra. - Responsibilities: the Key Responsibilities section with subpoints. - Requirements: Education and Experience (Bachelor’s degree, 1-2 years). Also maybe "Preferred, But Not Required Experience in Microsoft Office, Asana" could be under Requirements as optional. - Qualifications: The list of attributes (Detail-Oriented, Team Player, Multi-Tasking, Customer Focus, Analytical Skills, Communication, Adaptability, Problem-Solving, Empathy, Organizational Skills). Also maybe "Who you’ll work with?" not needed. - Skills: The Core Skills & Competencies, Competencies, Attributes from the Skills section. But that duplicates Qualifications. However we must preserve all substantive info; duplication is okay but we should not invent. We'll include both sections as they appear. - Benefits: The Benefits & Perks paragraph with bullet list. - Pay: Compensation Overview paragraph with salary range, bonus, equity. - Schedule: Work Arrangement sentence. We must not include sections with filler like "commensurate with experience". We have actual specifics. Now we need to output HTML fragment with

    headings and
    • for lists,

      for prose. We need to ensure we don't include any markdown fences. Let's craft. First, About the role:

      The Community Experience Specialist is responsible for executing all assigned tasks related to audience recruitment, rewards and incentives, member engagement and audience operations/administration. Projects will be deployed by Audience Experience Strategists or Managers. Community Experience Specialists may have a small book of business as determined by the Audience Experience Manager. Located in Los Angeles, CA.

      But location maybe separate; but okay. Now Responsibilities: We need to break into list items. The responsibilities have headings: Audience Operations & Engagement, Project Support & Execution, Customer Interaction & Account Support, Quality Assurance & Administration. Under each there are sentences. We'll create
      • for each responsibility heading, and inside each li we can have

        or just text. Probably each li can contain the description. Let's extract: Audience Operations & Engagement: - Support audience recruitment, onboarding, and ongoing engagement activities. - Execute scalable tasks related to audience recruitment, rewards, incentives, engagement and member satisfaction using the Fuel Cycle platform. - Monitor community activity and flag engagement opportunities or risks. Project Support & Execution: - Execute audience-related tasks and deliverables assigned by Audience Experience Strategists or Managers. - Coordinate across internal teams to ensure projects meet timelines and quality standards. - Provide support for campaigns, surveys, and events within audience communities. Customer Interaction & Account Support: - Own the audience experience for a designated vertical’s set of customer accounts i.e. book of business (as assigned). - Manages the bulk of customer management task execution on the Fuel Cycle technology - Communicate project updates, timelines, and best practices to clients clearly and professionally. - Collaborate with Strategists to provide recommendations on audience engagement and satisfaction. Quality Assurance & Administration: - Review and test deliverables to ensure high-quality outputs. - Maintain accurate records and documentation of audience activities and client communication. - Demonstrate Fuel Cycle Platform knowledge and account specific functions. Note there is a typo "Fuel Cyle" but we keep as is? We should preserve original text; but we can correct? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Changing typo could be considered altering. Safer to keep as is: "Fuel Cyle". We'll keep exactly. Now Requirements:

        Education: Bachelor’s degree in a relevant field.

        Experience: 1-2 years managing audience experience or an equivalent role in a B2B customer-facing capacity.

        Preferred, but not required: Experience in Microsoft Office, Asana.

        We could also put in a list. Now Qualifications: We need to list the attributes from "What You’ll Bring" after education/experience: Detail-Oriented, Team Player, Multi-Tasking, Customer Focus, Analytical Skills, Communication, Adaptability, Problem-Solving, Empathy, Organizational Skills. Each with description. We'll make
        • each. Descriptions: - Detail-Oriented: Detail-oriented team members with an eye towards execution and efficiency. - Team Player: Strong team player with excellent collaboration skills. - Multi-Tasking: Strong multi-tasker with excellent prioritization skills. - Customer Focus: Focused on high-quality customer service and deliverables. - Analytical Skills: Proficient in data analysis and reporting. - Communication: Excellent verbal and written communication skills. - Adaptability: Can handle diverse audience needs and challenges. - Problem-Solving: Effective at addressing complex audience experience issues. - Empathy: Understands audience perspectives and needs. - Organizational Skills: Manages multiple accounts efficiently. Now Skills: We need to include Core Skills & Competencies, Competencies, Attributes from the Skills section. Let's extract: Core Skills & Competencies: - Project Coordination – Ability to manage timelines, track tasks, and follow through on assigned responsibilities with excellent prioritization skills. - Written & Verbal Communication – Clear, professional, and customer-friendly communication with clients and internal teams. - Technology Proficiency – Comfortable working with SaaS platforms, spreadsheets, CRMs, or community management tools. - Analytical Skills: Proficient in data analysis and reporting. Competencies: - Process Execution – Follows structured workflows with consistency and accuracy. - Quality Assurance – Focused on high quality deliverables; reviews work carefully and identifies inconsistencies or errors before deliverables go out. - Client Service Orientation – Anticipates customer needs and

Similar jobs

Community Specialist

IDM CompaniesPhoenix, AZ· 1 mo ago
OTHRapply on idmcompanies.wd1.myworkdayjobs.com