Hearing Representative – Division of Adjudications
NYC Department of Housing Preservation & Development · New York, NY · 1 mo ago
OTHRFull-time
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 if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, EEO, etc. Keep substantive info.
We need to parse the posting: It includes "About The Agency", "Your Team", "Your Impact", "Your Role", "Responsibilities" (list), "Preferred Skills", "Minimum Qualifications", "Additional Information" (some EEO, remote work note, etc). Also "Public Service Loan Forgiveness", "Residency Requirement". Those are extra info but maybe not needed as sections? The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include sections like About the Agency (maybe as About the role? but they said use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. "About The Agency" could be "About the role"? Actually "About the role" is generic; but we have agency description. Could use "About the role" to describe the role/agency. Or we could create "About the Agency" but they said use headings e.g. About the role, Responsibilities, etc. Likely they expect those exact headings. So we should use those headings only if we have content. Let's see what we have:
- About the role: we have description of agency, team, impact, role. Could combine into About the role section.
- Responsibilities: we have a list of responsibilities under "Your Responsibilities". Good.
- Requirements: we have Minimum Qualifications (education/experience). Also maybe "Preferred Skills" could be Skills section. Requirements could be minimum qualifications.
- Qualifications: maybe same as Requirements? But they differentiate Requirements and Qualifications. Could treat Requirements as minimum qualifications, Qualifications as preferred? Or we could put Minimum Qualifications under Requirements, and Preferred Skills under Skills. Qualifications maybe left out if not distinct. But we could put "Qualifications" heading for any additional qualifications like remote work eligibility? Not sure.
- Skills: we have Preferred Skills list.
- Benefits: we have remote work note (up to two days per week), Public Service Loan Forgiveness, Residency Requirement maybe not benefits. Could treat remote work as benefit. Also maybe loan forgiveness as benefit. But we need actual content: "Note: This position is eligible for remote work up to two days per week, pursuant to the Remote Work Pilot Program agreed to between the City and DC37." Also "Public Service Loan Forgiveness As a prospective employee..." That's a benefit. Also maybe "Residency Requirement" is not a benefit but a requirement. Could be under Requirements? Might be better to include under Requirements? But they said only include sections if posting has real specific content. We have remote work and loan forgiveness specifics. So we can create Benefits section with those points.
- Pay: no salary info. So omit Pay section.
- Schedule: no schedule info besides remote work days? Not explicit schedule. Could omit.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications? Actually we have Minimum Qualifications (requirements) and Preferred Skills (skills). Could also have Qualifications maybe for any additional qualifications like "Public Service Loan Forgiveness"? Not exactly. Might be better to have Requirements (minimum qualifications) and Skills (preferred skills). Qualifications maybe omitted.
But the instruction list includes Qualifications as a possible heading. We could put "Qualifications" for Minimum Qualifications? But they'd be duplicate. Let's decide: Use Requirements for minimum qualifications, Qualifications for any additional qualifications like "Public Service Loan Forgiveness"? Not really. Maybe we can put "Qualifications" for Minimum Qualifications and "Skills" for Preferred Skills. But then we have both Requirements and Qualifications with similar content. Might be confusing but acceptable if we differentiate: Requirements = Minimum Qualifications; Qualifications = Additional qualifications like loan forgiveness? Not ideal.
Better: Use Requirements for Minimum Qualifications, Skills for Preferred Skills, and omit Qualifications. The instruction says "use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, EEO, etc. Keep substantive info.
We need to parse the posting: It includes "About The Agency", "Your Team", "Your Impact", "Your Role", "Responsibilities" (list), "Preferred Skills", "Minimum Qualifications", "Additional Information" (some EEO, remote work note, etc). Also "Public Service Loan Forgiveness", "Residency Requirement". Those are extra info but maybe not needed as sections? The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include sections like About the Agency (maybe as About the role? but they said use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. "About The Agency" could be "About the role"? Actually "About the role" is generic; but we have agency description. Could use "About the role" to describe the role/agency. Or we could create "About the Agency" but they said use headings e.g. About the role, Responsibilities, etc. Likely they expect those exact headings. So we should use those headings only if we have content. Let's see what we have:
- About the role: we have description of agency, team, impact, role. Could combine into About the role section.
- Responsibilities: we have a list of responsibilities under "Your Responsibilities". Good.
- Requirements: we have Minimum Qualifications (education/experience). Also maybe "Preferred Skills" could be Skills section. Requirements could be minimum qualifications.
- Qualifications: maybe same as Requirements? But they differentiate Requirements and Qualifications. Could treat Requirements as minimum qualifications, Qualifications as preferred? Or we could put Minimum Qualifications under Requirements, and Preferred Skills under Skills. Qualifications maybe left out if not distinct. But we could put "Qualifications" heading for any additional qualifications like remote work eligibility? Not sure.
- Skills: we have Preferred Skills list.
- Benefits: we have remote work note (up to two days per week), Public Service Loan Forgiveness, Residency Requirement maybe not benefits. Could treat remote work as benefit. Also maybe loan forgiveness as benefit. But we need actual content: "Note: This position is eligible for remote work up to two days per week, pursuant to the Remote Work Pilot Program agreed to between the City and DC37." Also "Public Service Loan Forgiveness As a prospective employee..." That's a benefit. Also maybe "Residency Requirement" is not a benefit but a requirement. Could be under Requirements? Might be better to include under Requirements? But they said only include sections if posting has real specific content. We have remote work and loan forgiveness specifics. So we can create Benefits section with those points.
- Pay: no salary info. So omit Pay section.
- Schedule: no schedule info besides remote work days? Not explicit schedule. Could omit.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications? Actually we have Minimum Qualifications (requirements) and Preferred Skills (skills). Could also have Qualifications maybe for any additional qualifications like "Public Service Loan Forgiveness"? Not exactly. Might be better to have Requirements (minimum qualifications) and Skills (preferred skills). Qualifications maybe omitted.
But the instruction list includes Qualifications as a possible heading. We could put "Qualifications" for Minimum Qualifications? But they'd be duplicate. Let's decide: Use Requirements for minimum qualifications, Qualifications for any additional qualifications like "Public Service Loan Forgiveness"? Not really. Maybe we can put "Qualifications" for Minimum Qualifications and "Skills" for Preferred Skills. But then we have both Requirements and Qualifications with similar content. Might be confusing but acceptable if we differentiate: Requirements = Minimum Qualifications; Qualifications = Additional qualifications like loan forgiveness? Not ideal.
Better: Use Requirements for Minimum Qualifications, Skills for Preferred Skills, and omit Qualifications. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not mandatory to use all. So we can omit Qualifications if no distinct content.
Thus final HTML:
About the role
About the role
... combine agency description, team, impact, role.
Responsibilities
- list items from responsibilities.
Requirements
Minimum qualifications: baccalaureate degree + 2 years community work OR high school + 6 years community work OR equivalent; plus at least one year of experience as described.
Skills
- list preferred skills.
Benefits
- remote work up to two days per week; eligibility for Public Service Loan Forgiveness programs; maybe note residency requirement? Not benefit.
We should also include maybe "Public Service Loan Forgiveness" as benefit.
We need to preserve all substantive information; not invent or summarize away detail. So we need to keep details like the list of programs, etc. In About the role we need to include agency overview, team, impact, role description. Must not lose specifics.
Let's craft About the role paragraph(s) summarizing but preserving details. However we must not summarize away detail; we need to preserve ALL substantive information. That means we cannot omit details like program names, numbers, etc. But we can rephrase as prose while preserving all facts. That's okay.
We need to include details: Agency oversees housing standards across 3.7 million homes, largest municipal housing agency, building/preserving affordable housing, protecting tenants, etc. Under Commissioner Dina Levy and Mamdani Administration, pursuing ambitious housing agenda. Tools: standards enforcement, tenant resources, creation of new affordable housing. Mission: making NYC more affordable for renters/homeowners.
Your Team: Community Coordinator as Hearing Representative in Division of Adjudications within Office of Compliance & Risk Management. Division consists of Appeals and Mitchell-Lama Hearings Units. Office of Housing Access and Stability (HAS) consists of divisions: Housing Opportunity, Tenant and Owner Resources, Housing Stability, Budget and Program Operations, Program Policy and Innovation. Mission: ensure fair, efficient, transparent access to affordable housing. Provides subsidies, placement services, tools connecting New Yorkers to affordable housing, ensures vulnerable households in subsidized housing have support. Housing Access committed to expanding housing choices, affirmatively furthering fair housing, stabilizing financial health of buildings. Division of Tenant and Owner Resources (DTOR) within HAS administers rental subsidy programs serving over 45,000 households and 9,000 landlords. Programs: HCV, PBV, Moderate Rehab Section 8, Moderate Rehab SRO, CoC/SPC, NYC 15/15, HAVP, City HAP, HOME TBRA. Largest program: federal Section 8 HCV program, provides funding to eligible low-income families for rental assistance toward decent, safe, affordable housing in neighborhood of choice. Families pay ~30% income toward rent, HPD pays difference directly to owner. Unit must have rent determined reasonable and affordable by HPD and meet federal HQS to be approved. Section 8 rent subsidy program funded/monitored by HUD is primary rental subsidy program administered by HPD. Appeals Unit conducts federally mandated informal hearings/reviews for Section 8 and other HPD administered rental subsidy program participants/applicants to appeal decisions made by HAS regarding participation/application. Mitchell-Lama Hearings Unit tries and settles cases from managing agents of housing complexes governed by Mitchell-Lama rules, helps ensure building owners/managing agents uphold obligations. Division of Housing Supervision within HPD’s Office of Asset & Property Management oversees Mitchell-Lama program (~45,000 units providing affordable rental/cooperative homeownership to moderate/middle income families).
Your Impact: As Hearing Representative for Division, you will bolster effective workflow and communications for Appeals Unit, prepare documents/exhibits for informal hearings/reviews concerning terminations/denials of assistance, requests for reasonable accommodations, other petitions from rent subsidy programs. Part of talented team of hearing reps, attorneys, admin support providing critical legal services to Agency as it executes affordable housing responsibilities.
Your Role: Under Deputy Director and Director’s supervision, selected candidate’s responsibilities will include representing HPD at informal hearings/reviews held at HPD’s Appeals unit.
We need to include all that in About the role section (maybe multiple paragraphs). That's a lot but okay.
Then Responsibilities list: we need to extract each bullet from "Your Responsibilities". Let's list them:
- Handling appeals from receipt to completion, including working with appellants and the various agency units, appellants and representatives to request and review all relevant documents.
- Taking timely steps to pre-resolve appeals or assign appeals independently as needed.
- Reviewing casefiles and determining potential procedural and mailing issues, proper standing and timeliness of cases.
- Alerting supervisors of lateness for untimely cases or requesting supporting documentation, making income and other calculations as needed.
- Independently reviewing case files for relevant evidence pertaining to HPD's actions and creating a timeline of events to clearly demonstrate the facts and events leading to HPD's decision, assessing the decision and its compliance with rules, policies and HPD’s Administrative Plan.
- Ensuring timely preparation of cases for hearing/review and presenting exhibits and arguing in support of the agency's decision or action at the informal hearings/reviews and explaining those steps and documents in a clear fashion at informal hearings/reviews.
- Working with Unit staff to ensure cases are calendared, scheduled and entered correctly in the Appeal Tracking Database.
- Working with staff to ensure correct and timely mailing of correspondence and decisions.
- Responding to inquiries from participants/applicants and their representatives, agency staff and the general public via phone and written correspondence.
- Reviewing, entering and/or updating information related to the appellants’ cases in the Appeals Tracking Database and other programs and databases such as Elite, Outlook and Expertly.
- Presenting cases to the Appeals Unit as needed for internal discussions and to HAS for review and discussion.
- Sending pre-resolve or reinstatement e-mails to senior staff within HAS for cases that may be able to be resolved without a hearing or review.
- Responding to inquiries that are received via mail, fax, or e-mail from staff within HAS as well as external parties such as attorneys, POA, case workers, etc.
- Serving as a liaison between the Program, the Appeals Unit and other relevant internal or external parties on hearing logistics and relevant issues.
- Independently managing own caseload and assignment of cases to other team members as needed.
- Assisting with training and mock hearings/second seating of current and incoming Appeals staff if needed or due to staff shortages.
- Making recommendations to supervisors and leadership on ways to improve Appeals unit functions and case management.
- Working on special projects, as needed, which may working on initiatives that result from Agency or Division priorities and strategic plans.
We need to preserve all; ensure no typos.
Now Requirements: Minimum Qualifications text: "A baccalaureate degree from an accredited college and two years of experience in community work or community centered activities in an area related to the duties described above; or High school graduation or equivalent and six years of experience in community work or community centered activities in an area related to the duties as described above; or Education and/or experience which is equivalent to "1" or "2" above. However, all candidates must have at least one year of experience as described in "1" above."
We need to keep that exactly.
Skills: Preferred Skills list:
- Strong communication and interpersonal skills; ability to convey data analysis or other complex concepts to colleagues with a variety of skillsets, strengths, and perspectives
- Ability to multi-task with high volume workload
- Data enthusiast with a passion for