Associate Engineer

We need to output HTML fragment with sections: h3 for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, navigation, cookie, application instructions. Must not create sections with filler like "commensurate with experience". So we need to parse the posting. Let's extract content: Title: Site Support Engineer (Orlando) – but we don't repeat as heading. Intro paragraph: "Presidio, Where Teamwork and Innovation Shape the Future At Presidio, we're at the forefront of a global technology revolution, transforming industries through cutting-edge digital solutions and next-generation AI. We empower businesses - and their internal customers - to achieve more through innovation, automation, and intelligent insights." Then "The Role The Site Support Engineer (Orlando) is responsible for the day-to-day technical operations, setup, and maintenance of Presidio's AI Solutions lab environment at the Orlando site. This hands-on role ensures that lab infrastructure, hardware, and demonstration environments are operational, well-maintained, and ready to support customer engagements, internal training, and solution validation activities. The Site Support Engineer works closely with Solutions Engineering, Lab Management, Field Sales, and vendor partners to ensure the Orlando site delivers a high-quality, reliable lab experience. This role translates infrastructure requirements into working environments, troubleshoots issues quickly, and helps maintain the readiness of demonstration assets that showcase Presidio's AI capabilities to clients and internal stakeholders." That's about the role. So we can put under

About the role

a paragraph(s) containing that. Next: "Responsibilities Include Major Responsibilities:" then list bullet points. We'll create

Responsibilities

with

