Senior Product Manager / Product Management Specialist

We need to output HTML fragment with headings for sections that have real specific content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Do not include Job ID etc as headings; can fold minor metadata into short

or drop. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "How To Apply", "Contact", etc. Also remove "About Human Services Dept" maybe? That's about agency, but could be considered "About the role"? Actually "About Human Services Dept" is agency description; could be part of "About the role"? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create sections that match content. We have content: Working Title etc metadata (Job Class, Agency, Job ID, Location, Telework Eligible, Full/Part Time, Regular/Temporary, Who May Apply, Date Posted, Closing Date, Hiring Agency/Seniority Unit, Division/Unit, Work Shift/Work Hours, Days of Work, Travel Required, Salary Range, Classified Status, Bargaining Unit/Union, FLSA Status, Designated in Connect 700 Program). This is metadata; we can fold into a short

maybe under a heading like "About the role" or maybe we just include a paragraph with these details. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a

with that metadata. Then we have a paragraph about the work: "The Department of Human Services (DHS) is unable to provide sponsorship..." etc. That's boilerplate about visa sponsorship, eligibility, etc. Might be considered legal boilerplate; we should remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The visa sponsorship line maybe legal; but it's substantive? It says "The Department of Human Services (DHS) is unable to provide sponsorship for work visas. Applicants must be eligible to work in the United States at the start of employment. DHS does not participate in E-Verify." This is likely boilerplate but maybe we keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is legal/EEO? It's about work authorization; could be considered legal. Might be removed. However, we need to preserve ALL substantive information; not sure if that is substantive. Probably it's boilerplate; we can drop. Then: "The work you'll do is more than just a job..." That's generic motivational text; could be considered boilerplate? Might be considered fluff but maybe we keep as part of About the role? It's not specific duties. Might be considered filler. The instruction: Prefer a few substantive sections over many thin ones. We could include a short paragraph under About the role summarizing role purpose. Then telework eligibility details: "This position is eligible for telework for applicants who reside in Minnesota or in a bordering state, with supervisory approval and satisfactory performance. If you live in a state bordering Minnesota, you must live within 50 miles or less from the primary work location to be eligible for telework. There is a required in office meeting once a month." That's substantive about schedule/telework; could go under Schedule or maybe a separate section but we only have Schedule heading allowed. So we can put that under Schedule. Then responsibilities paragraph: "The Senior Product Manager directs a product’s strategic vision and roadmap, and oversees the budget, evolution, and lifecycle of one or more products...." That's substantive; we can put under Responsibilities (maybe also include bullet list after "Responsibilities include but are not limited to:"). Then bullet list of responsibilities. Then Minimum Qualifications heading: we can use Requirements or Qualifications. The instruction includes Requirements and Qualifications as possible headings. We have Minimum Qualifications and Preferred Qualifications. Could combine into Requirements (minimum) and Qualifications (preferred) or Skills. We'll decide: Use

Requirements

for minimum qualifications, and

Qualifications

for preferred qualifications. Or we could use Skills for preferred qualifications. But we have both. Then Additional Requirements: background investigation etc. That's also a requirement; could be under Requirements as well. Then Benefits: list of benefits under Benefits heading. Then Pay: we have salary range; we can put under Pay heading. Then Schedule: we have work shift/hours, days of work, telework details; we can put under Schedule heading. We must not include sections with filler like "commensurate with experience". We have actual salary range, so Pay section is valid. We must not include sections like "About the role" if we don't have specific content; but we have some description about role purpose; we can include. We must not include duplicated lines. We must output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

Metadata paragraph: include Working Title, Job Class, Agency, Location, Telework Eligible, Full/Part Time, Regular/Temporary, Who May Apply, Date Posted, Closing Date, Hiring Agency/Seniority Unit, Division/Unit, Work Shift/Work Hours, Days of Work, Travel Required, Salary Range, Classified Status, Bargaining Unit/Union, FLSA Status, Designated in Connect 700 Program.

Then

About the role

with paragraph(s) describing role purpose: maybe combine the motivational paragraph and the description of what Senior Product Manager does (the first sentence after that). Actually we have a paragraph: "The work you'll do is more than just a job..." then "The Senior Product Manager directs a product’s strategic vision..." That's substantive about role. We'll put that under About the role. Then

Responsibilities

with

