Single Family Project Manager / Management Analyst 4
or drop it. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like EEO, legal, navigation, cookie, duplicated lines, application instructions. Also remove "How To Apply", "Contact", etc. Also remove "About Housing Finance Agency" maybe considered boilerplate? It's about agency; maybe keep as part of About the role? The instruction: "Prefer a few substantive sections over many thin ones." We need to decide which sections have content. Let's parse the posting: - Working Title: Single Family Project Manager (not heading) - Job Class: Management Analyst 4 - Agency: Housing Finance Agency - Job ID: 97077 - 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/17/2026 - Closing Date: 09/30/2026 - Division/Unit: SF-Bus Ops Super - Days of Work: Monday - Friday - Travel Required: No - Salary Range: $34.07 - $50.53 / hourly; $71,138 - $105,506 / annually - Classified Status: Classified - Supervisor: Judi Mortenson - Bargaining Unit/Union: 214 - MAPE - FLSA Status: Nonexempt - Designated in Connect 700 Program for Applicants with Disabilities: Yes - Eligibility to Bid: MAPE: ... (some details) - Telework details: candidates residing in Minnesota within 50 miles ... etc. - The work you'll do is more than just a job... (some mission statement) - Minnesota Housing is hiring! We’re a mission-focused financial institution looking for a Single Family Project Manager who will manage and communicate complex business and technical projects to ensure that processes and systems support the Single Family division’s priorities, workplan and the agency’s strategic plan. - Essential Job Duties (list) - Minimum Qualifications (list) - Preferred Qualifications (list) - Our employees are dedicated to ensuring cultural responsiveness. Preferred candidates will have a variety of experiences working effectively with others from different backgrounds and cultures. - Physical Requirements: Requires moving office items such as file folders and small office tools. - Additional Requirements: This position requires successful completion of the following: Reference Checks. Job related background checks. Conflict of Interest Disclosure. - Benefits section: list of benefits. - About Housing Finance Agency: description. - EQUAL OPPORTUNITY EMPLOYERS etc (boilerplate to remove) - Applicants With Disabilities etc (boilerplate to remove) We need to produce sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. Let's map: - About the role: could include mission statement, description of role, agency description. The posting includes: "Minnesota Housing is hiring! We’re a mission-focused financial institution looking for a Single Family Project Manager who will manage and communicate complex business and technical projects to ensure that processes and systems support the Single Family division’s priorities, workplan and the agency’s strategic plan." Also maybe the earlier paragraph about The work you'll do is more than just a job... and agency description. We can combine into About the role. - Responsibilities: Essential Job Duties list. - Requirements: Minimum Qualifications list. - Qualifications: Preferred Qualifications list (maybe also include cultural responsiveness). Could also include Physical Requirements? But Physical Requirements could be under Requirements or separate? The instruction says we can have sections like Requirements, Qualifications, Skills. We need to decide what goes where. We have Minimum Qualifications (mandatory) and Preferred Qualifications (nice-to-have). Also Physical Requirements (moving office items). Additional Requirements (reference checks, background checks, conflict of interest). Could be part of Requirements. Skills: maybe we can extract skills from Minimum Qualifications: skill in eliciting business needs, documenting requirements, translating them into clear project goals, etc. Also strong cross-functional communication and collaboration skills, organizational and time-management skills, cultural competency. Could be a Skills section. But we must not create thin sections. Perhaps combine Skills into Requirements or Qualifications. However the instruction says we can have sections like Requirements, Qualifications, Skills. We need to decide based on content. We have a lot of content for Minimum Qualifications (list of 6 bullet-like items). Preferred Qualifications (list of 4 items). Physical Requirements (one sentence). Additional Requirements (reference checks etc). Benefits (list). Pay (salary range). Schedule (Days of Work: Monday - Friday, Telework Eligible: Yes, details about telework eligibility). So we have Pay and Schedule sections with real content. Thus we can output sections: About the role, Responsibilities, Requirements (maybe combine Minimum Qualifications + Physical Requirements + Additional Requirements?), Qualifications (Preferred Qualifications), Benefits, Pay, Schedule. We could also include Skills but maybe not needed if we incorporate skills into Requirements/Qualifications. However the instruction says "Prefer a few substantive sections over many thin ones." So we could omit Skills section if its content is thin or covered elsewhere. But we have skill details in Minimum Qualifications; we could keep them there. Thus final HTML: sections with
headings and appropriate - for lists,
for prose.
We must not include job title heading. Must not include Job ID etc as headings; we can drop them or put in a short
maybe but better to drop minor metadata. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can drop them entirely.
We must preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep all substantive info from the posting, except boilerplate removed. That includes telework eligibility details, days of work, travel required, etc. Also includes the mission statement paragraphs.
We need to ensure we don't lose any substantive info like "The work you'll do is more than just a job..." etc. That is substantive; we can put in About the role.
Also "At the State of Minnesota, employees play a critical role..." etc. That's also substantive.
Also "Minnesota Housing is hiring! We’re a mission-focused financial institution..." etc.
Also "Our employees are dedicated to ensuring cultural responsiveness. Preferred candidates will have a variety of experiences working effectively with others from different backgrounds and cultures." That's substantive; could be part of Qualifications or About the role.
Physical Requirements: "Requires moving office items such as file folders and small office tools." That's substantive.
Additional Requirements: reference checks, job related background checks, conflict of interest disclosure. Substantive.
Benefits: list.
Pay: salary range.
Schedule: Days of Work: Monday - Friday; Telework Eligible: Yes; plus telework eligibility details (candidates residing in Minnesota within 50 miles ... etc). That's substantive.
We must not include application instructions, contact, How To Apply, etc.
We must not include EEO, equal opportunity, veteran-friendly, etc.
We must not include "Connect 700 Program" details? That is substantive? It mentions eligibility for Connect 700 Program applicants. That is part of the posting but maybe considered metadata? It's about eligibility for a specific program. Could be considered minor metadata but it's about eligibility. The instruction says "fold minor metadata into a short
or drop it." The Connect 700 Program details might be considered minor metadata but it's about eligibility for applicants with disabilities. Might be considered substantive? It's a program detail. However the instruction says to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Connect 700 Program is not exactly boilerplate; it's a specific program. But it's about eligibility for a subset of applicants. Could be considered minor metadata but maybe we keep it as part of About the role or Requirements? However it's not a duty or qualification. It's about application process for a specific group. Might be considered application instruction? It says "To receive consideration as a Connect 700 Program applicant, apply online, email the Job ID#, the Working Title and your valid Proof of Eligibility Certificate by the closing date to Human Resources at MHFA.HR@state.mn.us." That's application instruction for a specific program. So we should remove that as application instruction. So we can drop Connect 700 Program details.
Also "Eligibility to Bid: MAPE: You must be in the same job class as this posting, but within a different work unit and must be a permanent classified employee, and not on probation." That's also about eligibility for bidding (internal). Might be considered metadata but could be considered substantive? It's about who may apply (internal). The posting already says "Who May Apply: Open to all qualified job seekers". That's generic. The MAPE eligibility is more specific. Might be considered metadata but we could drop it as it's about internal bidding. However it's substantive info about eligibility. The instruction says to preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it unless it's considered boilerplate. It's not boilerplate; it's a specific eligibility rule. So we should keep it. Where to put? Could be part of About the role or Requirements? It's about eligibility, not duties. Could be a short
under About the role or maybe a separate section? But we only have predefined sections; we could put it in About the role as a note.
Similarly "Telework is available per the State of Minnesota policy." and the detailed telework eligibility details are substantive; we can put under Schedule.
Now we need to ensure we don't repeat any info.
Let's extract substantive content sections:
**About the role** (prose):
- 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.
- Minnesota Housing is hiring! We’re a mission-focused financial institution looking for a Single Family Project Manager who will manage and communicate complex business and technical projects to ensure that processes and systems support the Single Family division’s priorities, workplan and the agency’s strategic plan.
- Our employees are dedicated to ensuring cultural responsiveness. Preferred candidates will have a variety of experiences working effectively with others from different backgrounds and cultures.
- At Minnesota Housing, we know that affordable housing is an essential part of Minnesota’s infrastructure. When you work here, you’re helping to build stronger communities. We have a national reputation as one of the finest housing finance agencies in the country. Working together to improve the state we love. What do Minnesota's State employees have in common? A sense of purpose in their work, Connection with their coworkers and communities, Opportunities for personal and professional growth.
That's a lot of prose from the "About Housing Finance Agency" section. We can include that.
**Responsibilities** (list):
- Manage and deploy prioritized Single Family projects to ensure that processes and systems support the division workplan and agency strategic plan.
- Lead Single Family efforts for Agency-wide projects so the needs of the Single Family division are met.
- Research and analyze new project opportunities and shepherd from concept through implementation.
- Lead Single Family project portfolio, manage resource allocations and collaborate with IT.
- Establish and implement project management standards within the division to ensure all staff are aware of participation expectations and responsibilities as projects are started and deployed.
-
for prose. We must not include job title heading. Must not include Job ID etc as headings; we can drop them or put in a short
maybe but better to drop minor metadata. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can drop them entirely. We must preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep all substantive info from the posting, except boilerplate removed. That includes telework eligibility details, days of work, travel required, etc. Also includes the mission statement paragraphs. We need to ensure we don't lose any substantive info like "The work you'll do is more than just a job..." etc. That is substantive; we can put in About the role. Also "At the State of Minnesota, employees play a critical role..." etc. That's also substantive. Also "Minnesota Housing is hiring! We’re a mission-focused financial institution..." etc. Also "Our employees are dedicated to ensuring cultural responsiveness. Preferred candidates will have a variety of experiences working effectively with others from different backgrounds and cultures." That's substantive; could be part of Qualifications or About the role. Physical Requirements: "Requires moving office items such as file folders and small office tools." That's substantive. Additional Requirements: reference checks, job related background checks, conflict of interest disclosure. Substantive. Benefits: list. Pay: salary range. Schedule: Days of Work: Monday - Friday; Telework Eligible: Yes; plus telework eligibility details (candidates residing in Minnesota within 50 miles ... etc). That's substantive. We must not include application instructions, contact, How To Apply, etc. We must not include EEO, equal opportunity, veteran-friendly, etc. We must not include "Connect 700 Program" details? That is substantive? It mentions eligibility for Connect 700 Program applicants. That is part of the posting but maybe considered metadata? It's about eligibility for a specific program. Could be considered minor metadata but it's about eligibility. The instruction says "fold minor metadata into a short
or drop it." The Connect 700 Program details might be considered minor metadata but it's about eligibility for applicants with disabilities. Might be considered substantive? It's a program detail. However the instruction says to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Connect 700 Program is not exactly boilerplate; it's a specific program. But it's about eligibility for a subset of applicants. Could be considered minor metadata but maybe we keep it as part of About the role or Requirements? However it's not a duty or qualification. It's about application process for a specific group. Might be considered application instruction? It says "To receive consideration as a Connect 700 Program applicant, apply online, email the Job ID#, the Working Title and your valid Proof of Eligibility Certificate by the closing date to Human Resources at MHFA.HR@state.mn.us." That's application instruction for a specific program. So we should remove that as application instruction. So we can drop Connect 700 Program details. Also "Eligibility to Bid: MAPE: You must be in the same job class as this posting, but within a different work unit and must be a permanent classified employee, and not on probation." That's also about eligibility for bidding (internal). Might be considered metadata but could be considered substantive? It's about who may apply (internal). The posting already says "Who May Apply: Open to all qualified job seekers". That's generic. The MAPE eligibility is more specific. Might be considered metadata but we could drop it as it's about internal bidding. However it's substantive info about eligibility. The instruction says to preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it unless it's considered boilerplate. It's not boilerplate; it's a specific eligibility rule. So we should keep it. Where to put? Could be part of About the role or Requirements? It's about eligibility, not duties. Could be a short
under About the role or maybe a separate section? But we only have predefined sections; we could put it in About the role as a note. Similarly "Telework is available per the State of Minnesota policy." and the detailed telework eligibility details are substantive; we can put under Schedule. Now we need to ensure we don't repeat any info. Let's extract substantive content sections: **About the role** (prose): - 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. - Minnesota Housing is hiring! We’re a mission-focused financial institution looking for a Single Family Project Manager who will manage and communicate complex business and technical projects to ensure that processes and systems support the Single Family division’s priorities, workplan and the agency’s strategic plan. - Our employees are dedicated to ensuring cultural responsiveness. Preferred candidates will have a variety of experiences working effectively with others from different backgrounds and cultures. - At Minnesota Housing, we know that affordable housing is an essential part of Minnesota’s infrastructure. When you work here, you’re helping to build stronger communities. We have a national reputation as one of the finest housing finance agencies in the country. Working together to improve the state we love. What do Minnesota's State employees have in common? A sense of purpose in their work, Connection with their coworkers and communities, Opportunities for personal and professional growth. That's a lot of prose from the "About Housing Finance Agency" section. We can include that. **Responsibilities** (list): - Manage and deploy prioritized Single Family projects to ensure that processes and systems support the division workplan and agency strategic plan. - Lead Single Family efforts for Agency-wide projects so the needs of the Single Family division are met. - Research and analyze new project opportunities and shepherd from concept through implementation. - Lead Single Family project portfolio, manage resource allocations and collaborate with IT. - Establish and implement project management standards within the division to ensure all staff are aware of participation expectations and responsibilities as projects are started and deployed. -