IT Analyst

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate. The posting includes: - Intro about company (Hunter Douglas, Universal Screen) – could be "About the role"? Actually "About the role" is a heading for overview. The posting has "Position Overview" then description. So we can put that under

About the role

with paragraph(s) summarizing the overview. - Responsibilities: bullet list under "What you'll do". So

Responsibilities

with

• each bullet. - Requirements: there is "Other requirements:" bullet list. Also "Who you are" list. Those could be combined into Requirements and Qualifications. The instruction: Use headings for sections like Requirements, Qualifications, Skills. We need to decide what content goes where. Typically "Requirements" could be experience, etc. "Qualifications" could be education/experience. "Skills" could be specific skills. But we can just put all under Requirements if they are substantive. However we need to avoid empty sections. We can create sections for each that have content. Let's parse: Position Overview: "Support and optimize business systems and processes. This role bridges the gap between Operations and IT by working closely with internal teams to understand business needs, configure systems, troubleshoot issues, and ensure technology solutions effectively support day-to-day operations." That's prose. What you'll do bullet list: - Serve as the primary liaison between business users and IT for system-related needs - Provide day-to-day support for core business applications (ERP, CRM, or manufacturing systems) - Analyze business processes and recommend system improvements or efficiencies - Configure and maintain system settings, workflows, and user access. - Troubleshoot system issues and coordinate with technical teams or vendors when needed - Assist with system implementations, upgrades, and testing (UAT) - Develop and maintain documentation, including process flows and user guides. - Train end users on system functionality and best practices. - Support data integrity by monitoring, auditing, and correcting system data as needed. Other requirements bullet list: - Experience in manufacturing environments (especially indoor/outdoor products or custom fabrication) - Familiarity with reporting tools and basic data analysis (Excel, SQL, or BI tools) - Experience supporting system integrations or working with vendors - Train end users on system functionality and best practices (duplicate of earlier? Actually appears again) - Strong organizational and time-management skills. Who you are bullet list: - 5+ years of experience in a functional IT, systems analyst, or similar role - Strong understanding of business processes (operations, supply chain, manufacturing, or finance preferred) - Experience working with ERP systems (PIC experience is a plus) - Ability to translate business needs into system requirements - Strong problem-solving and analytical skills. - Excellent communication skills with both technical and non-technical stakeholders - Hands-on, self-starter mentality with a focus on execution. What's in it for you? includes: - Annual base salary range: $80,000.00 - $90,000.00 - Bonus target range: 10% - Generous benefits package including medical, dental, vision, life, disability - A company culture that prioritizes internal development and professional growth - Time off with pay - 401(k) plan with a degree of employer matching - Paid parental leave - Wellness programs and product discounts Also note: "Please note, all offers presented to candidates are carefully crafted..." boilerplate; we should drop that. Also EEO etc drop. Thus we have Pay (salary range, bonus), Benefits (list), maybe Schedule? No schedule info. So we should not create Schedule section. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly combine Requirements and Qualifications and Skills? But we have content for each. We could map: - About the role: Position Overview paragraph. - Responsibilities: What you'll do list. - Requirements: Other requirements list (manufacturing experience, reporting tools, system integrations, organizational skills). Also maybe "Train end users..." duplicate but we can keep. - Qualifications: Who you are list (5+ years experience, business processes, ERP, translate needs, problem-solving, communication, self-starter). - Skills: Could be derived from both but we might not have explicit skills list separate. Could combine some like "Strong organizational and time-management skills" etc. But we already used them. Perhaps we can put skills under Requirements or Qualifications. To avoid empty sections, we could omit Skills if no distinct content. But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications into one section called Requirements (or Qualifications). But headings list includes both; we can choose to include only those with content. So we could have About the role, Responsibilities, Requirements/Qualifications (maybe combine), Benefits, Pay. But we need to decide headings exactly as allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include any subset. Thus we will output:

  About the role

  ...

  Responsibilities

  ...

  Requirements

  ...
  (maybe combine other requirements + who you are? but that's qualifications.) Better: Requirements = other requirements (manufacturing experience, reporting tools, system integrations, organizational skills). Qualifications = who you are (5+ years, ERP, etc). Skills maybe not needed. Thus we have: Requirements: list of other requirements. Qualifications: list of who you are. Benefits: list of benefits. Pay: paragraph with salary and bonus. We should not include Schedule. Now ensure we preserve all substantive information. Need to include the duplicate "Train end users on system functionality and best practices" appears both in What you'll do and Other requirements. We should keep it; duplication is okay but we should not remove substantive info. However we might deduplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplicate lines are substantive? They are repeated; we could keep both but it's redundant. Probably better to keep as appears; but we could keep only one instance to avoid redundancy but that would be summarizing away detail (removing a duplicate). Safer to keep both? But that would be repeating same bullet twice under different sections, which might be odd but still preserves info. However the duplicate appears in "Other requirements" and also in "What you'll do". If we keep both, we are preserving the info. It's okay. But we might notice that "Train end users on system functionality and best practices." appears twice in the original: once under What you'll do, once under Other requirements. We'll keep both. Now format. We need to output only HTML fragment, no markdown fences. Let's craft. About the role paragraph: combine the two sentences: "Support and optimize business systems and processes. This role bridges the gap between Operations and IT by working closely with internal teams to understand business needs, configure systems, troubleshoot issues, and ensure technology solutions effectively support day-to-day operations." We'll put as

  Support and optimize business systems and processes. This role bridges the gap between Operations and IT by working closely with internal teams to understand business needs, configure systems, troubleshoot issues, and ensure technology solutions effectively support day-to-day operations.

  Responsibilities list: each bullet as
• . Requirements list (Other requirements): bullets: - Experience in manufacturing environments (especially indoor/outdoor products or custom fabrication) - Familiarity with reporting tools and basic data analysis (Excel, SQL, or BI tools) - Experience supporting system integrations or working with vendors - Train end users on system functionality and best practices - Strong organizational and time-management skills Qualifications list (Who you are): - 5+ years of experience in a functional IT, systems analyst, or similar role - Strong understanding of business processes (operations, supply chain, manufacturing, or finance preferred) - Experience working with ERP systems (PIC experience is a plus) - Ability to translate business needs into system requirements - Strong problem-solving and analytical skills. - Excellent communication skills with both technical and non-technical stakeholders - Hands-on, self-starter mentality with a focus on execution. Benefits list: bullets: - Generous benefits package including medical, dental, vision, life, disability - A company culture that prioritizes internal development and professional growth - Time off with pay - 401(k) plan with a degree of employer matching - Paid parental leave - Wellness programs and product discounts Pay: paragraph: "Annual base salary range: $80,000.00 - $90,000.00 Bonus target range: 10%". Could be two sentences. We should not include the note about offers, EEO, etc. Now output. Check for any other substantive content: The intro about Hunter Douglas and Universal Screen is company description; maybe could be part of About the role? But the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." The company description is not a heading; we could include it as part of About the role? But About the role is supposed to be role overview. The company description is more about the company; could be considered "About the role" context. However we already used About the role for position overview. We could add a preceding paragraph about company before the overview. That would preserve substantive info. The instruction: "Preserve ALL substantive information". So we should include that company description somewhere. Where? Could be a short

  before the About the role heading? But headings are for sections; we could include a

  before the first heading (the fragment can have plain paragraphs). That's allowed. So we can add a paragraph describing Hunter Douglas and Universal Screen. Thus output:

  Hunter Douglas is the world’s leading manufacturer of window coverings and a major manufacturer of architectural products. We are a brand that you know and trust. With more than 100 years of innovation, we’ve defined our industry with proprietary products that deliver revolutionary style and functionality and can be found in millions of homes and commercial buildings globally.As a member of the Hunter Douglas family of brands, Universal Screen manufactures the finest retractable shading solutions on the market. We use only the highest grade materials in the construction of each outdoor retractable shade. We firmly believe in providing our customers not only superior quality motorized shades, but also a seamless experience that surpasses their expectations.

  Then

  About the role

  with the overview paragraph. Then responsibilities, requirements, qualifications, benefits, pay. Make sure not to include any boilerplate like "We are searching for candidates that are driven, intelligent, creative, and entrepreneurial..." That's also substantive? It's a description of desired traits; could be considered part of "Who you are" but we already have that list. However that sentence is not captured in our lists. It's substantive: "We are searching for candidates that are driven, intelligent, creative, and entrepreneurial. By offering challenging and accelerated opportunities for growth, powered by a shared hunger for success, we create a space for your career to thrive. In return for your expertise, we are committed to providing competitive and robust total compensation and benefit packages to ensure you feel valued. Our dream is to become the fastest growing, most loved, window covering company in the world. What’s yours?" This is fluff but still substantive. Should we include? It's not a list; it's prose. Could be placed under About the role or maybe a separate section like "About the company". But we already have company description. This is more about the role and culture. Could incorporate into About the role paragraph after overview. To preserve all substantive info, we should include it. Let's add a paragraph after the overview