Automation Specialist

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, job title: Automation Specialist. Not to repeat as heading. We need sections: - About the role: likely the introductory paragraph(s) describing role. The posting starts with "Pax8 | USA | Open to Hybrid/Remote/On Site in Denver, CO Join Pax8 in USA as an Automation Specialist and help shape the future of AI-powered operations, building scalable automations that transform how work gets done across our global marketplace. Build the Future of Work. This is not a traditional automation role..." So we can put that in About the role. - Responsibilities: The "What You'll Be Doing" bullet list. - Requirements: maybe "Skills And Experience We're Looking For" includes required functional domain expertise, automation and systems thinking, practical AI experience, communication and change enablement. Could be considered Requirements. - Qualifications: maybe not separate; but we could treat "Skills And Experience We're Looking For" as Qualifications. However we need to decide which sections to include. The instruction: Prefer a few substantive sections over many thin ones. So we could combine some. We have Benefits and Pay: there is a Salary & Benefits section with base salary up to $155,000 and benefits list. So we can have Pay and Benefits sections. Schedule: The posting mentions "Work Your Best Way: This opportunity is open to remote, hybrid, or onsite working arrangements across the United States, aligned with Denver working hours." That's schedule info. So we can include Schedule. We also have "About Pax8" maybe could be About the role? But we already have About the role. Could also have a separate "About Pax8" but not required. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Pre-Employment Checks", "Equal Opportunities", "Closing date", "Privacy notice", repeated trust hiring text, "Bring Your Perspective", "Perks" duplicate benefits, "Please take a moment to review our Proprietary Rights and Non-Competition Agreement". Also remove "Why Pax8?" maybe part of About the role? It's descriptive but could be included. We need to preserve all substantive information. Let's extract substantive content: Intro: "Pax8 | USA | Open to Hybrid/Remote/On Site in Denver, CO Join Pax8 in USA as an Automation Specialist and help shape the future of AI-powered operations, building scalable automations that transform how work gets done across our global marketplace. Build the Future of Work. This is not a traditional automation role. At Pax8, we're creating an AI-enabled organisation where automation becomes a natural part of every workflow rather than isolated experiments. As an Automation Specialist, you'll have the opportunity to identify opportunities others miss, design intelligent solutions, and directly influence how work evolves across our business. You'll work at the intersection of business operations, automation, and AI, empowering teams to eliminate repetitive work, improve quality, and create capacity for higher-value contributions. Most importantly, you'll grow alongside emerging technologies, helping define what great looks like as AI becomes embedded into the fabric of our organisation." Why Pax8? "Pax8 is on a mission to build the world's leading managed intelligence marketplace. As we continue our AI transformation journey, we're investing in automation capabilities that empower our people, partners, and customers to achieve more. Working here means joining a passionate, ambitious, and collaborative team that embraces innovation, continuous learning, and experimentation. If you're excited by solving business problems with technology and want to help shape the future of operational excellence, you'll thrive here." That could be part of About the role. Responsibilities (What You'll Be Doing): list bullet points with emojis. Need to convert to

