2027 Summer Engineering Co-Op - Columbus, OH

We need to output HTML fragment only, with sections as needed: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning). Also remove duplicated lines, application instructions. We need to identify sections present: The posting includes: - Job Description paragraph: "The Engineering Co-op Program is a 15-week program hosted by the Engineering Department. Co-ops will assist the site Engineering Managers with day-to-day tasks and special projects, contributing to the goals and initiatives of the department. This Co-op begins May 2027. Co-ops will report to our Columbus, Ohio site. Job duties include contact with other employees and access confidential and proprietary information and/or other items of value, and such access may be supervised or unsupervised. The Company therefore has determined that a review of criminal history is necessary to protect the business and its operations and reputation and is necessary to protect the safety of the Company’s staff, employees, and business relationships." That's about the role. Could be "About the role" heading. - Responsibilities: list bullet points under "Responsibilities The Engineering Co-op will assist the Engineering Manager with: Equipment analysis New installations and facility revisions Developing drawings and specifications for equipment layout Investigation of new plant engineering processes and techniques Special projects as identified by the Engineering Team Present final presentation at the end of rotation to site, program, and division leadership" - Qualifications: includes Minimum Requirements bullet list and Preferred Qualifications bullet list. - About Us: description of company, mission, benefits mention. - Benefits: mention "A general description of benefits offered can be found at http://www.myswbenefits.com/ . Click on “Candidates” to view benefit offerings that you may be eligible for if you are hired as a Sherwin-Williams employee." That's benefits info. - Compensation: "Compensation decisions are dependent on the facts and circumstances of each case and will impact where actual compensation may fall within the stated wage range. The wage range listed for this role takes into account the wide range of factors considered in making compensation decisions including skill sets; experience and training; licensure and certifications; and other business and organizational needs. The disclosed range estimate has not been adjusted for the applicable geographic differential associated with the location at which the position may be filled. The wage range, other compensation, and benefits information listed is accurate as of the date of this posting. The Company reserves the right to modify this information at any time, with or without notice, subject to applicable law." But no actual wage range numbers given. So we cannot create Pay section because no specific numbers. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have some statement about benefits but no specifics; but we have a statement about benefits offered and a link. Is that enough to create Benefits section? The rule: "Prefer a few substantive sections over many thin ones." Benefits: we have a statement that benefits exist and a link. That's substantive enough? It says "A general description of benefits offered can be found at ..." That's not specific benefits but indicates benefits exist. Might be okay to include Benefits section with that info. However we must not include filler like "commensurate with experience". This is not filler; it's a statement about benefits. So we can include Benefits section with that paragraph. Schedule: No mention of schedule (hours, full-time/part-time). Not present, so omit. Pay: No wage range numbers, so omit. Skills: Not explicitly listed; maybe we could treat Microsoft Office experience as skill but it's under qualifications. Could create Skills section? The rule: use headings only when posting has real, specific content for it. We have qualifications and responsibilities; we could combine qualifications and skills into Qualifications section. Probably better to have Qualifications (including minimum and preferred) and Responsibilities. About Us could be "About the company" but we have "About Us" heading maybe not required; but we could include as "About the company" but rule says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). About Us is not in list but could be considered "About the role"? Actually "About the role" is for role description. The "About Us" is company description; maybe we could omit or incorporate into a short paragraph under a generic heading? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exhaustive; we could still use other headings if appropriate? Probably better to stick to those examples. So we could treat company description as part of "About the role"? Not exactly. Could we omit it? It's substantive info about company mission and benefits. Might be worth including under a heading like "About the company" but not in list. However the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. So we could add "About the company" heading. But to be safe, maybe we incorporate the company description into a brief paragraph under "About the role" or as a separate

