Analyst, IT - Infrastructure Support

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Content: Intro paragraph: "Hungry for a career...". That's marketing fluff, but we need to preserve substantive info? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The intro includes description of company, culture, etc. Might be considered substantive? However later there is a "Why You’ll Love Working At Aspire Bakeries" section with bullet points (Culture, Health & Wellness, Work-Life Balance, Financial Security, Growth & Development, Flexibility & Support, Recognition & Rewards). That's benefits. So we can capture benefits there. Then "About The Role" heading (they used "About The Role") - we need to map to

  About the role (lowercase? The rule says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should output exactly "About the role" as heading. Then responsibilities: "Core Accountabilities (What You’ll Be Doing)" list bullet points. That's responsibilities. Then "Minimum Qualifications (What You Bring to the Table) (Required to be Considered)" list bullet points. That's requirements/qualifications. Then "Preferred Qualifications (Extra Ingredients For Success)" list bullet points. Could be qualifications or skills. Might combine as "Qualifications" or "Preferred Qualifications". The rule says we can have sections like Qualifications, Skills. We could have "Minimum Qualifications" and "Preferred Qualifications" as sub-sections? But they said prefer few substantive sections over many thin ones. Could combine Minimum and Preferred into a single "Qualifications" section with two lists? But we need to preserve all detail. Could have

  Qualifications

  then two
  with headings? But we cannot add extra headings not allowed? We could embed

  describing Minimum and Preferred then lists. Simpler: have

  Minimum Qualifications

  and

  Preferred Qualifications

  . That's two sections, but still okay. Then benefits: The "Why You’ll Love Working At Aspire Bakeries" bullet points. That's benefits. So

  Benefits

  with list. Pay: There's "Compensation Salary Range: $71,000 - $80,000". Also later note about pay varying. So we have specific salary range. So we should include Pay section with that info. Not just "commensurate with experience". So we can include Pay. Schedule: There's mention: "This role requires you to be onsite at our Newark Bakery four days per week and at our Stockton Bakery one day per week. You will also provide remote support... This role will require up to 25% travel." That's schedule info (onsite days, travel). So we can include Schedule section. We should not include sections like Responsibilities if we already have Core Accountabilities; we could label that as Responsibilities. The rule says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map Core Accountabilities to Responsibilities. Minimum Qualifications to Requirements? Or Qualifications. Preferred Qualifications could be Skills? But better to keep Qualifications for both minimum and preferred? Might be confusing. Let's decide: - About the role: intro paragraph about role (the paragraph after About The Role). Actually after "About The Role" there is a paragraph describing the role: "We are seeking an Analyst, IT Infrastructure Support...". That's substantive. So we can put that in About the role. - Responsibilities: the Core Accountabilities list. - Requirements: Minimum Qualifications list. - Qualifications/Skills: Preferred Qualifications list (could be Skills). We'll label as Preferred Qualifications maybe but rule says we can use Skills. Let's use "Skills" heading for preferred qualifications. - Benefits: the Why You’ll Love Working At Aspire Bakeries list. - Pay: Salary range. - Schedule: onsite days and travel. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, equal opportunity, AI screening, etc. Also remove duplicated lines, navigation, cookie, legal, application instructions. The posting includes at end: "Aspire Bakeries LLC values the contribution..." and EEO statement, etc. Remove those. Also remove "We do not use artificial intelligence (AI) tools to screen, assess, or select applicants." Remove. Also remove "For union-represented postings, wage rates and ranges are governed by applicable collective bargaining agreements." Might be considered boilerplate? It's about pay but maybe substantive? It's a generic statement; could be considered boilerplate. Safer to remove. Also remove "Aspire Bakeries is proud to be an equal opportunity employer..." Remove. Also remove "The final determination of a successful candidate’s starting pay will vary based on a number of factors..." That's about pay but maybe substantive? It's generic; but we already have salary range. Could keep? It's not specific detail; it's generic. Might be considered filler. I'd remove. Also remove "We provide a competitive compensation package..." generic. Also remove "Additional pay may be determined for those candidates that exceed these specified qualifications and requirements." generic. We need to preserve all substantive information: salary range, benefits list, responsibilities list, minimum qualifications, preferred qualifications, schedule, about the role paragraph. Now craft HTML. Structure:

  About the role

  We are seeking an Analyst, IT Infrastructure Support to join our team at our Newark, CA Bakery. As an Analyst, IT Infrastructure Support, you will be accountable for delivering reliable onsite technology support that enables bakery production, warehousing, logistics, quality, and administrative operations. This role serves as the primary local IT resource, ensuring seamless technology services, maintaining critical infrastructure, and partnering with business teams to drive operational excellence. This role requires you to be onsite at our Newark Bakery four days per week and at our Stockton Bakery one day per week. You will also provide remote support to our Chaska, MN bakery and our corporate remote employees, allowing you to collaborate closely with teams across all three locations and stay connected to the day-to-day needs of the business. This role will require up to 25% travel.

  But note schedule info is also in this paragraph; we might move schedule to separate section. However the paragraph includes schedule details. If we move schedule to separate section, we might duplicate. Better to keep schedule details in Schedule section and not duplicate in About the role. So we should edit About the role paragraph to exclude schedule details (onsite days, travel). Let's extract schedule: "This role requires you to be onsite at our Newark Bakery four days per week and at our Stockton Bakery one day per week. You will also provide remote support to our Chaska, MN bakery and our corporate remote employees, allowing you to collaborate closely with teams across all three locations and stay connected to the day-to-day needs of the business. This role will require up to 25% travel." That's schedule. So About the role paragraph should be: "We are seeking an Analyst, IT Infrastructure Support to join our team at our Newark, CA Bakery. As an Analyst, IT Infrastructure Support, you will be accountable for delivering reliable onsite technology support that enables bakery production, warehousing, logistics, quality, and administrative operations. This role serves as the primary local IT resource, ensuring seamless technology services, maintaining critical infrastructure, and partnering with business teams to drive operational excellence." Now schedule section will contain those details. Now Responsibilities: list from Core Accountabilities. We need to output
  • for each. List: - Provide onsite IT support and serve as the primary technology resource for bakery, warehouse, and office operations. - Partner with cross-functional teams to align technology solutions with operational and business requirements. - Maintain end-user technology, mobile devices, local infrastructure, and workplace technology services. - Troubleshoot and resolve technical incidents, service requests, and infrastructure issues while meeting service expectations. - Administer user accounts, access permissions, and endpoint configurations across approved enterprise platforms. - Support technology deployments, upgrades, continuous improvement initiatives, and operational projects. - Promote technology security, compliance, documentation, and service reliability through established IT processes and standards. Now Requirements (Minimum Qualifications) list: - Bachelor’s degree in Information Technology, Computer Science, a related discipline, or an equivalent combination of education and experience. - Minimum of six (6) years of experience in technical support, infrastructure support, desktop support, client services, or related IT functions. - Working knowledge of Microsoft Windows operating systems, endpoint support, and Microsoft 365 technologies including Outlook, Teams, Entra ID, Intune, and Exchange Online. - Experience supporting desktops, laptops, printers, mobile devices, conferencing systems, and related peripherals. - Basic understanding of networking concepts including wireless networking, switching, TCP/IP, VPN connectivity, and infrastructure troubleshooting. - Strong troubleshooting, analytical, customer service, communication, and documentation skills with the ability to manage multiple priorities. - Ability to travel regularly (25% to 50% locally and occasionally out-of-state), work onsite, participate in on-call support, and lift or transport moderately heavy technology equipment. Note: travel ability appears also in schedule; but it's part of qualifications. We'll keep. Now Skills (Preferred Qualifications) list: - Experience supporting technology environments within manufacturing, bakery, distribution, warehousing, retail, or other operational settings. - Experience using IT service management platforms such as ServiceNow. - SAP user administration and support experience. - Experience supporting enterprise technology deployments, upgrades, and infrastructure projects. - Demonstrated ability to collaborate effectively across technical and non-technical business functions. Now Benefits list from Why You’ll Love Working At Aspire Bakeries: - Culture - Our culture thrives on collaboration, diversity, and a shared passion for excellence. We support team members, empower growth, and encourage everyone to bring their authentic selves to work. - Health & Wellness – Comprehensive medical, dental, and vision coverage, plus company-paid life insurance and additional voluntary options to fit your needs. - Work-Life Balance – Paid parental leave, generous paid time off, and holidays so you can recharge and spend time on what matters most. - Financial Security – A competitive 401(k) with immediate company match, plus short- and long-term disability coverage for peace of mind. - Growth & Development – Opportunities to build skills, grow your career, and develop expertise through Aspire Bakeries’ learning and development programs. - Flexibility & Support – HSA and FSA plans to help you manage everyday expenses. - Recognition & Rewards – Performance incentive plans that celebrate achievements across sales, bakery performance, and individual contributions. Note: each bullet includes a dash; we can keep as is. Now Pay section: Salary Range: $71,000 - $80,000. We could also include note that final determination varies etc but we decided to remove generic. So just salary range. Now Schedule section: Onsite: Newark Bakery 4 days/week, Stockton Bakery 1 day/week. Remote support to Chaska, MN bakery and corporate remote employees. Up to 25% travel. We'll put as

    or

    ? It's not a list but we can use

    . Now ensure we don't include any boilerplate. Now output HTML