Senior Data Marketplace Platform Enablement Analyst

We need to output HTML fragment with sections: headings

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job description. Content: - Job Description paragraph: "The Data Marketplace Platform Enablement Analyst specializes..." This is about the role. Could be "About the role" section. - Responsibilities: bullet list (multiple sentences). We'll put under

Responsibilities

with

• each. - Qualifications: includes Education and Experience Required and Preferred. Could be under

  Qualifications

  (or Requirements). The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose Qualifications for education/experience. Could also have Skills section for specific skills like BI/Analytics Technologies, etc. But we should avoid thin sections. Let's see content: Qualifications includes Education and Experience Required (bachelor's degree, 7 years experience, etc.) plus list of abilities: proficient in data analysis, ability to communicate, experience with large datasets, familiarity with learning and development techniques, BI/Analytics Technologies (list), must be legally authorized, must be 18+. Preferred: Data Warehouse or Analytics platform experience such as Databricks, Snowflake or PowerBI. We could put all that under Qualifications. Or split into Requirements (education/experience) and Skills (technical). But we need to avoid thin sections. Perhaps combine into Qualifications. Also there is "About Us" section describing company, benefits, etc. That could be "About the role"? Actually "About Us" is company description. Could be omitted? The instruction: include a section ONLY when the posting has real, specific content for it. The "About Us" is generic company description; could be considered not specific to role. Might be omitted. However there is also benefits description: "At Sherwin-Williams, part of our mission is to help our employees..." and link to benefits. That's benefits info. Could create Benefits section with that description. But it's generic; still it's specific content about benefits. The instruction says: never create Benefits section unless posting actually states them. It does state benefits: "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/." That's benefits info. So we can include Benefits section with that paragraph. Pay: there is a paragraph about compensation decisions, wage range, etc. It mentions wage range but not actual numbers. It says "The wage range listed for this role takes into account..." but no actual range given. It's vague. According to instruction: do NOT emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does not give actual wage range numbers; it just says wage range listed but not provided. That's likely placeholder. So we should not create Pay section. Schedule: not mentioned (no info about remote/hours). It says "This is not a remote position and will report to our Global Headquarters in downtown Cleveland, OH." That's location, not schedule. So no Schedule section. Skills: Could be extracted from qualifications but we already have Qualifications. Might not need separate Skills. Thus sections: About the role (intro paragraph), Responsibilities (list), Qualifications (education/experience + abilities + preferred), Benefits (benefits paragraph). Possibly also "Location" but not in allowed headings. Could fold location into About the role paragraph. We must not repeat job title as heading. Already not. We must not include Job ID etc. We must remove boilerplate: EEO, legal, scam warning, etc. At end there is EEO statement, VEVRAA, etc. Remove. Also remove "About Us" generic company description? Might keep as part of Benefits? Actually "About Us" includes mission statement etc. Could be considered not specific to role; but we could incorporate into Benefits? Probably better to omit "About Us" entirely, as it's boilerplate-ish. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About Us" is substantive about company mission. Might be considered relevant. But we have no heading for company description; we could put it under About the role? But About the role is for role description. Could we add a section "About the company"? Not in allowed headings. So we might need to omit it, but that would be removing substantive info. However the instruction says "Prefer a few substantive sections over many thin ones." It doesn't forbid omitting company description if not fitting headings. But we must preserve ALL substantive information; we cannot omit. So we need to include it somewhere. Perhaps we can include it under About the role as a paragraph after role description. That would be okay: About the role section can contain both role description and company overview. The heading is About the role, but we can include company info there. That seems acceptable. Thus About the role section will contain: the role description paragraph, plus the "About Us" paragraph (mission, purpose, etc.) maybe also the benefits? But benefits we will separate. Let's extract: Role description: "The Data Marketplace Platform Enablement Analyst specializes in the enablement leg of our data self-service program by designing and configuring a platform experience that allows users of all personas to leverage data products with minimal IT involvement to derive business insights. The role leverages understanding of existing and target consumption patterns and establishes standards and configurations that enable those patterns. Through this combination, the role can facilitate an enterprise data-driven culture by making access to data and insights faster, easier, and more relevant to individual users’ contexts." About Us: "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." But note that the benefits paragraph appears twice? Actually the About Us includes benefits description. Then later there is a separate paragraph about 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 essentially same as earlier. So we can combine. Thus About the role section will include role description + company purpose + benefits description (maybe we can keep benefits separate). But we might still want a Benefits section for clarity. However the benefits description is already in About Us; we could still create Benefits section with that paragraph, but then we would duplicate content. The instruction says preserve ALL substantive information; not duplicate? It didn't forbid duplication but better to avoid. We could put benefits in Benefits section and not repeat in About the role. Then About the role includes role description and company purpose (mission, etc.) but not benefits. Let's split: - About the role: role description paragraph + company purpose/mission paragraph (the first part about inspiring and improving world, etc.) but not the benefits paragraph. - Benefits: the benefits paragraph (starting with "At Sherwin-Williams, part of our mission is to help our employees..."). Check if there is any other benefits info: also earlier "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". That's part of company purpose paragraph. So we can keep that in About the role. Thus About the role will have two paragraphs: role description and company purpose/values. Now Responsibilities: list each sentence as bullet. Let's extract responsibilities sentences: - Collaborate with Data Platform teams to configure the marketplace platform (Databricks and related technologies) - Identify and enforce platform standards around data products, including metadata, trust indicators, and other key attributes - Collaborate with teams involved in integrating marketplace experience, including Enterprise Risk and Resiliency around data access as well as Data Governance around tagging - Engage data end users to understand, document, and deliver desired features for the platform as well as provide feedback to other ED&I teams on desired additional data products. - Partner with Data Literacy and User Enablement teams to suggest activities to remediate current and present user skill and knowledge challenges to leveraging data and insights for data-driven decision-making. - Partner with SMEs and other members of Data Literacy as needed to provide short-term solutions - Leverage industry developments and internal data SMEs to influence the data marketplace roadmap - Foster user communities through recurring user group meetings, online fora, knowledge transfer activities, and other data-democratizing approaches. Also there is a sentence: "This is not a remote position and will report to our Global Headquarters in downtown Cleveland, OH." That's location, not responsibility. Could be placed in About the role maybe. Also: "This position is not eligible for sponsorship for work authorization now or in the future, including conversion to H1-B visa." That's a requirement about work authorization; could be in Qualifications. Also: "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 background check requirement; could be in Qualifications or Requirements. We need to preserve all substantive info. So we need to include work authorization and criminal history review somewhere. Could be under Qualifications (maybe as a note). Or we could create a separate section "Requirements" for such mandatory items. But we have Qualifications heading allowed. We can put those under Qualifications as bullet points. Thus Qualifications will contain: - Education and Experience Required: Bachelor’s degree in Data Science, Statistics, Computer Science, or a related field, or in lieu of related degree, at least 7 years of experience with data analytics responsibilities in either a data-related or business org - 4+ years of experience in a Data Analysis or Data Management role - Proficient in data analysis and statistical tools and techniques or data management - Ability to communicate and collaborate effectively with both technical and non-technical stakeholders - Experience in working with large datasets and performing predictive analysis - Familiarity with learning and development techniques and best practices - BI/Analytics Technologies