• list from "Responsibilities include but are not limited to:" plus maybe also include the preceding sentences about directing product etc? But those are also responsibilities; we can include them as part of the list or as preceding paragraph. To avoid duplication, we can include the list only; but we need to preserve all substantive information. The preceding sentences are also substantive; we could include them as a paragraph before the list. That's fine. Then

  Requirements

  for Minimum Qualifications and Additional Requirements (background investigation). We'll combine. Then

  Qualifications

  for Preferred Qualifications. Then

  Benefits

  with list. Then

  Pay

  with paragraph stating salary range. Then

  Schedule

  with paragraph about work shift, days, telework eligibility, in-office meeting. We must not include sections like "About Human Services Dept" (agency description) maybe we can drop as it's boilerplate? It's somewhat substantive about agency but not role-specific. Might be considered filler; but we could include under About the role? The instruction says prefer few substantive sections over many thin ones. The agency description is not about the role; maybe we drop it. We must remove EEO boilerplate etc. Now craft HTML. Be careful to escape any special characters? Not needed. Let's write. Metadata paragraph: We'll include as a single

  with semicolons. Example:

  Working Title: Senior Product Manager; Job Class: Product Management Specialist; Agency: Human Services Dept; Location: St. Paul; Telework Eligible: Yes; Full/Part Time: Full-Time; Regular/Temporary: Unlimited; Who May Apply: Open to all qualified job seekers; Date Posted: 09/24/2026; Closing Date: 09/30/2026; Hiring Agency/Seniority Unit: Human Services Dept / MAPE DHS Central Office; Division/Unit: Department of Human Services (DHS) / Office of Inspector General (OIG)-DSA Product Mgmt Unit; Work Shift/Work Hours: Day Shift / 8:00 a.m. - 4:30 p.m.; Days of Work: Monday - Friday; Travel Required: No; Salary Range: $37.91 - $56.39 / hourly; $79,156 - $117,742 / annually; Classified Status: Classified; Bargaining Unit/Union: 214 - MN Assoc of Professional Empl/MAPE; FLSA Status: Exempt - Administrative; Designated in Connect 700 Program for Applicants with Disabilities: Yes

  Now About the role: combine the motivational paragraph and the role description. Paragraph: "The work you'll do is more than just a job. At the State of Minnesota, employees play a critical role in developing policies, providing essential services, and working to improve the well-being and quality of life for all Minnesotans. The State of Minnesota is committed to equity and inclusion, and invests in employees by providing benefits, support resources, and training and development opportunities. This position is eligible for telework for applicants who reside in Minnesota or in a bordering state, with supervisory approval and satisfactory performance. If you live in a state bordering Minnesota, you must live within 50 miles or less from the primary work location to be eligible for telework. There is a required in office meeting once a month. The Senior Product Manager directs a product’s strategic vision and roadmap, and oversees the budget, evolution, and lifecycle of one or more products. The Senior Product Manager works to address the needs of the people we serve in alignment with the Department of Human Services (DHS) mission and vision, DHS Equity Policy, and DHS strategic plan in coordination with product leadership. Managing the end-to-end product development lifecycle, the Senior Product Manager ensures high-quality, timely delivery that aligns with product line objectives and guiding principles — while championing a consistent, intuitive user experience. Success in this role depends on building strong stakeholder relationships, fostering collaboration, and rallying support across the organization for the product's direction. The ideal Senior Product Manager models a collaborative, innovative working style — encouraging cross-functional teamwork, knowledge sharing, and continuous learning rooted in product management best practices." But note we already included telework details in metadata? Actually we included telework eligibility in metadata; but we also have telework details in this paragraph. Might duplicate. We could keep telework details only in Schedule section; but we have them also in About the role. To avoid duplication, we could remove telework details from About the role and keep them in Schedule. However the instruction says preserve ALL substantive information; we can't discard. But we can include them in both places? That would be duplication. Better to keep them in Schedule and not repeat in About the role. So we should edit About the role paragraph to exclude telework details (since they'll be in Schedule). Also we should exclude the sentence about "This position is eligible for telework..." etc. So About the role will contain the motivational and role description minus telework. Thus About the role paragraph: "The work you'll do is more than just a job. At the State of Minnesota, employees play a critical role in developing policies, providing essential services, and working to improve the well-being and quality of life for all Minnesotans. The State of Minnesota is committed to equity and inclusion, and invests in employees by providing benefits, support resources, and training and development opportunities. The Senior Product Manager directs a product’s strategic vision and roadmap, and oversees the budget, evolution, and lifecycle of one or more products. The Senior Product Manager works to address the needs of the people we serve in alignment with