Senior AI Platform Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Key info: - Ideal start timeline: July 2026 - Role status: Exempt - Compensation: target hiring range $175,000-$215,000 plus participation in Annual Bonus Program with eligibility for $12,000 bonus. Actual compensation will be commensurate with experience and skills. (We cannot include Pay section if it includes "commensurate with experience" placeholder? The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation range and bonus. So we can include Pay section with that info, but we must avoid filler like "commensurate with experience". We can include the range and bonus, but maybe we should not include the phrase "Actual compensation will be commensurate with experience and skills." That's filler? It's somewhat generic but still part of posting. The rule says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not include that sentence. We can include the range and bonus. - Campminder s Flexible Working Location: Our employees have the option to work 100% remotely within the United States in select states where Campminder has established entities or their choice of days at home and at our office in Boulder, Colorado. We host a variety of all-company hybrid meetings and social events. We require anybody working remotely to have a very reliable, high-speed internet connection. We know the best people can choose to work anywhere. - Then a list of reasons why 100+ choose Campminder: bullet points? It's a paragraph with sentences. We can treat as a list? Might be better as

• for each reason. Let's extract: - With 20+ years experience of serving the industry through its digital transformation, we’re stable, profitable, and have developed a loyal customer base (that continues to grow). - We build software for summer camps, an industry that enables meaningful experiences for kids. - We work on interesting, ambitious projects that create real value for our clients. - We know our team members feel their work has an impact on the organizations purpose. - At the same time, we are genuinely committed to work/life balance. Our team members feel they have the flexibility to take time off when needed and feel supported in making use of flexible working arrangements. - We invest in emerging technology and cutting-edge leadership and are proud to take an "AI-Enabled" approach in our solutions. - We’ve been listed on Outside Magazines 50 Best Places to Work for 8 consecutive years for our values-led culture and employee experience. - This roles mission & overview: paragraph describing Senior AI Engineer role. - Candidates should be solid in at least two of the following three areas: AI expertise, AI enablement of technical and non-technical teammates, and building scalable software with a genuine eagerness to grow in the third. This is a high-impact, high-autonomy role for someone who thrives on solving hard technical problems that unlock a whole new way of working at Campminder, while being in close collaboration with people across the entire company. - As a Senior AI Engineer on our AI Platform team, you will: list of duties (bullet points). We'll put under Responsibilities. - We Think a Successful Candidate Will Bring: list of qualifications/skills. - Our Interview Process: list of steps. - A few of the benefits we are proud to offer: list of benefits. - We Encourage People Of All Backgrounds To Apply: EEO boilerplate, should be removed. - We encourage applications from parents... also maybe part of benefits? It's more EEO/encouragement; we should remove as boilerplate. - Originally posted on Himalayas: metadata, drop. We need sections: About the role (mission & overview), Responsibilities (the "As a Senior AI Engineer... you will:" list), Requirements/Qualifications/Skills (the "We Think a Successful Candidate Will Bring" list), Benefits (the benefits list), Pay (compensation range + bonus), Schedule? Not mentioned besides flexible working location; but schedule not explicitly given. Could include "Flexible Working Location" maybe under a section like "Work Arrangement" but not in allowed headings. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put flexible location under About the role or maybe under Benefits? But Benefits is for benefits like medical etc. Could create a section "About the role" that includes mission, flexible work location, start timeline, role status. Or we could create a separate section "Schedule"? Not really schedule. The rule: only include sections when posting has real specific content for it. So we can include About the role, Responsibilities, Requirements (or Qualifications/Skills), Benefits, Pay. Possibly also Schedule if we have info like flexible working location? But schedule is about hours; not present. So omit Schedule. We need to decide whether to have separate Requirements, Qualifications, Skills sections. The posting has a list under "We Think a Successful Candidate Will Bring". That includes experience, skills, etc. Could split into Requirements and Skills? But we should prefer few substantive sections over many thin ones. So we could combine into one section, maybe "Requirements". Or "Qualifications". Choose one heading. Let's use "Requirements". Or "Qualifications". The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can pick any. I'll use "Requirements" to encompass the candidate qualifications. Thus sections: -

  About the role

  : includes mission & overview paragraph, ideal start timeline, role status, flexible working location description. -

  Responsibilities

  : list of duties from "As a Senior AI Engineer on our AI Platform team, you will:" bullet points. -

  Requirements

  : list from "We Think a Successful Candidate Will Bring". -

  Benefits

  : list from "A few of the benefits we are proud to offer:". -

  Pay

  : compensation range and bonus. We must not include filler like "commensurate with experience". So we will include only the range and bonus. We need to preserve all substantive info; do not invent or summarize away detail. So we need to keep all bullet points exactly as given (maybe slight rewording? Must preserve info, not necessarily exact wording but cannot lose detail. We'll keep the substance. We need to remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Our Interview Process" maybe? That's not a standard heading but could be considered part of Requirements? It's about interview process, not a job requirement. Should we include? The instruction: remove application instructions. Interview process is part of hiring process, not a job requirement. Likely should be removed as it's not about the role. So we omit Interview Process. Also remove "We Encourage People Of All Backgrounds To Apply" etc. Now craft HTML. We'll need
  • for lists. For About the role: we have multiple paragraphs: mission & overview, ideal start timeline, role status, flexible working location. We'll combine into

    elements. Let's extract mission & overview paragraph: "This roles mission & overview: We are looking for a Senior AI Engineer to join our AI Platform team, which owns AI enablement internally across Campminder , and externally to our customers. As a senior engineer on the team, you will be partnering directly with our executive leadership team to identify the greatest needs for AI enablement and AI tooling across all of Campminder , and then working with teams across the company to co-build AI solutions that improve efficiency and empowerment for those teams. You will also be partnering with our product team to build AI solutions that will empower external customers and internal engineers to use agentic coding tools to customize Campminder products. This will be a highly visible role, focused on partnering with stakeholders across the business to bring Campminder at the leading edge of AI enablement and AI platforms. Candidates should be solid in at least two of the following three areas: AI expertise, AI enablement of technical and non-technical teammates, and building scalable software with a genuine eagerness to grow in the third. This is a high-impact, high-autonomy role for someone who thrives on solving hard technical problems that unlock a whole new way of working at Campminder , while being in close collaboration with people across the entire company." Note: This paragraph also includes the "Candidates should be solid..." which is actually a requirement; but it's inside mission overview. Might be better to keep it there? But we also have a separate Requirements list later. To avoid duplication, we could keep the mission overview without that sentence? However the instruction: preserve ALL substantive information; do not invent or summarize away detail. If we remove that sentence, we lose info about candidate solid in at least two areas. But that info is also captured in Requirements list later (the "We Think a Successful Candidate Will Bring" list). However the mission overview includes that sentence as part of overview; we could keep it there and also have Requirements list; duplication is okay? The instruction says remove duplicated lines. So we should avoid duplicating the same content. The sentence about candidates solid in at least two areas appears also in the Requirements list? Let's check the Requirements list: It includes "Hands-on experience building AI-powered tools used by internal teams of varying skill levels and technical backgrounds", etc. Not exactly that sentence. So the "Candidates should be solid in at least two of the following three areas: AI expertise, AI enablement of technical and non-technical teammates, and building scalable software with a genuine eagerness to grow in the third." is not repeated later. So we should keep it somewhere. It fits under About the role or Requirements. Since it's about candidate qualifications, maybe better under Requirements. But the mission overview also includes it; we could keep it in About the role and not duplicate elsewhere. However the Requirements list later includes many specific items; we could keep the overview without that sentence and put that sentence in Requirements as a summary. But we must preserve all info; we can keep it in Requirements as a bullet? It's not a bullet but a statement. Could be a

    inside Requirements. That's fine. Thus we can split: About the role includes mission & overview without the candidate solid sentence? Let's see: The mission overview paragraph before that sentence: "We are looking for a Senior AI Engineer to join our AI Platform team, which owns AI enablement internally across Campminder , and externally to our customers. As a senior engineer on the team, you will be partnering directly with our executive leadership team to identify the greatest needs for AI enablement and AI tooling across all of Campminder , and then working with teams across the company to co-build AI solutions that improve efficiency and empowerment for those teams. You will also be partnering with our product team to build AI solutions that will empower external customers and internal engineers to use agentic coding tools to customize Campminder products. This will be a highly visible role, focused on partnering with stakeholders across the business to bring Campminder at the leading edge of AI enablement and AI platforms." Then after that, the candidate solid sentence. Then the next sentence: "This is a high-impact, high-autonomy role for someone who thrives on solving hard technical problems that unlock a whole new way of working at Campminder , while being in close collaboration with people across the entire company." That could stay in About the role. Thus we can keep About the role with those two paragraphs (mission overview and high-