IT Applications Intern (Summer 2027)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Company Description: we can include as maybe "About the role"? Actually "Company Description" is about company, not role. Could be "About the role" maybe includes purpose. The posting includes "Position Purpose" and "Essential Functions". So we can have sections: About the role (maybe combine Position Purpose and Company Description?), Responsibilities (Essential Functions), Requirements (Education And Training, Minimum Qualifications), Skills (list of skills), Benefits (benefits description), Pay (none), Schedule (none). We must not create Pay/Schedule unless present. There's no pay or schedule specifics. So omit those sections. We need to preserve all substantive info, not invent. We need to remove boilerplate: EEO, etc. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. There's no explicit application instructions. We need to format lists with

• . Use

  for prose. We need to avoid repeating job title as heading (not present). No Job ID. We need to include sections only when posting has real specific content. So we need to decide headings. Potential sections: - About the role (could include Company Description and Position Purpose) - Responsibilities (Essential Functions) - Requirements (Education And Training + Minimum Qualifications) - Skills (list of skills: customer-service orientation, SQL, OOP, HTML/CSS/JS, communication, MS Office, ability to work independently/team) - Benefits (benefits description) We must not include headings with filler like "commensurate with experience". Not present. Now extract content. Company Description paragraph: "Hendrickson is the leading global manufacturer and supplier of medium- and heavy-duty mechanical, elastomeric and air suspensions; integrated and non-integrated axle systems; auxiliary lift axle systems; parabolic and multi-leaf springs; stabilizers; and bumper and trim components to the global commercial transportation industry. The heart of Hendrickson is its people. We are always searching for talented students to join our team, and value the opportunity to develop students’ knowledge. An internship or co-op with Hendrickson is a hands-on opportunity for students to bring the classroom to life. Our commitment to you as a PATH Student Program Member is to deliver you a Real-world, Innovative, Diverse Experience which will set you up for success. We aim to nurture the future leaders of the industry with the passion, creativity, and drive needed to continue down the path of advancing the world around us." Position Purpose: "Assist team with data preparation and cleansing for migration to QAD 2016 ee and QAD EAM systems from iSeries (AS400) and iMaint, monitor and complete help desk tickets (Tier 1) for end-user support and troubleshooting of software applications, create and update work instructions, project scopes, etc., and assist with routine tasks." Essential Functions list bullet points: - Data preparation and cleansing - Monitor, research and complete help desk tickets for end-user support and troubleshooting - Create and update user guides, manuals, work instructions, test scripts, etc. - Participate in user acceptance testing for new applications and enhancements - Gather requirements for new applications or enhancements to create project scopes and supporting documentation - Development and modification of SQL queries and/or stored procedures - Bug-fixing within internal applications - Assist team with other projects and tasks as needed Education And Training: "Current studies in the field of Information Technology" Minimum Qualifications list: - Current studies in the field of Information Technology - Strong customer-service orientation - Strong understanding of SQL - Basic understanding of Object-Oriented Programming, preferably C#, VB.NET - Familiarity with HTML, HTML5, CSS, CSS3, JavaScript - Above average communication skills, written and verbal - attention to detail is a must - Proficient in MS Office/MS 365 (Word, Excel, PowerPoint, Teams, Outlook, OneNote, etc.) - Ability to work independently and as part of a team Physical Demands etc maybe not needed as section? Could be omitted as not requested headings. Not required. Behavioral Traits: similar to qualifications but could be merged. We need to avoid duplication: Education And Training repeats "Current studies in the field of Information Technology". Minimum Qualifications also includes that. We should preserve all substantive info but not duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid deduplication but we should keep info. Could keep both but might be redundant. Safer to keep both but maybe combine? I'd keep both but note duplication is okay. However we should not repeat same sentence twice in same section maybe okay. We'll create sections:

  About the role

  with

  containing Company Description + Position Purpose combined.

  Responsibilities

  with
  • list of Essential Functions.

    Requirements

    with

    maybe combine Education And Training and Minimum Qualifications? Could be two

    or a

    . Since they are list-like, we can use
    • for each qualification. But we also have Education And Training as a statement; we could treat as a

      then list. Better:

      Requirements

      Current studies in the field of Information Technology.

      • Strong customer-service orientation
      ... etc. But we already have the same statement; we could just have a

      for Education And Training and then list for Minimum Qualifications. Skills: maybe we separate skills from requirements? The instruction says use headings for Skills if present. We have many skill items: customer-service orientation, SQL, OOP, HTML/CSS/JS, communication, MS Office, ability to work independently/team. Could put them under Skills. But we already put them under Requirements. To avoid duplication, we could have Requirements for education and training, and Skills for technical/soft skills. Let's decide: - About the role: company description + position purpose. - Responsibilities: essential functions. - Requirements: Education And Training (current studies in IT). - Skills: list of qualifications (customer service, SQL, OOP, HTML/CSS/JS, communication, MS Office, teamwork). - Benefits: benefits description. We must not create Pay/Schedule. Now extract Benefits paragraph: "We offer a full complement of benefits that include medical, dental, and vision insurance; life, travel, and disability insurance; a flexible spending account; 401K plans; a pension plan; paid holidays and vacation. We also offer financial assistance programs if you decide to adopt a child or want to pursue further education. We have a comprehensive wellness program and an Employee Assistance Program, that supports individuals in the proactive management of their overall health and wellness." We'll put that in

      under Benefits. Now ensure we removed boilerplate: EEO statement, etc. Also remove "Physical Demands", "Environmental Conditions", "Behavioral Traits" maybe not needed as headings; but we could incorporate some into Skills? But we already have skills list; behavioral traits could be considered skills but we can ignore as not required headings. However we must preserve ALL substantive information; if we omit those sections, we lose info. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot drop Physical Demands, Environmental Conditions, Behavioral Traits unless we incorporate them elsewhere. But we are not required to have headings for those; we could embed them in a section like "Additional Information" but not in allowed headings list. The allowed headings are only those listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We cannot create other headings. So we must fit that info into those sections if possible. Physical Demands: "Ability to travel to division and plant sites as required (limited to none). Frequent sitting, work at computer for extended periods of time." Could be placed under Requirements or Skills? Maybe under Requirements as additional requirement. Environmental Conditions: "Office setting. Exposure to cold data rooms where equipment is located. Plant floor environment requires the wearing of protective equipment." Could be under Requirements. Behavioral Traits: "Strong verbal, written and interpersonal skills. Must exhibit the highest professionalism, self-initiative, enthusiasm, and work ethic. Customer service skills: Ability to demonstrate patience and understanding when helping users of IT services." Could be under Skills. Thus we can incorporate these into Requirements or Skills. We must not create new headings like "Physical Demands". So we will add those details as

      or

      • under appropriate sections. Let's allocate: - Requirements: Education And Training (current studies in IT) plus Physical Demands and Environmental Conditions maybe as

        paragraphs. - Skills: list of technical and soft skills including customer-service orientation, SQL, OOP, HTML/CSS/JS, communication, MS Office, ability to work independently/team, plus Behavioral Traits (professionalism, self-initiative, enthusiasm, work ethic, patience, understanding). We need to avoid duplication: customer-service orientation appears both in Minimum Qualifications and Behavioral Traits? Actually Minimum Qualifications includes "Strong customer-service orientation". Behavioral Traits includes "Customer service skills: Ability to demonstrate patience and understanding when helping users of IT services." So we can keep both. Now we need to format. Let's craft HTML. Start with

        About the role

        Hendrickson is the leading global manufacturer and supplier of medium- and heavy-duty mechanical, elastomeric and air suspensions; integrated and non-integrated axle systems; auxiliary lift axle systems; parabolic and multi-leaf springs; stabilizers; and bumper and trim components to the global commercial transportation industry. The heart of Hendrickson is its people. We are always searching for talented students to join our team, and value the opportunity to develop students’ knowledge. An internship or co-op with Hendrickson is a hands-on opportunity for students to bring the classroom to life. Our commitment to you as a PATH Student Program Member is to deliver you a Real-world, Innovative, Diverse Experience which will set you up for success. We aim to nurture the future leaders of the industry with the passion, creativity, and drive needed to continue down the path of advancing the world around us. Assist team with data preparation and cleansing for migration to QAD 2016 ee and QAD EAM systems from iSeries (AS400) and iMaint, monitor and complete help desk tickets (Tier 1) for end-user support and troubleshooting of software applications, create and update work instructions, project scopes, etc., and assist with routine tasks.

        Now Responsibilities:

        Responsibilities

        • Data preparation and cleansing
        • Monitor, research and complete help desk tickets for end-user support and troubleshooting
        • Create and update user guides, manuals, work instructions, test scripts, etc.
        • Participate in user acceptance testing for new applications and enhancements
        • Gather requirements for new applications or enhancements to create project scopes and supporting documentation
        • Development and modification of SQL queries and/or stored procedures
        • Bug-fixing within internal applications
        • Assist team with other projects and tasks as needed
        Now Requirements:

        Requirements

        Current studies in the field of Information Technology.

        Ability to travel to division and plant sites as required (limited to none). Frequent sitting, work at computer for extended periods of time.

        Office setting. Exposure to cold data rooms where equipment is located. Plant floor environment requires the wearing of protective equipment.

        Now Skills:

        Skills

        • Strong customer-service orientation
        • Strong understanding of SQL
        • Basic understanding of Object-Oriented Programming, preferably C