Jobs · Information Technology · Ohio

Infrastructure Engineer II

ODW Logistics · Columbus, OH · 3 wk ago
Information Technology$81.75/hrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if content exists. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate like EEO, equal opportunity, disclaimer, navigation, cookie, etc. Must not create sections with filler like "commensurate with experience". Must include Pay and Schedule only if posting actually states them. The posting includes "Salary Pay Grade Level 17 Salary Range $81.750 to $109,000". So we have Pay info. No schedule info. So we should include Pay section. Benefits? Not mentioned explicitly. There's no benefits listed. So we should not include Benefits heading. Skills? Could be derived from qualifications but we should only include if posting has specific content for Skills. The posting includes "Capabilities" list, which could be considered Skills. But the instruction: Use headings for Skills if posting has real, specific content. The "Capabilities" section lists skills like troubleshooting, communication, etc. That seems like Skills. We could put that under Skills heading. However we also have Qualifications And Education section. That includes Required Qualifications, Preferred Qualifications, Education & Experience, Certifications. That's a lot. We could combine into Qualifications heading. The instruction: Prefer a few substantive sections over many thin ones. So we could have About the role (from Who We Are and Position Summary), Responsibilities (Essential Responsibilities), Qualifications (Qualifications And Education plus Certifications maybe), Skills (Capabilities). Pay (Salary). No Benefits, Schedule. We must not include boilerplate like equal opportunity, disclaimer, etc. Also remove duplicated lines. Also remove "Experience Fulfillment At Odw Logistics." etc. We need to preserve all substantive information. So we need to include the content from Who We Are, Position Summary, Essential Responsibilities, Qualifications And Education (including Required Qualifications, Preferred Qualifications, Education & Experience, Certifications), Capabilities, Physical & Mental Requirements? That's also substantive. Should we include that? It's not under any of the allowed headings. Could we put it under Requirements? Possibly. But the instruction says use headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could map Physical & Mental Requirements to Requirements heading. However Requirements heading is generic; we could include both qualifications and physical requirements under Requirements. But we also have Qualifications heading separate. Might be overlapping. Better to follow the list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide what goes where. About the role: Who We Are + Position Summary. Responsibilities: Essential Responsibilities. Requirements: Could include Physical & Mental Requirements? Or maybe we treat Requirements as the "Required Qualifications". But we already have Qualifications heading for qualifications. Hmm. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they expect those headings. We need to include sections only when posting has real, specific content for it. So we need to decide content for each. - About the role: we have Who We Are and Position Summary. Good. - Responsibilities: Essential Responsibilities. - Requirements: Could be the "Physical & Mental Requirements" plus maybe "Experience supporting enterprise infrastructure technologies" etc? But those are qualifications. However we have Qualifications heading separate. So maybe Requirements is for things like "Physical & Mental Requirements" and maybe "Ability to..." etc. But we also have Capabilities which could be Skills. - Qualifications: The "Qualifications And Education" section including Required Qualifications, Preferred Qualifications, Education & Experience, Certifications. - Skills: The "Capabilities" list. - Benefits: none. - Pay: Salary range. - Schedule: none. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. We must not include empty headings. Now we need to format content: Use
  • for any list of duties/requirements/benefits, and

    for prose. We need to decide what is a list vs prose. For About the role: we have two paragraphs: Who We Are (a paragraph) and Position Summary (a paragraph). Could combine into one

    or two

    s. Probably two

    elements. For Responsibilities: It's a long list of duties, each sentence starts with a verb. Could be formatted as

    • each duty. We need to preserve all substantive information; we should not lose any duty. So we need to split the responsibilities into list items. The responsibilities paragraph is a long sentence with many clauses separated by periods. We can split at each period that ends a duty. Let's extract: "Implement, support, maintain, and optimize enterprise infrastructure across on-premises, cloud, and hybrid environments." "Support infrastructure platforms including networking, servers, virtualization, operating systems, storage, collaboration technologies, monitoring systems, and cloud services." "Support and maintain cloud and hybrid infrastructure services, including identity, networking, storage, backup, recovery, and monitoring solutions." "Assist with ensuring high availability, performance, resiliency, and operational effectiveness of business-critical systems." "Monitor infrastructure health, capacity, availability, and performance, identifying issues and opportunities for improvement." "Participate in infrastructure upgrades, migrations, deployments, and technical projects while coordinating with internal stakeholders, vendors, and service providers." "Collaborate with IT leadership, business stakeholders, and technical teams to support business requirements and technology initiatives." "Implement and support enhancements to infrastructure platforms, cloud services, automation solutions, and enterprise technology systems." "Assist with implementing infrastructure security controls, vulnerability remediation, patch management, access management, and system hardening activities." "Support backup and recovery operations, disaster recovery exercises, security reviews, and operational resiliency initiatives." "Develop and maintain scripts, automation, and process improvements that increase efficiency, consistency, and reliability." "Troubleshoot complex infrastructure issues and serve as an escalation point for operational support activities." "Perform operational analysis and provide recommendations to improve system reliability, performance, supportability, and overall business value." "Partner with vendors, service providers, and contractors to support infrastructure-related products and services." "Create and maintain technical documentation, system configurations, operational procedures, support records, and technical diagrams." "Perform technical validation, testing, and user acceptance activities for new and updated systems." "Assist with user training and knowledge transfer activities when appropriate." "Stay current with emerging technologies, cybersecurity best practices, and industry trends." "Perform other duties as assigned." That seems comprehensive. Now Requirements: Physical & Mental Requirements list. Let's extract: "While performing the duties of this job, the employee requires the ability to:" Then bullet list: - Hear, read and comprehend, write and communicate - Continuously sit, type, and perform repetitive wrist motion - Occasionally stand, walk, bend, squat/kneel, twist/turn or reach - Focus (with or without corrective lenses) to see close and distant, along with depth perception capabilities - Lift up to 40 lbs. Also note: "The physical demands herein are representative of those that must be met by an employee to successfully perform the essential functions of this job. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." We could include that as prose after list. Now Qualifications: We have Required Qualifications, Preferred Qualifications, Education & Experience, Certifications. We need to preserve all. Could format as
      • for each bullet. But there are headings inside. We could keep headings as

        maybe? But instruction: Use

        for section headings only. Inside sections we can use

        for prose and

        • for lists. So we could treat each subsection as a

          heading? Not allowed to use other headings. So we could put the subsection titles in

          with bold? But we cannot add extra headings. We could just list items under Qualifications as a combined list, but we need to preserve the distinction between Required, Preferred, Education & Experience, Certifications. We could keep them as separate

          paragraphs introducing each group, then

          • for items. E.g.:

            Required Qualifications

            • Experience supporting enterprise infrastructure technologies in a business environment.
            • ...

              That seems acceptable: we are not using

              inside, just

              for subsection titles. Similarly for Preferred Qualifications, Education & Experience, Certifications. Now Skills: Capabilities list. We'll make

              • each capability. Now Pay: Salary range: "Salary Pay Grade Level 17 Salary Range $81.750 to $109,000". Note there is a typo: $81.750 (should be 81,750). We'll preserve as given. We'll output as

                Salary Pay Grade Level 17 Salary Range $81.750 to $109,000

                . Now ensure we removed boilerplate: Remove equal opportunity statements, disclaimer, "Experience Fulfillment At Odw Logistics.", "ODW Logistics is an equal opportunity employer..." duplicates, etc. Also remove "OUR VALUES" section? That's values; not under any heading; could be considered boilerplate? It's substantive but not fitting any heading. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Values might be considered not boilerplate but not fitting headings. However we must preserve ALL substantive information. Where to put values? Could be part of About the role? Possibly include as a paragraph under About the role. The values are: Respect, Trust, Team, Opportunity with descriptions. That's substantive. We could include them under About the role as a paragraph. But we must not invent sections. We could add a

                under About the role after the position summary. Thus About the role will have: Who We Are paragraph, Position Summary paragraph, Values paragraph (maybe as a list). But values are not a list of duties; we could format as

                • each value with description. However the instruction says use
                  • for any list of duties/requirements/benefits. Values are not duties/requirements/benefits, but could be considered a list. Safer to put as

                    prose. We'll include values as a paragraph: "Our values are: Respect | Give and it will be given. We treat others as we want to be treated. We cannot control events, but we can control our response. We build respect through honesty, fairness, and integrity. Trust | Earned over time. We do what we say we will do. We are clear, direct, and honest. We seek to understand and be understood. Team | Accomplish more together. We work hard toward a common goal. We desire to make everyone successful. We achieve the best results as a team. Opportunity | Realize your potential. We believe all people have significance and potential. We understand work and life are integrated and we value both. We strive to make an impact in the world around us." Now ensure we didn't include any duplicated lines. Now we need to output only HTML fragment, no /, no markdown. Let's craft. Structure:

                    About the role

                    Who We Are ODW Logistics is a people-focused and customer-driven third-party logistics (3PL) provider committed to delivering seamless end-to-end supply chain solutions. Our extensive range of services includes supply chain design and innovation, warehousing, efficient distribution and fulfillment, freight brokerage, transportation management, and specialized e-commerce fulfillment solutions.

                    Position Summary The Infrastructure Engineer II is responsible for implementing, supporting, maintaining, and continuously improving enterprise infrastructure across on-premises

Similar jobs