Cultural Liaison - Hmong
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists,
for prose
- Don't repeat job title as heading
- Don't put Job ID/requisition as headings
- Fold minor metadata into short
or drop
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/scam-warning, duplicated lines, application instructions)
- Include section ONLY when real specific content exists
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer few substantive sections over many thin ones
- Output ONLY HTML fragment, no html/body, no markdown fences
Let me map the content:
1. Salary/Schedule/Benefits info: "Non Affiliated Exempt Position Expected Hiring Salary: .6FTE - Approx. $33,000.00 and Benefits Eligible Working Schedule: 204 days" - This is substantive pay/schedule/benefits info. Should I create a Pay section? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. But also "Prefer a few substantive sections over many thin ones." Could fold into a short
under a general section or create a Pay/Schedule section. Since it's specific, I'll include a Pay section with that info.
2. General Definition of Work: This is prose about the role. Could be "About the role" section.
3. Essential Functions / Program Responsibilities: This is a list of duties. Should be "Responsibilities" section with
- .
4. Knowledge, Skills And Abilities: This is a list of skills/abilities. Could be "Skills" or "Requirements" section. The rule mentions "Requirements, Qualifications, Skills" as possible headings. This seems like a mix of knowledge, skills, abilities. I'll use "Skills" or "Requirements". Since it's labeled "Knowledge, Skills And Abilities", maybe "Skills" heading.
5. Education And Experience: This is qualifications. Could be "Qualifications" section.
6. Physical Requirements: This is a list of physical demands. Could be "Requirements" or separate. Might fold into Qualifications or separate. Since it's specific, maybe include as "Physical Requirements" but the allowed headings are limited: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Physical Requirements" not in list. Could put under "Requirements" or "Qualifications". I'll include as part of Qualifications or separate? The rule says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only those headings. I should map to those. Physical Requirements could go under "Requirements" or "Qualifications". I'll put under "Requirements" maybe.
But the rule says "include a section ONLY when the posting has real, specific content for it". So I need to decide which of those standard headings apply.
Let's list standard headings from example: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
I'll create:
- About the role (for General Definition)
- Responsibilities (for Essential Functions/Program Responsibilities)
- Qualifications (for Education And Experience)
- Skills (for Knowledge, Skills And Abilities)
- Pay (for salary info)
- Schedule (for working schedule 204 days)
- Benefits (for benefits eligible)
But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. However, "Prefer a few substantive sections over many thin ones." The Pay, Schedule, Benefits are thin (just one line each). Could combine into one "Pay & Schedule" or fold into a short
in About the role. But the rule says use those headings when they have content. I think I'll include Pay and Schedule as separate sections because they are specific. Benefits is just "Benefits Eligible" - maybe include in Pay section.
Alternatively, I could create a "Compensation" section but not in allowed list. The allowed list includes Pay, Schedule, Benefits. I'll use them.
But the user said "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So those are the allowed headings. I should only use those.
Thus, I'll create:
- About the role
- Responsibilities
- Qualifications (for Education and Experience)
- Skills (for Knowledge, Skills and Abilities)
- Requirements (for Physical Requirements? But Physical Requirements is not exactly requirements. Could be under Qualifications. But there is a "Requirements" heading. Might use Requirements for Physical Requirements. However, the Knowledge, Skills and Abilities is more like Skills. The Education and Experience is Qualifications. Physical Requirements could be Requirements.
But the rule says "never emit a heading followed by filler/placeholder text". So if I create Requirements, I need real content. Physical Requirements is real content.
Let's structure:
About the role
General Definition of Work: Performs work supporting Hmong-speaking and other AAPI students, families and staff in the White Bear Lake Area School District. The positions will assist in the communication between Hmong-speaking and other AAPI parents and school staff including translating for various meetings as needed. In addition, this position will assist in the enrollment process for families in need of additional support and connecting with students at various sites.
Responsibilities
- Execute under the direction of the Director of Equity and Engagement.
- Work with enrollment, building leadership, and multilingual department staff in the development of programming that directly impacts the learning experience and academic success of Hmong and other AAPI children in WBLAS.
- Responsible for helping the district identify Hmong and other AAPI students within the system, facilitate cultural and linguistic integration, and support district enrollment and retention efforts.
- Partner with principals and school staff to develop a positive, inclusive building climate that leads to educational equity, strong home-school partnerships, and elevated student achievement for all Hmong and other AAPI students.
- Facilitate student empowerment, social, racial, academic, and cultural identity development groups (e.g., AAPI student affinity groups, youth leadership circles, and peer mentoring).
- Offer guidance and collaboration to district staff to provide supplemental, culturally relevant, and linguistically responsive experiential learning opportunities inside and outside the classroom.
- Implement the goals and objectives of the Achievement and Integration Plan and the District Strategic Plan as they relate to Hmong and other AAPI students and families.
- Coordinate and collaborate with district leadership, community partners, and the AAPI Parent Advisory Committee (or family advisory groups) to support, advocate for, and execute targeted engagement and education initiatives.
- Help create system-wide educational, family engagement, and community-building experiences that celebrate Hmong and other AAPI history, language, and heritage while fostering belonging across the district.
Qualifications
Bachelor's degree, or equivalent combination of education and experience.
Skills
- Some knowledge of district policies, manuals, programs, processes and procedures
- Some knowledge of standard office practices, procedures and equipment
- Some knowledge of business English, spelling and arithmetic
- Knowledge of native cultures and traditions
- Some knowledge of federal program rules, policies, and procedures
- Ability to build strong community partnerships
- Some skill operating standard office equipment, personal computer and applicable hardware and software
- Some skill performing data entry on web-based forms
- Ability to compute rates, ratios and percentages
- Ability to make arithmetic computations using whole numbers, fractions and decimals
- Ability to create and maintain files, records, reports and databases in a timely and effective manner both electronically and on paper
- Ability to change and influence school climate and culture
- Ability to facilitate groups and peer meetings
- Ability to communicate effectively both orally and in written formats
- Ability to establish and maintain effective working relationships with officials, teachers, employees, students, similar professionals, and the general public
Requirements
- Occasional exertion of up to 10 pounds of force
- Frequently sitting, occasionally standing, walking, using hands to finger, handle or feel, reaching with hands and arms, lifting and repetitive motions
- Standard vision requirements
- Vocal communication required for expressing or exchanging ideas by means of the spoken word
- Hearing required to perceive information at normal spoken word levels
- Preparing and analyzing written or computer data, operating machines and observing general surroundings and activities
- No exposure to environmental conditions
- Generally in a moderately noisy location (e.g., business office, light traffic)
Pay
Non-affiliated exempt position; .6 FTE at approximately $33,000.00 per year.
Schedule
204-day work schedule.
Benefits
Benefits eligible.
But note: The original says "Non Affiliated Exempt Position Expected Hiring Salary: .6FTE - Approx. $33,000.00 and Benefits Eligible Working Schedule: 204 days". That's one line. I split into Pay, Schedule, Benefits. That's okay.
Now, check for any duplicate or boilerplate: Application Procedure, EEO, website, email - remove.
Also, the job title is not given? The user didn't provide a title. The posting starts with "Non Affiliated Exempt Position Expected Hiring Salary...". No explicit title. But the rule says "Do NOT repeat the job title as a heading (the page already shows it)". Since we don't have a title, we don't need to worry.
Now, ensure we preserve ALL substantive information. The Knowledge, Skills and Abilities list has some duplicates (ability to compute rates, ratios and percentages appears twice; ability to make arithmetic computations appears twice). I'll keep as is but maybe deduplicate? The rule says preserve ALL substantive information; do NOT invent or summarize away detail. So keep duplicates? Probably keep as in original. But it's a list, duplicates might be okay. I'll include each bullet as separate? The original text: "ability to compute rates, ratios and percentages; ability to make arithmetic computations using whole numbers, fractions and decimals; ability to create and maintain files, records, reports and databases in a timely and effective manner both electronically and on paper; ability to make arithmetic computations using whole numbers, fractions and decimals; ability to compute rates, ratios
for prose - Don't repeat job title as heading - Don't put Job ID/requisition as headings - Fold minor metadata into short
or drop - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning, duplicated lines, application instructions) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment, no html/body, no markdown fences Let me map the content: 1. Salary/Schedule/Benefits info: "Non Affiliated Exempt Position Expected Hiring Salary: .6FTE - Approx. $33,000.00 and Benefits Eligible Working Schedule: 204 days" - This is substantive pay/schedule/benefits info. Should I create a Pay section? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. But also "Prefer a few substantive sections over many thin ones." Could fold into a short
under a general section or create a Pay/Schedule section. Since it's specific, I'll include a Pay section with that info. 2. General Definition of Work: This is prose about the role. Could be "About the role" section. 3. Essential Functions / Program Responsibilities: This is a list of duties. Should be "Responsibilities" section with
- .
4. Knowledge, Skills And Abilities: This is a list of skills/abilities. Could be "Skills" or "Requirements" section. The rule mentions "Requirements, Qualifications, Skills" as possible headings. This seems like a mix of knowledge, skills, abilities. I'll use "Skills" or "Requirements". Since it's labeled "Knowledge, Skills And Abilities", maybe "Skills" heading.
5. Education And Experience: This is qualifications. Could be "Qualifications" section.
6. Physical Requirements: This is a list of physical demands. Could be "Requirements" or separate. Might fold into Qualifications or separate. Since it's specific, maybe include as "Physical Requirements" but the allowed headings are limited: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Physical Requirements" not in list. Could put under "Requirements" or "Qualifications". I'll include as part of Qualifications or separate? The rule says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only those headings. I should map to those. Physical Requirements could go under "Requirements" or "Qualifications". I'll put under "Requirements" maybe. But the rule says "include a section ONLY when the posting has real, specific content for it". So I need to decide which of those standard headings apply. Let's list standard headings from example: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I'll create: - About the role (for General Definition) - Responsibilities (for Essential Functions/Program Responsibilities) - Qualifications (for Education And Experience) - Skills (for Knowledge, Skills And Abilities) - Pay (for salary info) - Schedule (for working schedule 204 days) - Benefits (for benefits eligible) But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. However, "Prefer a few substantive sections over many thin ones." The Pay, Schedule, Benefits are thin (just one line each). Could combine into one "Pay & Schedule" or fold into a short
in About the role. But the rule says use those headings when they have content. I think I'll include Pay and Schedule as separate sections because they are specific. Benefits is just "Benefits Eligible" - maybe include in Pay section. Alternatively, I could create a "Compensation" section but not in allowed list. The allowed list includes Pay, Schedule, Benefits. I'll use them. But the user said "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So those are the allowed headings. I should only use those. Thus, I'll create: - About the role - Responsibilities - Qualifications (for Education and Experience) - Skills (for Knowledge, Skills and Abilities) - Requirements (for Physical Requirements? But Physical Requirements is not exactly requirements. Could be under Qualifications. But there is a "Requirements" heading. Might use Requirements for Physical Requirements. However, the Knowledge, Skills and Abilities is more like Skills. The Education and Experience is Qualifications. Physical Requirements could be Requirements. But the rule says "never emit a heading followed by filler/placeholder text". So if I create Requirements, I need real content. Physical Requirements is real content. Let's structure:
About the role
General Definition of Work: Performs work supporting Hmong-speaking and other AAPI students, families and staff in the White Bear Lake Area School District. The positions will assist in the communication between Hmong-speaking and other AAPI parents and school staff including translating for various meetings as needed. In addition, this position will assist in the enrollment process for families in need of additional support and connecting with students at various sites.
Responsibilities
- Execute under the direction of the Director of Equity and Engagement.
- Work with enrollment, building leadership, and multilingual department staff in the development of programming that directly impacts the learning experience and academic success of Hmong and other AAPI children in WBLAS.
- Responsible for helping the district identify Hmong and other AAPI students within the system, facilitate cultural and linguistic integration, and support district enrollment and retention efforts.
- Partner with principals and school staff to develop a positive, inclusive building climate that leads to educational equity, strong home-school partnerships, and elevated student achievement for all Hmong and other AAPI students.
- Facilitate student empowerment, social, racial, academic, and cultural identity development groups (e.g., AAPI student affinity groups, youth leadership circles, and peer mentoring).
- Offer guidance and collaboration to district staff to provide supplemental, culturally relevant, and linguistically responsive experiential learning opportunities inside and outside the classroom.
- Implement the goals and objectives of the Achievement and Integration Plan and the District Strategic Plan as they relate to Hmong and other AAPI students and families.
- Coordinate and collaborate with district leadership, community partners, and the AAPI Parent Advisory Committee (or family advisory groups) to support, advocate for, and execute targeted engagement and education initiatives.
- Help create system-wide educational, family engagement, and community-building experiences that celebrate Hmong and other AAPI history, language, and heritage while fostering belonging across the district.
Qualifications
Bachelor's degree, or equivalent combination of education and experience.
Skills
- Some knowledge of district policies, manuals, programs, processes and procedures
- Some knowledge of standard office practices, procedures and equipment
- Some knowledge of business English, spelling and arithmetic
- Knowledge of native cultures and traditions
- Some knowledge of federal program rules, policies, and procedures
- Ability to build strong community partnerships
- Some skill operating standard office equipment, personal computer and applicable hardware and software
- Some skill performing data entry on web-based forms
- Ability to compute rates, ratios and percentages
- Ability to make arithmetic computations using whole numbers, fractions and decimals
- Ability to create and maintain files, records, reports and databases in a timely and effective manner both electronically and on paper
- Ability to change and influence school climate and culture
- Ability to facilitate groups and peer meetings
- Ability to communicate effectively both orally and in written formats
- Ability to establish and maintain effective working relationships with officials, teachers, employees, students, similar professionals, and the general public
Requirements
- Occasional exertion of up to 10 pounds of force
- Frequently sitting, occasionally standing, walking, using hands to finger, handle or feel, reaching with hands and arms, lifting and repetitive motions
- Standard vision requirements
- Vocal communication required for expressing or exchanging ideas by means of the spoken word
- Hearing required to perceive information at normal spoken word levels
- Preparing and analyzing written or computer data, operating machines and observing general surroundings and activities
- No exposure to environmental conditions
- Generally in a moderately noisy location (e.g., business office, light traffic)
Pay
Non-affiliated exempt position; .6 FTE at approximately $33,000.00 per year.
Schedule
204-day work schedule.
Benefits
Benefits eligible.
But note: The original says "Non Affiliated Exempt Position Expected Hiring Salary: .6FTE - Approx. $33,000.00 and Benefits Eligible Working Schedule: 204 days". That's one line. I split into Pay, Schedule, Benefits. That's okay. Now, check for any duplicate or boilerplate: Application Procedure, EEO, website, email - remove. Also, the job title is not given? The user didn't provide a title. The posting starts with "Non Affiliated Exempt Position Expected Hiring Salary...". No explicit title. But the rule says "Do NOT repeat the job title as a heading (the page already shows it)". Since we don't have a title, we don't need to worry. Now, ensure we preserve ALL substantive information. The Knowledge, Skills and Abilities list has some duplicates (ability to compute rates, ratios and percentages appears twice; ability to make arithmetic computations appears twice). I'll keep as is but maybe deduplicate? The rule says preserve ALL substantive information; do NOT invent or summarize away detail. So keep duplicates? Probably keep as in original. But it's a list, duplicates might be okay. I'll include each bullet as separate? The original text: "ability to compute rates, ratios and percentages; ability to make arithmetic computations using whole numbers, fractions and decimals; ability to create and maintain files, records, reports and databases in a timely and effective manner both electronically and on paper; ability to make arithmetic computations using whole numbers, fractions and decimals; ability to compute rates, ratios