• . Remove emojis? Probably keep text but can drop emojis. Keep the description. List: - Identify and redesign business processes that create the greatest opportunity for automation and efficiency - Design, build, deploy, and enhance intelligent workflows using modern low-code and no-code automation platforms - Apply AI capabilities to streamline repetitive activities such as data processing, routing, summarisation, knowledge retrieval, and standardised responses - Connect systems and platforms to enable seamless information flow across the business - Measure and communicate the value delivered through automation, tracking efficiency gains, quality improvements, and adoption - Facilitate process-mapping workshops and collaborate with stakeholders to understand challenges and design practical solutions - Create repeatable frameworks, playbooks, standards, and templates that accelerate automation across multiple business functions - Enable adoption through training, coaching, demonstrations, documentation, and ongoing support - Establish sustainable ownership models and governance practices that ensure automations remain effective over time - Partner closely with Workflow Engineering and Automation Specialists across Pax8 to share best practices and scale successful approaches globally Impact You'll Make: could be part of Responsibilities or separate? Might be considered Responsibilities but we can include as part of Responsibilities or maybe a separate "Impact". But we only have set headings; we could include under Responsibilities. Skills And Experience We're Looking For: break into subparts but we can just list as
  • each bullet. Functional Domain Expertise (Required): - Significant experience in function with deep understanding of the workflows and data and systems within that function. - Proven experience improving processes that actually stick — not just documented future-state diagrams. - Credibility with functional stakeholders and comfort navigating cross-functional work. Automation And Systems Thinking (Required): - Demonstrated systems thinking: ability to understand end-to-end processes, interdependencies, and how changes impact roles, capacity, and outcomes. - Experience redesigning workflows and operating rhythms to align with new tools — not just implementing tools. - Understanding basic systems communication standards such as Identity protocols, MCP, RESTful systems integration. - Hands-on experience building workflows using platforms such as Microsoft Power Automate, n8n, ServiceNow, Workday configuration, Zapier, or Airtable automations. - Comfort with logic, routing rules, conditional workflows, and integrations. - Strong self-directed learning mindset for new tools and platforms. - Ability to troubleshoot system issues in domain/function and know when to escalate to Workflow Engineering. Practical AI Experience (Required): - Regular use of leading AI tools (e.g., ChatGPT Codex, Claude Code) in real work. - Understanding of workflow solutioning that requires deterministic (programatic) ways of problem solving vs non-deterministic AI Agent based solutions ie. Where AI adds value in an automation/workflow — and where it doesn’t. - Bonus: experience building chatbots, AI-assisted routing, or automated knowledge retrieval. Communication And Change Enablement (Required): - Ability to explain automation concepts clearly to non-technical audiences. - Experience training users and creating documentation people actually follow. - Strong adoption mindset: building is only half the job. - Confidence holding teams accountable while remaining empathetic to change. - An entrepreneurial, start-up mindset with the curiosity, resilience, and initiative to turn ideas into impactful solutions while thriving in a fast-moving, evolving environment. We could treat this as Requirements or Qualifications. Since we have both Requirements and Qualifications headings possible, we could put this under Requirements (or Qualifications). The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have both Requirements and Qualifications. We need to decide what goes where. Typically Requirements are mandatory, Qualifications are desired. But we can split: Requirements could be the "Required" bullet points; Qualifications could be the "Bonus" or maybe "Entrepreneurial mindset". However we have limited time. Perhaps we put all under Requirements and skip Qualifications (if no specific content). But we need to include a section only when posting has real specific content for it. If we don't have distinct qualifications beyond requirements, we could omit Qualifications. Skills: Could be separate from Requirements? The posting already has "Skills And Experience We're Looking For". That could be Skills section. So we could put that under Skills. Then Requirements could be something else like "Must have right to work in US". There's a line: "To fulfil this role, you must hold valid right to work in the United States." That's a requirement. Also maybe "Open to Hybrid/Remote/On Site in Denver, CO". That's location/ schedule. Thus we can have: - About the role: intro + Why Pax8? maybe. - Responsibilities: What You'll Be Doing list. - Skills: Skills And Experience We're Looking For (the detailed bullet list). - Requirements: Must hold valid right to work in the United States. (maybe also location? but location is schedule.) - Benefits: list of benefits. - Pay: Base salary up to $155,000, depending on experience and location. - Schedule: Work Your Best Way: open to remote, hybrid, or onsite working arrangements across the United States, aligned with Denver working hours. Occasional travel to Denver and attendance at Pax8 Beyond or relevant industry events may be required. We also have "Impact You'll Make" maybe could be part of Responsibilities or separate but we don't have a heading for Impact; we could incorporate into Responsibilities. We must not include boilerplate like "Why Pax8?" maybe it's fine to keep as part of About the role. We must not repeat job title as heading. We must not include duplicated lines (like benefits repeated). We'll include benefits once. We must not include "Pre-Employment Checks", "Equal Opportunities", "Closing date", "Privacy notice", "Trust Starts With How We Hire" repeated, "Bring Your Perspective", "Perks" duplicate, "Proprietary Rights and Non-Competition Agreement". Now produce HTML fragment. Structure:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Skills

    • ... (maybe group subheadings? but we can just list each bullet as li; subheadings could be strong text inside li). We'll keep as li with maybe Functional Domain Expertise (Required): then the sentences. Better to keep readability.

      Requirements

      • Must hold valid right to work in the United States.

      Benefits

      • 401(k) with Company Match
      • Medical, Dental & Vision Coverage
      • Employee Assistance Program (EAP)
      • Employer-Paid Life, AD&D, Short-Term Disability & Long-Term Disability Insurance
      • Flexible Open PTO
      • Paid Sick Leave
      • Paid Parental Leave
      • RTD EcoPass (eligible Colorado-based employees)

      Pay

      Base salary: Up to $155,000, depending on experience and location.

      Schedule

      This opportunity is open to remote, hybrid, or onsite working arrangements across the United States, aligned with Denver working hours. Occasional travel to Denver and attendance at Pax8 Beyond or relevant industry events may be required.

      We need to ensure we didn't miss any substantive info: The "Impact You'll Make" paragraph: "The solutions you build will directly improve how Pax8 operates. You'll help reduce manual effort, increase process consistency, improve user experiences, and unlock capacity for teams to focus on strategic, high-value work. Success in this role will be visible and measurable. Your work will influence operational excellence at scale while helping establish automation and AI as core capabilities across the organisation." Could be added to Responsibilities or About the role. Let's add a paragraph under Responsibilities after the list, or maybe under About the role. I'd add a

      after the list under