without heading? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose." It doesn't forbid other headings, but suggests using those for sections. I'd include headings for About the role, Responsibilities, Qualifications, Benefits. Possibly also "About the company" but maybe not needed. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, equal-opportunity, scam-warning, legal, etc. Also remove duplicated lines. Let's extract substantive content: About the role (job description): - Engineering Co-op Program is a 15-week program hosted by the Engineering Department. - Co-ops will assist the site Engineering Managers with day-to-day tasks and special projects, contributing to the goals and initiatives of the department. - This Co-op begins May 2027. - Co-ops will report to our Columbus, Ohio site. - Job duties include contact with other employees and access confidential and proprietary information and/or other items of value, and such access may be supervised or unsupervised. - The Company therefore has determined that a review of criminal history is necessary to protect the business and its operations and reputation and is necessary to protect the safety of the Company’s staff, employees, and business relationships. Responsibilities (list): - Equipment analysis - New installations and facility revisions - Developing drawings and specifications for equipment layout - Investigation of new plant engineering processes and techniques - Special projects as identified by the Engineering Team - Present final presentation at the end of rotation to site, program, and division leadership Qualifications: Minimum Requirements: - Must be legally authorized to work in the country of employment without needing sponsorship for employment work visa status now or in the future - Must be at least eighteen (18) years of age or older - Must be currently enrolled in a college or university at the time of the Co-op program - Must be currently pursuing an Engineering Degree with sophomore standing or higher Preferred Qualifications: - Have at least one (1) year of experience using Microsoft Office products (e.g. Word, Excel, PowerPoint, Teams, and/or Outlook) - Currently pursuing a degree in Electrical Engineering, Mechanical Engineering, or Chemical Engineering - Have previous experience working in a team-oriented setting including work experience, extracurricular activities, military service, etc. - Have at least one (1) year of experience in leadership role(s), supervising others, or leading teams - Have at least one (1) year of work experience in a manufacturing, distribution, operations function or have completed a Sherwin-Williams Development Program in an Engineering function - Have previous internship or Co-op experience in the Sherwin-Williams Global Supply Chain Division - Willingness to relocate for future job opportunities About Us / Company description: - At Sherwin-Williams, our purpose is to inspire and improve the world by coloring and protecting what matters. - Our paints, coatings and innovative solutions make the places and spaces in our world brighter and stronger. - Your skills, talent and passion make it possible to live this purpose, and for customers and our business to achieve great results. - Sherwin-Williams is a place that takes its stability, growth and momentum and translates it to possibility for our people. - Our people are behind the strength of our success, and we invest and support you in: - Life … with rewards, benefits and the flexibility to enhance your health and well-being - Career … with opportunities to learn, develop new skills and grow your contribution - Connection … with an inclusive team and commitment to our own and broader communities - It's all here for you... let's Create Your Possible At Sherwin-Williams, part of our mission is to help our employees and their families live healthier, save smarter and feel better. This starts with a wide range of world-class benefits designed for you. From retirement to health care, from total well-being to your daily commute—it matters to us. A general description of benefits offered can be found at http://www.myswbenefits.com/ . Click on “Candidates” to view benefit offerings that you may be eligible for if you are hired as a Sherwin-Williams employee. Compensation: Not specific numbers, so we omit Pay section. Schedule: Not mentioned. We must not include boilerplate like "Compensation decisions are dependent..." but that is about compensation; but since we are not making a Pay section, we could still include that paragraph under a generic heading? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The compensation paragraph is not exactly boilerplate but it's generic legal-ish. Might be considered boilerplate? It's about compensation policy. Since we are not making a Pay section, maybe we should omit it entirely because it's not specific. The rule: "Preserve ALL substantive information; do NOT invent or summarize away detail." The compensation paragraph is substantive? It says compensation decisions depend on factors, wage range listed takes into account factors, etc. It's somewhat generic but still info about compensation. However we cannot create a Pay section because no actual range. Could we include it as a

  under a heading like "Compensation"? Not in the list but maybe allowed. But the instruction says "Prefer a few substantive sections over many thin ones." Including a compensation paragraph without numbers might be thin. Better to omit it because it's not specific and could be considered boilerplate. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't forbid mentioning compensation in prose elsewhere. But we could keep it as a short paragraph under a generic heading like "Compensation details". However the heading list didn't include Compensation. Might be okay to add a heading "Compensation" as it's not in examples but could be used. But to be safe, maybe we omit it because it's not specific and could be considered boilerplate. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." If we omit it, we are losing some info about compensation policy. Is that substantive? It's somewhat generic but still info. I'd lean to keep it as a brief paragraph under a heading "Compensation" (h3) but we must not create Pay section unless posting actually states them. The posting does state compensation decisions etc. So we could include a Compensation section with that paragraph. However the examples list includes Pay, not Compensation. But we could treat Pay as compensation. Since no specific wage range, we