• each. List items: - Install, configure, and maintain lab hardware, servers, networking gear, and AI/ML demonstration systems at the Orlando site. - Set up and tear down demonstration environments in support of customer visits, partner sessions, and internal training events. - Monitor lab infrastructure health, identify issues proactively, and resolve incidents in a timely manner. - Coordinate with vendors and internal teams to manage hardware warranties, RMAs, and equipment refresh cycles. - Maintain accurate inventory of lab assets, cabling, and consumables; track equipment assignments and locations. - Support physical site operations including workspace setup, signage, security access, and safety compliance. - Document lab configurations, network topologies, and standard operating procedures for the Orlando site. - Collaborate with Lab Management and Solutions Engineering to plan capacity, growth, and new technology introductions. - Provide on-site technical support during customer demonstrations and executive briefings. - Escalate complex issues to senior engineering staff and follow through on resolution. Now "Required Skills And Professional Experience" then subheadings: Technology/Area of Specialization: list items. Then "Basic Knowledge, Skills, And Abilities": list items. Then "Required Skills": list items (3-5 years experience etc). Then "Competencies Required": list items. Then "Physical Requirements": paragraph. We need to decide which sections to map to headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content that could go under Requirements (maybe required skills/experience). Qualifications (education). Skills (technology familiarity). Benefits? Not mentioned. Pay? Not mentioned. Schedule? Not mentioned (except travel approx 10%). Travel could be schedule? Not exactly schedule. The instruction: only create Pay/Schedule/Benefits sections if posting actually states them. There's no explicit pay, benefits, schedule (work hours). Travel percentage maybe could be considered schedule? But schedule usually refers to work schedule (full-time, part-time, shift). Not present. So we should not create Pay, Schedule, Benefits sections. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills. Possibly also "Physical Requirements" could be under Requirements or separate? But we only have allowed headings list; we could put physical requirements under Requirements or maybe under a separate heading not allowed? 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 suggests those are typical. Safer to stick to those. Physical requirements could be part of Requirements. Competencies Required could be under Skills or Requirements. We'll decide. Let's map: - About the role: intro paragraphs. - Responsibilities: list. - Requirements: combine "Required Skills And Professional Experience" (including Technology/Area of Specialization, Basic Knowledge, Skills, And Abilities, Required Skills (experience/education), Competencies Required, Physical Requirements). Could be a big section with sublists. - Qualifications: maybe education requirement (Bachelor's degree...). Could be separate but we have Qualifications heading. We'll put education there. - Skills: maybe the technology familiarity list? But we already put tech under Requirements. Could separate: Skills heading for technology familiarity, while Requirements for experience and education. Let's think: The posting has "Technology/Area of Specialization:" list, then "Basic Knowledge, Skills, And Abilities:" list, then "Required Skills:" list (experience/education), then "Competencies Required:" list, then "Physical Requirements:" paragraph. We could allocate: - Skills: Technology/Area of Specialization + Basic Knowledge, Skills, And Abilities + Competencies Required (these are skills/competencies). - Requirements: Required Skills (experience/education) + Physical Requirements. - Qualifications: maybe not needed if we put education under Requirements. But we have education in Required Skills list: "Bachelor's degree in Information Technology, Computer Science, or related field — or equivalent hands-on experience." That's qualification. Could put under Qualifications. Thus:

  About the role

  ...intro...

  Responsibilities

  ...

  Skills

  combine technology familiarity, basic knowledge/skills/abilities, competencies. But we need to avoid duplication: The lists have overlapping items? Let's list them: Technology/Area of Specialization: - Familiarity with server, storage, and networking hardware commonly used in lab and demonstration environments. - Familiarity with virtualization platforms (VMware, Hyper-V) and container-based demonstration stacks. - Familiarity with AI/ML hardware ecosystems including GPU servers, inference appliances, and supporting infrastructure. - Familiarity with basic networking concepts (TCP/IP, VLANs, routing) and physical cabling standards. Basic Knowledge, Skills, And Abilities: - Strong hands-on technical aptitude with the ability to install, configure, and troubleshoot hardware and software systems. - Detail-oriented with disciplined approach to documentation, inventory tracking, and change management. - Effective communication skills; ability to coordinate with engineers, sales teams, and vendors. - Self-motivated with the ability to work independently at a remote site with minimal supervision. - Customer-service mindset with comfort supporting customer-facing demonstrations and executive visits. - Physical ability to lift and move hardware (up to 50 lbs) and work in data center / lab environments. Competencies Required: - Attention to Detail - Customer Focus - Initiative and Persistence - Collaboration and Teamwork - Adaptability - Technical Expertise Physical Requirements paragraph: "This role is based at the Orlando lab site and involves extended periods of standing, walking, and physical activity including lifting hardware up to 50 lbs. Travel is approximately 10%, primarily to other Presidio sites for training or cross-site collaboration. Regular participation in on-site customer demonstrations and team meetings is expected." We could put physical ability under Skills (since it's a skill/ability) but also physical requirements paragraph includes travel etc. Might be better to put physical requirements under Requirements or a separate section not allowed. Since we cannot create new heading, we could embed physical requirements paragraph under Requirements. Thus: Skills: combine Technology/Area of Specialization, Basic Knowledge, Skills, And Abilities, Competencies Required. Requirements: combine Required Skills (experience/education) and Physical Requirements paragraph. Qualifications: maybe we could put education under Qualifications, but we already have education in Required Skills. To avoid duplication, we could put education under Qualifications and experience under Requirements. Let's split: Required Skills list includes: - 3-5 years of experience in IT infrastructure, lab support, or systems administration roles. - Hands-on experience with server hardware, networking equipment, and operating system installation. - Experience supporting customer-facing demonstrations or technical events preferred. - Bachelor's degree in Information Technology, Computer Science, or related field — or equivalent hands-on experience. We could put experience items under Requirements, and degree under Qualifications. Thus:

  Requirements

  experience items (3-5 years, hands-on experience, experience supporting demos preferred)
  plus maybe physical requirements paragraph as

  .

  Qualifications

  Bachelor's degree in Information Technology, Computer Science, or related field — or equivalent hands-on experience.

  But we also have "Physical ability to lift and move hardware (up to 50 lbs) and work in data center / lab environments." That's under Basic Knowledge, Skills, And Abilities; we already included that in Skills list. However physical requirements paragraph also mentions lifting hardware up to 50 lbs, standing, walking, travel 10%. We could keep physical ability in Skills and also mention travel/standing in Requirements paragraph? Might duplicate. Better to keep physical ability under Skills (as it's a skill/ability) and put travel/standing paragraph under Requirements as a note about physical demands and travel. Thus Requirements section will have:
  • 3-5 years of experience in IT infrastructure, lab support, or systems administration roles.
  • Hands-on experience with server hardware, networking equipment, and operating system installation.
  • Experience supporting customer-facing demonstrations or technical events preferred.

  This role is based at the Orlando lab site and involves extended periods of standing, walking, and physical activity including lifting hardware up to 50 lbs. Travel is approximately 10%, primarily to other Presidio sites for training or cross-site collaboration. Regular participation in on-site customer demonstrations and team meetings is expected.

  Qualifications:

  Bachelor's degree in Information Technology, Computer Science, or related field — or equivalent hands-on experience.

  Skills: combine technology familiarity, basic knowledge/skills/abilities (excluding physical ability? but we included physical ability there; we could keep it), and competencies. Let's list Skills items: Technology/Area of Specialization (4 items) Basic Knowledge, Skills, And Abilities (6 items) includes physical ability. Competencies Required (6 items) We'll output as
  • ... each. Now About the role: we need to combine the intro paragraphs: first paragraph about Presidio, then "The Role ..." paragraph. We'll combine into one or two

    elements. Let's craft:

    At Presidio, we're at the forefront of a global technology revolution, transforming industries through cutting-edge digital solutions and next-generation AI. We empower businesses - and their internal customers - to achieve more through innovation, automation, and intelligent insights.

    The Site Support Engineer (Orlando) is responsible for the day-to-day technical operations, setup, and maintenance of Presidio's AI Solutions lab environment at the Orlando site. This hands-on role ensures that lab infrastructure, hardware, and demonstration environments are operational, well-maintained, and ready to support customer engagements, internal training, and solution validation activities. The Site Support Engineer works closely with Solutions Engineering, Lab Management, Field Sales, and vendor partners to ensure the Orlando site delivers a high-quality, reliable lab experience. This role translates infrastructure requirements into working environments, troubleshoots issues quickly, and helps maintain the readiness of demonstration assets that showcase Presidio's AI capabilities to clients and internal stakeholders.

    Now Responsibilities list as above. Now Skills list.