Implementation Specialist

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. From posting: "Job Duties" then "About Us" then "Description" then "What You'll Do" (duties). Then "Requirements". Then later "Position Salary Range". Also "This role can be performed 100% virtually anywhere in the US while following our Remote Work Policy." That's schedule/location info. Also "Deadline to apply is at least 3 days after the posting date listed." That's metadata, we can drop. Also "Job Benefits Not specified" - we should not create Benefits section because not specified. So we omit Benefits. We need sections: About the role (maybe from About Us and Description). Responsibilities (What You'll Do). Requirements (Requirements). Qualifications? Might be same as Requirements? Could combine but we need separate only if content. Could put Qualifications as education/experience etc. But we have Requirements already includes education, experience, etc. Could split: Requirements (education/experience) and Qualifications (skills). However we have also Skills section maybe for skills like presentation, facilitation etc. Let's parse. Responsibilities: list of duties under "What You'll Do". We'll output

• each bullet. Requirements: bullet list under "Requirements". That includes many bullet-like sentences. We'll output as list. Qualifications: maybe we can include education/experience etc but we already used Requirements. Could treat Requirements as qualifications. But we need to follow instruction: use headings only when posting has real specific content. We can have About the role, Responsibilities, Requirements, Qualifications, Skills, Pay, Schedule. But we must avoid thin sections. Let's see content: About the role: we have About Us paragraph and Description paragraph. That's substantive. Responsibilities: we have list of duties. Requirements: we have list of requirements (education, experience, understanding, knowledge, abilities). That's substantive. Qualifications: maybe we can separate education/experience vs skills? But we already have skills list within requirements (presentation, facilitation, etc). Could create Skills section for those soft/technical skills. But we already have many in requirements. Might be redundant. Better to have Requirements cover education/experience and knowledge, and Skills cover abilities like presentation, facilitation, interpersonal, communication, time management, attention to detail, analytical, problem-solving, critical thinking, self-starter, technical aptitude, MS Office, discretion, enthusiasm, work ethic, integrity, collaboration, travel ability. That's many. Schedule: we have "This role can be performed 100% virtually anywhere in the US while following our Remote Work Policy." Also maybe shift info: "Shift First (Day)" from metadata. That's schedule info. So we can create Schedule section with that. Pay: we have salary range: "$60,000- $80,000 USD + bonus + benefits + perks + community gains." Also later "Compensation $60,000.00 - $80,000.00 / Annually". So we have pay info. So we create Pay section. Benefits: not specified, so omit. Now we need to ensure we don't repeat job title heading. Not include Job ID etc. We'll output HTML fragment with sections in order: About the role, Responsibilities, Requirements, Skills, Pay, Schedule. We need to use

  for each heading. Use

  for prose paragraphs. Use

  • for lists. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting. Let's extract About Us paragraph: "ImageTrend, LLC. is dedicated to connecting life's most important data in the healthcare and emergency response community. We deliver software solutions, data analytics and services for EMS, hospitals, community paramedicine (CP), critical care, fire, and preparedness to enable fully integrated patient-centric healthcare and public safety. Our commitment to innovation, its clients, and providing world-class implementation and support is unsurpassed. Based in Eagan, MN, ImageTrend combines business analysis, creative design and data driven architecture to offer scalable solutions and strategies for today and the future. Employment at ImageTrend is not just about doing a job; it's about being a part of a community. We are top-notch talent, passionate about making a difference through the work we do together!" Description paragraph: "Under the direction of an Implementation Lead or Manager, the Implementation Specialist I will deliver and coordinate implementation of systems and services. This position works directly with our community implementing ImageTrend products, working to improve and maintain the consistency, predictability and efficiency of the organization's project delivery." We can combine these into About the role section as prose. Now Responsibilities: list from "What You'll Do". Let's extract each bullet: - Assists clients through planning, development, training and execution of the ImageTrend products - Designs & maintains implementation schedules and ensures compliance to timeframe and requirements by collaborating with stakeholders for all implementation processes - Ensures all implementation requirements, objectives, obstacles, and delays are properly documented, including time worked in implementation ticket - Provides assistance in scoping projects to aid in developing proposals & contracts. - Maintains/contributes to the ongoing maintenance of departmental OneNote, internal demo sites and other internal products used - Establishes and maintains great relationships with clients as a trusted advisor, providing informed, reliable and professional advice about our solutions - Conducts onsite and virtual training with clients and presents or teaches at the Annual Connect Conference and other tradeshows, conferences or meetings as appropriate - Works collaboratively and effectively with other customer success teams or departments as needed to create alignment across all teams ensuring a positive client experience - Reviews and advises on updates to instructional and technical documentation to ensure clarity, accuracy, accessibility and ease of use to improve and maintain internal and external documentation, product requirements, release notes, screenshots, diagrams and screencast videos - Travel to orientation, industry or company events, or other onsite meetings as required - Perform additional duties or tasks as assigned We'll output each as
  • . Now Requirements: list from "Requirements". Let's extract each bullet (they are sentences separated by line breaks). We'll list: - Bachelor's Degree or the equivalent combination of education and relevant work experience - Experience working in implementation, project delivery and/or adult education, preferably including agile/scrum experience, PMP certification, and technology or industry experience in the healthcare or public safety industries - Understanding of state and national EMS and Fire reporting requirements - Understanding of basic concepts for adult education and effective content delivery - Knowledge of implementation or project management tools used for delivery of education and project roll-out - Knowledge of ImageTrend products & functions, or other similar industry related technologies highly preferred - Ability to define, scope, estimate work and track implementation tasks to facilitate successful project completion and an understanding of standardized data collection practices - Strong presentation, facilitation, interpersonal and communication skills, both verbal and written - Excellent time management and organizational skills, and strong appreciation of and accountability to meeting critical timelines - Strong attention to detail, analytical, problem-solving and critical thinking skills - Ability to be a proactive self-starter and work independently within a highly collaborative and team-oriented environment - Strong technical aptitude to learn new technologies or systems and knowledge of MS Office Suite or other similar tools - Ability to maintain discretion when handling proprietary and confidential information - Enthusiasm for learning and expanding knowledge or skills - Strong work ethic, integrity, honesty, collaboration and team orientation - Ability to travel up to 10% - This role can be performed 100% virtually anywhere in the US while following our Remote Work Policy. (Actually that's schedule, but appears in requirements section; we might move to Schedule.) We need to decide where to put the remote work statement. It appears after "Ability to travel up to 10%" then a line: "This role can be performed 100% virtually anywhere in the US while following our Remote Work Policy." That's schedule/location. We'll move to Schedule section. Also "Deadline to apply is at least 3 days after the posting date listed." drop. Now we have Requirements list (excluding remote). We'll output as
    • . Now Skills: we could extract soft skills from Requirements that are skill-based: presentation, facilitation, interpersonal, communication, time management, organizational, attention to detail, analytical, problem-solving, critical thinking, proactive self-starter, technical aptitude, MS Office, discretion, enthusiasm for learning, work ethic, integrity, honesty, collaboration, team orientation. But many of these are already in Requirements. To avoid duplication, maybe we should not create Skills section; instead keep Requirements as is. However the instruction says we can have Skills section if there is real specific content. We have skill details; but they'd duplicate. Better to keep them under Requirements and not create Skills. But we need to decide if we want to split. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid splitting into many thin sections. So we can combine education/experience, knowledge, abilities into Requirements. That's fine. Thus we will have sections: About the role, Responsibilities, Requirements, Pay, Schedule. Now Pay section: include salary range and bonus etc. Also mention "Compensation $60,000.00 - $80,000.00 / Annually". We'll combine. Pay prose: "The annual base salary range for this full-time role is $60,000- $80,000 USD + bonus + benefits + perks + community gains. Within the range, individual pay is determined by job-related skills, education or training and other relevant qualifications." Also we can mention the compensation line. Now Schedule section: include shift info: "Shift First (Day)" maybe from metadata. Also remote work statement: "This role can be performed 100% virtually anywhere in the US while following our Remote Work Policy." Also maybe "Place of Work On-site" from metadata conflicts with remote? Actually Place of Work On-site vs remote. The posting says "Place of Work On-site" but also says role can be performed 100% virtually anywhere in the US while following Remote Work Policy. That's contradictory but we must preserve all info. We'll include both. Also "Public Transportation Accessible Yes". That's schedule/location detail. Also "Veterans Encouraged to Apply No" is EEO, drop. "Physical Required Yes", "Drug Test Required Yes" maybe we could include as part of Schedule? They are not schedule but maybe we could put under Requirements? They are not really requirements but could be considered job requirements. However they are metadata like physical required, drug test. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Physical required and drug test are not EEO but could be considered job requirements. Might keep them under Requirements? But they are not about skills. However we can include them in Requirements as additional requirements. But they are more like conditions. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep them. Where to place? Could add to Requirements as bullet points: "Physical required: Yes", "Drug test required: Yes". But they are not phrased as requirements; they are metadata. Could also create a separate section like "Job Details" but we only have allowed headings list. Could put under Requirements as additional bullets. But we also have "Minimum Education Required Bachelor Degree", "Minimum Experience Required None", "Shift First (Day)", "Number of Openings 1", "Public Transportation Accessible Yes", "Veterans Encouraged to Apply No", "Physical Required Yes", "Drug Test Required Yes", "Compensation ...", "Postal Code 55121", "Job Type Full Time", "Place of Work On-site", "Requisition ID". Many of these are metadata; we should drop Job ID, requisition numbers,