Senior Trainer

We need to output HTML fragment with sections: About the role? Actually we have Position Summary, Key Responsibilities, Qualifications (Preferred Experience, Federal Acquisition Domain Knowledge, Core Skills And Abilities, Education), Remote Work, Clearance, Why Join Unison (maybe Benefits?), but we must only include sections when posting has real specific content. We must not include boilerplate like EEO, privacy policy, state laws, etc. Also we must not repeat job title as heading. Use

for section headings. Use

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

  for prose. We need to preserve all substantive information, but remove boilerplate. Let's parse content. Sections present: - About Unison (company description) – maybe we can include as "About the company" but not required? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings if appropriate? Probably we should stick to those headings when applicable. The posting includes "Position Summary", "Key Responsibilities", "Qualifications" (with sub-sections Preferred Experience, Federal Acquisition Domain Knowledge, Core Skills And Abilities, Education), "Remote Work", "Clearance", "Why Join Unison". Also "About Unison" at top. We need to decide which sections to include: About the role (maybe Position Summary). Responsibilities (Key Responsibilities). Requirements/Qualifications (Qualifications). Skills (Core Skills And Abilities). Benefits? Not explicit benefits besides maybe "Why Join Unison" which is culture; not benefits like health etc. Pay and Schedule not provided. So we should not include Pay or Schedule sections. We should include About Unison? Could be "About the company" but not in list; maybe we can include as a

  without heading? 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 says use those for section headings. Probably we should map content to those headings. So: - About the role: Position Summary (maybe also About Unison? but that's about company). We'll put Position Summary under About the role. - Responsibilities: Key Responsibilities. - Requirements: Qualifications (maybe combine Preferred Experience, Federal Acquisition Domain Knowledge, Core Skills And Abilities, Education). Could split into Requirements and Skills? But we have both Requirements and Skills headings available. Could put Requirements for experience/qualifications, Skills for core skills. However Qualifications includes both experience and skills. Might be better to have Requirements (Preferred Experience, Federal Acquisition Domain Knowledge, Education) and Skills (Core Skills And Abilities). Let's do that. - Benefits: Not present; skip. - Pay: skip. - Schedule: Remote Work mentions On-site working requirements vary. In-Person Interview required. That's schedule-ish but not explicit schedule. Might be considered Schedule? The instruction: only include if posting actually states them. It does mention Remote Work and In-Person Interview. That's about work location and interview requirement, not schedule. Probably we should not create Schedule section. We could include a section "Remote Work" but not in allowed headings. Might be better to incorporate into a

  under About the role or Requirements? But we need to preserve all substantive information. The remote work statement: "On-site working requirements vary. In-Person Interview Our hiring process requires an in-person meeting, typically the final interview. Travel and accommodations will be provided." That's substantive. We could put it under a heading like "Work Arrangements" but not in list. However we could embed as a

  after Qualifications without a heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Probably they expect us to use only those headings. So we need to fit remote work info into one of those sections. Maybe under Requirements? Not ideal. Could be under About the role? Could add a sentence. Alternatively, we could create a section "Schedule" and put remote work info there, even though not exactly schedule. But the instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state remote work and in-person interview, which could be considered schedule/work arrangement. Might be acceptable to put under Schedule. But they'd likely expect Schedule to contain info about work hours, shift, etc. Not present. Safer to omit schedule section and embed remote work info in a

  under About the role or Qualifications? Let's see: The remote work statement is about working requirements and interview process. Could be considered part of "About the role" (role expectations). We'll add a paragraph after Position Summary. Now, we need to remove boilerplate: EEO, privacy policy, state laws, etc. Also remove duplicated lines. Also remove "About Unison" maybe we can keep as part of About the role? But we need to preserve all substantive information; About Unison is company description, maybe not essential to role but still substantive. Could we include as a

  under About the role before Position Summary? That would preserve it. The heading About the role could contain both company description and position summary. That seems okay. Now, let's extract content. About Unison paragraph: "Unison’s products power the business of government to work smoother and smarter, making critical federal processes and acquisitions simpler and more effective. Trusted by over 200,000 federal employees and government contractors, our AI-infused software and deep domain expertise help contract shops, cost engineers, 1102s, program managers, and budgeting professionals cut through friction, keep compliance airtight, and sharpen decisions. Our federal focus brings efficiency, transparency, and clarity to complex data, regulations, and workflows, empowering agencies and executives to spend more minutes on mission and achieve strategic objectives. Unison is how federal business gets done. Unison is proud to be recognized as a 2026 Quantum Certified Workplace™ in Washington D.C., reflecting our continued focus on building a workplace where people feel supported and teams thrive." Position Summary: "Unison Software is seeking a Trainer to deliver training that drives user adoption and effective use of Unison's acquisition, grants management, and contract lifecycle solutions across federal civilian, defense, and intelligence community customers. Trainers at Unison are client-facing practitioners who translate complex systems and configured business processes into practical, role-based guidance. The role spans training delivery, hands-on material development, and post-deployment adoption support across both implementation and operations and maintenance (O&M) engagements, working alongside Consultants, Instructional Systems Designers, and Project Managers. Audience size, curriculum ownership, and depth of independent delivery scale with experience level and are defined in the specific job posting." Key Responsibilities list: bullet points. We need to convert each to

  . Qualifications: Preferred Experience bullet list (multiple). Federal Acquisition Domain Knowledge bullet list. Core Skills And Abilities bullet list. Education bullet. We need to decide headings: Requirements (maybe combine Preferred Experience and Federal Acquisition Domain Knowledge and Education). Skills (Core Skills And Abilities). Or we could have Requirements (Preferred Experience, Federal Acquisition Domain Knowledge, Education) and Skills (Core Skills And Abilities). Let's do that. Now, we need to ensure we don't include filler like "commensurate with experience" etc. The Preferred Experience includes "Professional experience in software training, implementation, or client-facing consulting, with depth of experience commensurate with the level of the position". That phrase "depth of experience commensurate with the level of the position" is filler? It's somewhat generic but still part of the posting. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It says never emit a heading followed by filler/placeholder text. It doesn't say we must remove that phrase from within a list; it's about headings followed by filler text. So we can keep the phrase inside a list item. Now, we need to remove duplicated lines: I don't see duplicates. Now, produce HTML. Structure:

  About the role

  About Unison paragraph.

  Position Summary paragraph.

  Remote work statement? We'll add after Position Summary: "On-site working requirements vary. In-Person Interview: Our hiring process requires an in-person meeting, typically the final interview. Travel and accommodations will be provided." We'll keep as a paragraph. Then

  Responsibilities

  list items. Then

  Requirements

  Maybe split into two sub-sections? But we can just list all items under Requirements. However we have distinct categories; we could keep them as separate

  but not allowed. We'll just list all items under Requirements as

  . Might be long but okay. Then

  Skills

  for Core Skills And Abilities. We should also include Education under Requirements? Yes. Now, ensure we don't include sections like Benefits, Pay, Schedule. Now, write HTML. Let's craft. About Unison paragraph: we need to keep as is. Position Summary paragraph. Remote work statement: "On-site working requirements vary. In-Person Interview: Our hiring process requires an in-person meeting, typically the final interview. Travel and accommodations will be provided." Now Responsibilities list items: - Partner with clients to understand business processes, user roles, and training objectives - Deliver training across multiple formats, including in-person instructor-led sessions, virtual sessions, and hands-on labs - Develop practical training materials such as user guides, job aids, quick reference cards, and scenario-based exercises - Translate system functionality and configured business processes into actionable, role-based guidance for end users - Support implementations and upgrades by aligning training content and schedule with configuration, testing, and deployment milestones - Facilitate sessions for diverse audiences, including federal employees, contractors, and internal teams, adapting delivery to varying levels of system and acquisition experience - Reinforce user adoption through follow-up support, office hours, refresher sessions, and ongoing client engagement - Build and maintain training environments, training data sets, and exercise scenarios used for instruction - Gather and act on participant feedback, assessment results, and adoption metrics to improve content and delivery - Collaborate with Consultants, Instructional Systems Designers, and Project Managers to ensure a consistent, high-quality client experience, and manage assigned tasks to timelines and quality standards Now Requirements list items (Preferred Experience, Federal Acquisition Domain Knowledge, Education). Let's list each as separate
  • . Preferred Experience items: - Professional experience in software training, implementation, or client-facing consulting, with depth of experience commensurate with the level of the position - Experience facilitating instructor-led and virtual training for audiences of varying size and seniority - Experience developing training materials such as user guides, job aids, and scenario-based exercises - Experience supporting enterprise software, ERP, or commercial off-the-shelf (COTS) implementations and upgrades - Exposure to software implementation lifecycle activities, including requirements, configuration, and testing - Familiarity with instructional design principles or eLearning development tools - Hands-on experience with Unison's PRISM acquisition platform, or with comparable federal acquisition, procurement, or grants management systems Federal Acquisition Domain Knowledge items (preferred): - Familiarity with one or more of the following is preferred: Federal acquisition and procurement lifecycle, from requirements and market research through award, administration, and closeout - Federal acquisition, contract writing, contract lifecycle management, or grants management systems, including commercial off-the-shelf (COTS) implementations - Training or supporting federal audiences such as 1102 contract specialists, program office staff, and financial management personnel - Organizational change management and user adoption in federal