The MLC Matching Support Temp

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. Need to parse posting. Content: - Intro: "Are you interested in joining a purpose-driven company in the music industry? Do you thrive in a collaborative, hybrid work environment? If you do, we would like to get to know you." This is like an intro paragraph. - "WORKING AT THE MLC" paragraph: description of culture. - "Who We Are": description of MLC. - "THE ROLE": description of temporary contract, duration, etc. - "QUALIFICATIONS": list of qualifications. - "FOCUS AREAS": list of duties. - "YOU WILL CHAMPION THE MLC’S CULTURE BY:" repeated twice with similar content. - Then EEO boilerplate to remove. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we drop the EEO paragraph. Also duplicate "YOU WILL CHAMPION THE MLC’S CULTURE BY:" appears twice; we need to deduplicate? The instruction: remove duplicated lines. So we should keep only one instance. We need to preserve all substantive information. We need to decide sections. Potential sections: - About the role (maybe combine intro and working at MLC and who we are? But "About the role" heading is for role description. Could use "About the role" for the role description (THE ROLE). Could also have "About the company" but not required heading list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which sections have content. We have: - Role description: THE ROLE (temporary contract, duration, expectations, hybrid, location, hours, continuing education). That's substantive. - Responsibilities: FOCUS AREAS (list of duties). That's responsibilities. - Requirements/Qualifications: QUALIFICATIONS list. - Skills: maybe not explicit separate; but qualifications include music knowledge, Excel, etc. Could treat as Skills. - Benefits: mention "continuing education opportunities through free webinars and hands-on training." That's a benefit. Also maybe hybrid work environment? Not exactly benefit but could be. - Pay: not specified. No pay info. So we should NOT create Pay section. - Schedule: mention "expected to work up to 37.5 hours per week, with occasional additional hours or overtime based on business needs, which may include weekends." That's schedule info. So we can create Schedule section. - About the role: we could include intro paragraphs about company culture and who we are as "About the role" or maybe "About the company". But we have heading "About the role" allowed. Could put the introductory paragraphs there. We must not repeat job title as heading (the page already shows it). So we don't add a heading for the job title. We need to output only HTML fragment, no /. Use

for section headings. Use

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

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: EEO paragraph, duplicated lines (the duplicate YOU WILL CHAMPION...). Also maybe remove repeated "YOU WILL CHAMPION THE MLC’S CULTURE BY:" lines; keep one. Also remove any application instructions (none present). Also remove any cookie/navigation/legal etc. Now craft sections. Let's extract prose: Intro: "Are you interested in joining a purpose-driven company in the music industry? Do you thrive in a collaborative, hybrid work environment? If you do, we would like to get to know you." Working at the MLC: "The MLC is committed to excellence, service and transparency. Our culture is collaborative, and our team works in a hybrid environment. On our team, you are respected, valued for your unique strengths and experiences, and empowered to identify and resolve your own challenges." Who We Are: "The Mechanical Licensing Collective (The MLC) is a nonprofit organization established under the Music Modernization Act of 2018 to help ensure songwriters, composers, and music publishers receive the mechanical royalties they’re owed from digital music services. Operating at the intersection of music, technology, and finance, The MLC manages a sophisticated data platform that connects music, ownership, and royalty data at scale. Through technology, data, and industry collaboration, we work to accurately match musical works to rightsholders, distribute royalties, and bring greater transparency to the digital music ecosystem." We could combine these into an "About the role" or maybe "About the company". Since we have heading "About the role", we could put the role-specific info there, but the intro and who we are are more about company. However we could still put them under About the role as they describe the role context. It's okay. Alternatively we could not have About the role section and instead have separate sections: Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. But we need to use headings only when there is real specific content. We have content for Responsibilities (FOCUS AREAS), Requirements/Qualifications (QUALIFICATIONS), Skills (maybe overlapping), Benefits (continuing education), Schedule (hours). We could also have About the role (THE ROLE). That seems appropriate. Thus sections: - About the role: includes THE ROLE description (temporary contract, duration, hybrid, location, hours, continuing education). Also maybe include the intro paragraphs? But we can keep them separate as part of About the role. Better to put the intro and who we are under About the role as well? Might be redundant but okay. But we must not invent or summarize away detail; we can keep them as is. Let's decide to have:

  About the role

  Are you interested in joining a purpose-driven company in the music industry? Do you thrive in a collaborative, hybrid work environment? If you do, we would like to get to know you.

  The MLC is committed to excellence, service and transparency. Our culture is collaborative, and our team works in a hybrid environment. On our team, you are respected, valued for your unique strengths and experiences, and empowered to identify and resolve your own challenges.

  The Mechanical Licensing Collective (The MLC) is a nonprofit organization established under the Music Modernization Act of 2018 to help ensure songwriters, composers, and music publishers receive the mechanical royalties they’re owed from digital music services. Operating at the intersection of music, technology, and finance, The MLC manages a sophisticated data platform that connects music, ownership, and royalty data at scale. Through technology, data, and industry collaboration, we work to accurately match musical works to rightsholders, distribute royalties, and bring greater transparency to the digital music ecosystem.

  This is a temporary contract position with an anticipated duration of approximately 4–5 months, with the possibility of long-term extension. If you’re a data geek, music nerd, and technophile, this could be a great opportunity for you. As a Matching Support Temp, you’ll combine an in-depth knowledge of music with a strong affinity for data, technology, and systems. Whether your expertise runs from Acid Rock to Zydeco—or anywhere in between—your music knowledge will help you research, analyze, and connect music data accurately. Both music knowledge and comfort working with data are essential to success in this role. This position is expected to work up to 37.5 hours per week, with occasional additional hours or overtime based on business needs, which may include weekends. You’ll also have access to continuing education opportunities through free webinars and hands-on training. This is a Hybrid position, we are based in Nashville.

  But note we duplicated some content: The last paragraph includes hours and continuing education etc. We might split. Better to keep THE ROLE paragraph as is, and then maybe separate Benefits and Schedule sections. But we must not duplicate content. Let's extract THE ROLE block exactly: "The Role This is a temporary contract position with an anticipated duration of approximately 4–5 months, with the possibility of long-term extension. If you’re a data geek, music nerd, and technophile, this could be a great opportunity for you. As a Matching Support Temp, you’ll combine an in-depth knowledge of music with a strong affinity for data, technology, and systems. Whether your expertise runs from Acid Rock to Zydeco-or anywhere in between-your music knowledge will help you research, analyze, and connect music data accurately. Both music knowledge and comfort working with data are essential to success in this role. This position is expected to work up to 37.5 hours per week, with occasional additional hours or overtime based on business needs, which may include weekends. You’ll also have access to continuing education opportunities through free webinars and hands-on training. This is a Hybrid position, we are based in Nashville." We need to preserve that exactly (maybe fix hyphens). We'll keep as is. Now Responsibilities: FOCUS AREAS list. Extract: "Match sound recording data to musical works data through a combination of cross-referencing available data points and performing outside research;Extensively investigate source data for accurate matching;Perform various data entry and clean-up tasks;Review and confirm the work of peers, as needed;Communicate issues to supervisors and other team members;Collaborate with team members and supervisors to develop and improve matching and research strategies;Continually update and improve work processes based on results of prior work and newly-received data;andMeet productivity standards for throughput;Quickly align your work with new procedures.The Focus Areas may inevitably evolve and change over time to meet changing business needs." We need to split into list items separated by semicolons. We'll create
  • for each. Now Qualifications: list: "Music knowledge of one or more genres requiredProven experience working independently with a high level of dependabilityProficiency in using Excel and/or data (Prior business class, analytics course, certification, hands-on usage)Experience handling a high volume of data with sharp attention to detail is preferredExperience with computer focused work for long periods of time preferredMust have access to a computer and high-speed internet service" We need to split into items. Probably each sentence separated by missing punctuation. We'll split at capital letters? Better to just keep as a single paragraph? But rule: Use
    • for any list of duties/requirements/benefits. So we should make list. We can split by looking for capital letters after a lowercase? Might be messy. Simpler: treat each line as separate item based on the original formatting (they were likely separate lines). We'll approximate: - Music knowledge of one or more genres required - Proven experience working independently with a high level of dependability - Proficiency in using Excel and/or data (Prior business class, analytics course, certification, hands-on usage) - Experience handling a high volume of data with sharp attention to detail is preferred - Experience with computer focused work for long periods of time preferred - Must have access to a computer and high-speed internet service We'll output as
      • each. Now Benefits: we have "You’ll also have access to continuing education opportunities through free webinars and hands-on training." That's a benefit. Could also mention hybrid work environment? But that's more about role. We'll make Benefits section with that sentence. Schedule: we have "This position is expected to work up to 37.5 hours per week, with occasional additional hours or overtime based on business needs, which may include weekends." That's schedule. We could also include that it's hybrid and based in Nashville under About the role. Now we need to avoid duplicate sections: we have About the role (including intro, who we are, THE ROLE). Responsibilities (FOCUS AREAS). Requirements (maybe Qualifications). Skills (maybe not needed). Benefits. Schedule. We could combine Requirements and Qualifications as