Senior Shared Data Platforms Developer
Sherwin-Williams · Cleveland, OH · 1 mo ago
Information TechnologyFull-time
We need to output HTML fragment with sections: About the role? Actually we have job description content. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the job description.
Content:
- Job Description: "Responsible for architecting and designing applications and managing the integration of their respective in-house applications, databases, and systems with third-party applications. Design and implement integration solutions within the Digital Integration layer for in-house and cloud business applications, databases, and systems. Analyze and troubleshoot complex integration issues to ensure seamless integration of applications and systems. Collaborate with cross-functional teams (i.e., Product Owner, DevOps Engineers, business leaders) to identify and build integration solutions to support business needs. Develop integration flows and APIs using middleware tools. Work closely with the Architecture community to manage or implement the API strategy of the organization. Configure and maintain middleware infrastructure to support application integrations and ensure high availability and performance. Provide technical support for integration-related issues, including system outages and performance problems. Document integration solutions, processes, and procedures to ensure knowledge sharing and sustainability. Role is office-based with flexibility to work up to 12 days from home per year within reasonable commuting distance of the Cleveland, OH office. Multiple openings available."
That's the description.
Then there is a "Responsibilities" heading but then some boilerplate: "#DNP; #DNP-LI; ; #NP; #dnp-jobright; #dnpjobright This position is not hybrid/remote and will be located at our Cleveland Headquarters office. 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. This position is also eligible for bonus based on performance and subject to the terms of the Company’s applicable plans."
We need to remove boilerplate like EEO, legal, etc. The responsibilities section: we have some content about location, criminal history, bonus. Those are not duties but maybe we can treat as responsibilities? The instruction: "Use
- for any list of duties/requirements/benefits". So we need to extract duties. The responsibilities list may be implied in the description; but there is a "Responsibilities" heading with some text. We need to preserve substantive information, not filler. The text after "Responsibilities" includes: "This position is not hybrid/remote and will be located at our Cleveland Headquarters office." That's location info (maybe schedule?). "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." That's a duty? It's about access. "The Company therefore has determined that a review of criminal history is necessary..." That's a requirement (background check). "This position is also eligible for bonus based on performance and subject to the terms of the Company’s applicable plans." That's compensation/bonus.
We need to decide sections: About the role (maybe the initial description). Responsibilities (list of duties). Requirements (education/experience). Qualifications (maybe same as requirements? The posting has "Qualifications REQUIREMENTS:" then bullet list). Skills (special skills). Benefits (mention of benefits link). Pay (wage range mentioned). Schedule (office-based with flexibility to work up to 12 days from home per year). Also mention multiple openings.
We must not invent or summarize away detail. Must preserve all substantive information.
We need to avoid boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The text includes EEO statements later; we must remove those. Also remove the "#DNP; #DNP-LI; ; #NP; #dnp-jobright; #dnpjobright" tags.
We need to output only HTML fragment.
Let's extract substantive content:
Job Description (initial paragraph) - could be considered "About the role". We'll put that in
About the role
then...
. Responsibilities: We have duties from description plus maybe the location and bonus etc. But we need to list duties as- . Let's gather duty statements:
- Architecting and designing applications and managing the integration of respective in-house applications, databases, and systems with third-party applications.
- Design and implement integration solutions within the Digital Integration layer for in-house and cloud business applications, databases, and systems.
- Analyze and troubleshoot complex integration issues to ensure seamless integration of applications and systems.
- Collaborate with cross-functional teams (i.e., Product Owner, DevOps Engineers, business leaders) to identify and build integration solutions to support business needs.
- Develop integration flows and APIs using middleware tools.
- Work closely with the Architecture community to manage or implement the API strategy of the organization.
- Configure and maintain middleware infrastructure to support application integrations and ensure high availability and performance.
- Provide technical support for integration-related issues, including system outages and performance problems.
- Document integration solutions, processes, and procedures to ensure knowledge sharing and sustainability.
- Role is office-based with flexibility to work up to 12 days from home per year within reasonable commuting distance of the Cleveland, OH office. (This could be schedule)
- Multiple openings available. (maybe not a duty but info)
- Position is not hybrid/remote and will be located at our Cleveland Headquarters office. (location)
- 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. (duty)
- This position is also eligible for bonus based on performance and subject to the terms of the Company’s applicable plans. (compensation)
We need to separate schedule, pay, benefits.
Schedule: "Role is office-based with flexibility to work up to 12 days from home per year within reasonable commuting distance of the Cleveland, OH office." Also "Position is not hybrid/remote and will be located at our Cleveland Headquarters office." That seems contradictory but we can combine: office-based, not hybrid/remote, located at Cleveland HQ, with up to 12 days remote per year.
Pay: "This position is also eligible for bonus based on performance and subject to the terms of the Company’s applicable plans." Also later: "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 we don't have actual wage range numbers; they are not given. The posting mentions "wage range listed for this role" but no actual numbers provided in the text we have. Since we cannot include placeholder like "not specified". We should not create Pay section unless posting actually states them. It mentions wage range but not actual numbers; that's still stating that there is a wage range but not giving numbers. Is that considered substantive? It says "The wage range listed for this role takes into account..." but no actual range. Since we don't have the range, we cannot provide specifics. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". So we should not create a Pay section if we don't have actual numbers. However we could mention bonus eligibility. But that's not pay range. The instruction says include a section ONLY when the posting has real, specific content for it. So we could maybe include a Pay section with the bonus eligibility? But that's not pay. Might be better to omit Pay section.
Benefits: "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."
That's substantive: description of benefits and link. So we can include Benefits section.
Requirements: "Bachelor’s degree in Computer Science, Information Systems, Electronics Engineering or a related field and five (5) years of experience as an IT Application Developer, Oracle Developer, Systems Engineer, Consultant or related role where required experience gained."
Also "Must be eighteen years or older". That's a requirement.
Qualifications: The posting has "Qualifications REQUIREMENTS:" then list of special skills. Actually the section titled "Qualifications REQUIREMENTS:" includes both education/experience and special skills. Might be overlapping. We need to separate Requirements and Qualifications and Skills as per instruction. But we can decide to put education/experience under Requirements, and special skills under Skills. Qualifications maybe we can combine? The instruction says use headings for Requirements, Qualifications, Skills. We need to decide what goes where based on content.
The posting: after "Qualifications" heading, there is "REQUIREMENTS: Bachelor’s degree ... and five (5) years of experience ..." Then "SPECIAL SKILLS: Also requires experience in the following: Five (5) years in application integrations and middleware development; Four (4) years in Integration technologies, APIs, and web; Oracle ERP; Database Management Systems and Operating Systems; System Configuration and Solution Analysis; and Software Development Lifecycle (SDLC) Methodology. Must be eighteen years or older"
Thus we can treat:
- Requirements: education + years experience (IT Application Developer etc.)
- Qualifications: maybe the same as requirements? But we already used Requirements for education/experience. Qualifications could be the special skills? But they also have a SPECIAL SKILLS heading. Perhaps we should map:
Requirements: education + base experience.
Qualifications: maybe the same as requirements? But we need to avoid duplication. Could put Qualifications as the same as Requirements? Might be redundant. Better to follow the posting: they have Qualifications heading then REQUIREMENTS and SPECIAL SKILLS subheadings. So we could output:
Qualifications
Requirements: Bachelor’s degree ... and five (5) years of experience as an IT Application Developer, Oracle Developer, Systems Engineer, Consultant or related role where required experience gained.
Special Skills: Five (5) years in application integrations and middleware development; Four (4) years in Integration technologies, APIs, and web; Oracle ERP; Database Management Systems and Operating Systems; System Configuration and Solution Analysis; and Software Development Lifecycle (SDLC) Methodology. Must be eighteen years or older.
But the instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they expect separate headings for Requirements, Qualifications, Skills. However the posting lumps them. We could still create separate sections: Requirements (education/experience), Qualifications (maybe same as requirements? but we could treat Qualifications as the special skills?), Skills (maybe also special skills?). This is confusing. Better to interpret: The posting's "Qualifications" section includes both REQUIREMENTS and SPECIAL SKILLS. So we can map: - Requirements: education + base experience. - Qualifications: maybe the same as requirements? But we could treat Qualifications as the combination of education/experience and special skills? But then Skills would
- . Let's gather duty statements:
- Architecting and designing applications and managing the integration of respective in-house applications, databases, and systems with third-party applications.
- Design and implement integration solutions within the Digital Integration layer for in-house and cloud business applications, databases, and systems.
- Analyze and troubleshoot complex integration issues to ensure seamless integration of applications and systems.
- Collaborate with cross-functional teams (i.e., Product Owner, DevOps Engineers, business leaders) to identify and build integration solutions to support business needs.
- Develop integration flows and APIs using middleware tools.
- Work closely with the Architecture community to manage or implement the API strategy of the organization.
- Configure and maintain middleware infrastructure to support application integrations and ensure high availability and performance.
- Provide technical support for integration-related issues, including system outages and performance problems.
- Document integration solutions, processes, and procedures to ensure knowledge sharing and sustainability.
- Role is office-based with flexibility to work up to 12 days from home per year within reasonable commuting distance of the Cleveland, OH office. (This could be schedule)
- Multiple openings available. (maybe not a duty but info)
- Position is not hybrid/remote and will be located at our Cleveland Headquarters office. (location)
- 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. (duty)
- This position is also eligible for bonus based on performance and subject to the terms of the Company’s applicable plans. (compensation)
We need to separate schedule, pay, benefits.
Schedule: "Role is office-based with flexibility to work up to 12 days from home per year within reasonable commuting distance of the Cleveland, OH office." Also "Position is not hybrid/remote and will be located at our Cleveland Headquarters office." That seems contradictory but we can combine: office-based, not hybrid/remote, located at Cleveland HQ, with up to 12 days remote per year.
Pay: "This position is also eligible for bonus based on performance and subject to the terms of the Company’s applicable plans." Also later: "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 we don't have actual wage range numbers; they are not given. The posting mentions "wage range listed for this role" but no actual numbers provided in the text we have. Since we cannot include placeholder like "not specified". We should not create Pay section unless posting actually states them. It mentions wage range but not actual numbers; that's still stating that there is a wage range but not giving numbers. Is that considered substantive? It says "The wage range listed for this role takes into account..." but no actual range. Since we don't have the range, we cannot provide specifics. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". So we should not create a Pay section if we don't have actual numbers. However we could mention bonus eligibility. But that's not pay range. The instruction says include a section ONLY when the posting has real, specific content for it. So we could maybe include a Pay section with the bonus eligibility? But that's not pay. Might be better to omit Pay section.
Benefits: "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."
That's substantive: description of benefits and link. So we can include Benefits section.
Requirements: "Bachelor’s degree in Computer Science, Information Systems, Electronics Engineering or a related field and five (5) years of experience as an IT Application Developer, Oracle Developer, Systems Engineer, Consultant or related role where required experience gained."
Also "Must be eighteen years or older". That's a requirement.
Qualifications: The posting has "Qualifications REQUIREMENTS:" then list of special skills. Actually the section titled "Qualifications REQUIREMENTS:" includes both education/experience and special skills. Might be overlapping. We need to separate Requirements and Qualifications and Skills as per instruction. But we can decide to put education/experience under Requirements, and special skills under Skills. Qualifications maybe we can combine? The instruction says use headings for Requirements, Qualifications, Skills. We need to decide what goes where based on content.
The posting: after "Qualifications" heading, there is "REQUIREMENTS: Bachelor’s degree ... and five (5) years of experience ..." Then "SPECIAL SKILLS: Also requires experience in the following: Five (5) years in application integrations and middleware development; Four (4) years in Integration technologies, APIs, and web; Oracle ERP; Database Management Systems and Operating Systems; System Configuration and Solution Analysis; and Software Development Lifecycle (SDLC) Methodology. Must be eighteen years or older"
Thus we can treat:
- Requirements: education + years experience (IT Application Developer etc.)
- Qualifications: maybe the same as requirements? But we already used Requirements for education/experience. Qualifications could be the special skills? But they also have a SPECIAL SKILLS heading. Perhaps we should map:
Requirements: education + base experience.
Qualifications: maybe the same as requirements? But we need to avoid duplication. Could put Qualifications as the same as Requirements? Might be redundant. Better to follow the posting: they have Qualifications heading then REQUIREMENTS and SPECIAL SKILLS subheadings. So we could output: