Director of Survey Operations
headings for each section used. We must not repeat job title as heading. So no heading like "Director III". Use generic headings. We must not put Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. So we can drop posting number, closing date, etc. Maybe include location in a
under About the role? 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 location, date maybe in a short paragraph. We must preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep all details from the posting, but we can reorganize into sections. Must not omit substantive info like specific duties, KSAs, requirements, benefits, pay, schedule, etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes some like "Review our Tips for Success when applying for jobs at DFPS, DSHS and HHSC." That's application instruction; remove. Also "Active Duty, Military, Reservists, Guardsmen, And Veterans ..." maybe not boilerplate but could be considered encouragement; but it's substantive? It's about encouraging veterans; maybe keep? It's not boilerplate but it's a statement encouraging certain groups; could be considered EEO? Might be considered EEO/equal-opportunity boilerplate. Safer to remove? The instruction says remove EEO/equal-opportunity boilerplate. So remove that paragraph. Also "ADA Accommodations" is likely boilerplate; remove. "Pre-Employment Checks And Work Eligibility" maybe substantive? It includes background checks, E-Verify, I-9, telework disclaimer. Some of that is substantive (background checks). But it's also somewhat boilerplate. However, the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Pre-employment checks might be considered legal boilerplate. Might be safer to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So legal boilerplate includes pre-employment checks? Possibly yes. But we need to preserve ALL substantive information. The background check requirement is substantive. However, it's also legal. The instruction may intend to remove standard legal disclaimers like EEO, but keep specifics like background check? Hard to know. I'd keep the background check details as they are substantive to the job. But the "Pre-Employment Checks And Work Eligibility" heading itself might be considered legal boilerplate; we could fold the content into a
under Requirements or Additional Information. Similarly "Telework Disclaimer" maybe legal; but we already have telework eligibility. We'll try to keep substantive details: background check requirements, fingerprint, SEMARC, NAR, LNFA, conflict of interest disclosure, etc. Those are important. We'll also keep "Additional Information Must be able to work hours other than 8 AM to 5 PM, Monday through Friday, as necessary. Requires some weekend, early morning, late evening, and overnight travel. May be required to be on call." That's schedule. We'll keep "The interview process for this position may include a written exercise." That's application instruction? Might be considered application instruction; maybe remove. But it's substantive about selection process. The instruction says remove application instructions. So remove that line. We'll keep "All applicants must pass a fingerprint criminal background check and the SEMARC (Search Engine for Background Checks) check. Additional checks as applicable may include the NAR (Nurse Aide Registry) and LNFA (Licensed Nursing Facility Administrator) check." Keep. We'll keep "If you are offered and accept the position, you will not be permitted to continue employment at any HHSC regulated facilities or providers. You will be required to disclose any potential conflicts of interest, secondary employment, volunteer activities, and friends/family who own, operate, or work at regulated providers." Keep. We'll keep "If you are an active or former licensed nursing facility administrator, certified nurse aide, or medication aide, hiring will be pending until professional licensing and Employee Misconduct Registry checks are completed." Keep. We'll keep "Review our Tips for Success when applying for jobs at DFPS, DSHS and HHSC." Remove as application instruction. We'll keep "Active Duty, Military, Reservists, Guardsmen, And Veterans ..." maybe remove as EEO encouragement. We'll keep "ADA Accommodations" remove. We'll keep "Pre-Employment Checks And Work Eligibility" maybe fold content. We'll keep "Telework Disclaimer" maybe fold. We'll keep "Nearest Major Market: Houston" maybe location. Now structure sections: - About the role: short paragraph summarizing purpose: joining HHSC, role as Director of Survey Operations, location, etc. Could include date, location, agency, department. - Responsibilities: list of duties from the description and Essential Job Functions. Use
- . - Requirements: education and experience criteria from Initial Screening Criteria and Registrations, Licensure Requirements Or Certifications. Could combine. - Qualifications: maybe KSAs? But KSAs are knowledge, skills, abilities. Could be Skills section. The instruction says we have sections: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. We have KSAs (knowledge, skills, abilities). Could split: Knowledge -> Requirements? Skills -> Skills section? Abilities -> Qualifications? Or we could treat KSAs as Skills. But we have separate Skills section; we could put the skill items there. Qualifications could be education/experience. Requirements could be licensure/certifications? Hmm. Better: Use Requirements for mandatory education/experience/licensure. Use Qualifications for preferred or additional qualifications? But we don't have separate preferred. Could use Qualifications for KSAs (knowledge, skills, abilities). Then Skills for maybe specific skill items? But KSAs already include skills and abilities. Might be redundant. We could follow typical job posting: Requirements = education/experience; Qualifications = knowledge, skills, abilities; Skills = maybe specific skills like problem solving, etc. But we have limited time. Given instruction: "Prefer a few substantive sections over many thin ones." So we might combine some. We could have sections: About the role, Responsibilities, Requirements (education/experience/licensure), Qualifications (KSAs), Benefits, Pay, Schedule. That's 6 sections. Skills maybe omitted if covered in Qualifications. But we have a Skills heading in the list; we could still include Skills if we have specific skill items. The KSAs list includes both knowledge and skills and abilities. We could split: Knowledge and maybe some abilities under Qualifications, skills under Skills. But that may be thin. Better to follow the instruction: include a section ONLY when the posting has real, specific content for it. So if we have content for Skills, we include; if not, we skip. We have explicit skill items: "Skill in identifying problems, evaluating alternatives and implementing solutions." etc. So we have skills content. So we can include Skills section. Qualifications could be knowledge items? Or we could treat KSAs as Qualifications (knowledge) and Skills as skills. Abilities maybe also under Qualifications? Hmm. Let's parse KSAs list: Knowledge of relevant state and federal laws, regulations, policies, rules and requirements involving the regulation of long-term care facilities, agencies, and individuals Knowledge of the Texas legislative process. Knowledge of quality assurance and quality improvement principles, techniques and activities. Knowledge of LTCR policies, processes, State performance measures, and survey process. Knowledge of strategic planning, budget management, human resource management and project management. Knowledge of principles of leadership and how to effectively interact with various leadership styles. Skill in identifying problems, evaluating alternatives and implementing solutions. Skill in managing multiple and competing priorities. Skill in working collaboratively and cooperatively with diverse groups. Ability to plan, organize and implement complex systems to assure quality and consistency of regulatory activities throughout the state. Ability to effectively communicate complex information to a variety of individuals or groups. Ability to develop creative and innovative solutions. Ability to interpret and apply federal and state laws, regulations, policies, rules and requirements in health and human services. Ability to conduct formal presentations. Ability to interpret and use data for goal and strategic development. Thus we have Knowledge, Skill, Ability. We could make Qualifications = Knowledge (maybe plus some abilities). Skills = Skill items. Abilities maybe also under Qualifications? But we have no separate Abilities heading. Could put abilities under Qualifications as well. Simplify