Program Manager 2 - College of Education
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. The posting includes description (responsibilities), additional posting info (more responsibilities), experience, education, MQ (minimum qualifications). No explicit benefits, pay, schedule. Salary says "Commensurate with Experience/Education" which is not specific; we should NOT create Pay section because it's not specific (commensurate with experience/education is placeholder). So we omit Pay, Benefits, Schedule.
We need sections: About the role (maybe a brief summary), Responsibilities (list), Requirements (maybe experience/education), Qualifications (maybe MQ), Skills (maybe not explicit). We need to preserve all substantive info. Let's parse.
Posting:
Department: Dean, Education
Salary: Commensurate with Experience/Education
Description: Manages the day-to-day operations of a large university program or department, including the supervision of staff employees, student workers, programs or processes. Plans and develops procedures for administering a large or complex department or program. Manages fiscal activities, including procurement and budget analysis. Provides guidance to subordinate staff and evaluates performance. Prepares abstracts, research reports, funding proposals, operations and procedure manuals, and other written material and documentation. Creates and reviews reports of expenditures and activities. May administer grants and grant-related related communications, scholarships and other operations. Develops, implements and maintains appropriate policies and procedures. May serve as property custodian for the department. Performs other job-related duties as assigned.
Additional Posting Information: Process and manage contract agreements and associated invoice payments, ensuring compliance with institutional policies and contractual requirements. Process Procurement Card (P-Card) purchases and maintain accurate documentation and reconciliation records. Coordinate and process gift card purchases for both human subjects and non-human subjects research studies in accordance with applicable regulations and procedures. Verify and review monthly financial reconciliations for faculty grant cost centers to ensure accuracy and compliance with university financial guidelines. Oversee budgets, procurement activities, and financial analysis. Use Pivot database to identify funding opportunities for faculty. Review faculty grant applications for readability. Serve as backup for pre-award research administrator, including reviewing funders’ requests for applications to ensure eligibility and understand requirements, developing grant budgets, compiling all components of grant applications, submitting grants on behalf of the University, and ensuring adherence to applicable internal and federal regulations. Prepare research reports, abstracts, funding proposals, operational documents, and other written materials. Administer grants and grant-related communications when applicable. Develop, implement, and maintain policies and procedures that support program goals and compliance requirements.
Experience Will Be Considered In Lieu Of Education. Education will be considered in lieu of experience.
MQ: Education: Requires a thorough understanding of both theoretical and practical aspects of an analytical, technical or professional discipline; or the basic knowledge of more than one professional discipline. Knowledge of the discipline is normally obtained through a formal, directly job-related 4 year degree from a college or university or an equivalent in-depth specialized training program that is directly related to the type of work being performed. Experience: Requires a minimum of one (1) year of directly job-related experience. Certification/Licensing: None.
All positions at the University of Houston-System are security sensitive and will require a criminal history check. The University of Houston System and its universities are Equal Opportunity Institutions. Everyone is encouraged to apply.
We need to remove boilerplate: EEO, equal-opportunity, security sensitive, criminal history check, etc. Also remove duplicated lines? There's some duplication maybe.
We need to output HTML fragment only.
We need headings for sections we include.
Potential sections:
- About the role: maybe a brief summary from description? Could combine description into About the role? But we also need Responsibilities section. The description already lists responsibilities. Could treat "About the role" as a short paragraph summarizing the role (maybe first sentence). But we must not invent content. We can use the description as responsibilities. The instructions: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. 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.
Thus we need to decide which sections to include. The posting has description (responsibilities), additional posting info (more responsibilities), experience/education/MQ (qualifications). No explicit skills list. Could we infer skills from responsibilities? Better not to invent. So we may omit Skills section if no explicit list.
We could have:
About the role
Manages the day-to-day operations of a large university program or department, including supervision of staff, student workers, programs or processes; plans and develops procedures; manages fiscal activities; provides guidance and evaluates performance; prepares reports, proposals, manuals; administers grants; develops policies; may serve as property custodian.
But that is essentially summarizing description; we risk summarizing away detail? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Summarizing may be okay if we keep all details? But summarizing may lose detail. Better to keep the responsibilities as a list (- ) under Responsibilities section. Then About the role could be a short prose that is not required but we could include a brief overview from the first sentence? However that may be considered summarizing. The instruction says "Prefer a few substantive sections over many thin ones." So maybe we just have one section Responsibilities with all duties listed, and another section Requirements/Qualifications for education/experience. About the role may be thin if we just have a short sentence; maybe we can omit About the role if we don't have specific content beyond responsibilities. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we should not create About the role if we don't have specific content beyond what we already put in Responsibilities. However we could put a brief overview that is directly from the posting content: maybe the first sentence of description: "Manages the day-to-day operations of a large university program or department, including the supervision of staff employees, student workers, programs or processes." That is specific content. So we could have About the role as a
with that sentence. Then Responsibilities as a
with the rest of duties (including additional posting info). That would preserve all detail.
Let's extract duties:
From Description:
- Manages the day-to-day operations of a large university program or department, including the supervision of staff employees, student workers, programs or processes.
- Plans and develops procedures for administering a large or complex department or program.
- Manages fiscal activities, including procurement and budget analysis.
- Provides guidance to subordinate staff and evaluates performance.
- Prepares abstracts, research reports, funding proposals, operations and procedure manuals, and other written material and documentation.
- Creates and reviews reports of expenditures and activities.
- May administer grants and grant-related related communications, scholarships and other operations.
- Develops, implements and maintains appropriate policies and procedures.
- May serve as property custodian for the department.
- Performs other job-related duties as assigned.
From Additional Posting Information:
- Process and manage contract agreements and associated invoice payments, ensuring compliance with institutional policies and contractual requirements.
- Process Procurement Card (P-Card) purchases and maintain accurate documentation and reconciliation records.
- Coordinate and process gift card purchases for both human subjects and non-human subjects research studies in accordance with applicable regulations and procedures.
- Verify and review monthly financial reconciliations for faculty grant cost centers to ensure accuracy and compliance with university financial guidelines.
- Oversee budgets, procurement activities, and financial analysis.
- Use Pivot database to identify funding opportunities for faculty.
- Review faculty grant applications for readability.
- Serve as backup for pre-award research administrator, including reviewing funders’ requests for applications to ensure eligibility and understand requirements, developing grant budgets, compiling all components of grant applications, submitting grants on behalf of the University, and ensuring adherence to applicable internal and federal regulations.
- Prepare research reports, abstracts, funding proposals, operational documents, and other written materials.
- Administer grants and grant-related communications when applicable.
- Develop, implement, and maintain policies and procedures that support program goals and compliance requirements.
Note some duplicates: "Prepare research reports, abstracts, funding proposals, operational documents, and other written materials." similar to earlier "Prepares abstracts, research reports, funding proposals, operations and procedure manuals, and other written material and documentation." and "Develops, implements and maintains appropriate policies and procedures." similar to later "Develop, implement, and maintain policies and procedures that support program goals and compliance requirements." We should preserve all but we can deduplicate? The instruction: "Remove duplicated lines". So we should eliminate duplicate sentences. Let's identify duplicates:
- Prepares abstracts, research reports, funding proposals, operations and procedure manuals, and other written material and documentation.
- Prepare research reports, abstracts, funding proposals, operational documents, and other written materials.
These are similar but not identical; one mentions operations and procedure manuals, the other operational documents. Could be considered distinct but overlapping. Might keep both? The instruction says remove duplicated lines. If they are not exact duplicates, we keep both. However we could combine? Safer to keep both as they are not exact duplicates.
- Develops, implements and maintains appropriate policies and procedures.
- Develop, implement, and maintain policies and procedures that support program goals and compliance requirements.
Again similar but not exact; one says appropriate policies and procedures, the other says policies and procedures that support program goals and compliance requirements. Keep both.
Now Responsibilities list will be long. We'll output as - items.
Now Requirements/Qualifications: We have MQ: Education, Experience, Certification/Licensing: None. Also "Experience Will Be Considered In Lieu Of Education. Education will be considered in lieu of experience." That's a statement about substitution. We'll include that as part of Requirements.
We could have a section Requirements (or Qualifications). The instruction lists both Requirements and Qualifications as possible headings. We need to decide which to use. The posting has MQ (minimum qualifications) which includes Education and Experience. So we could use Qualifications for MQ, and Requirements for the experience/education substitution statement? Or combine. Better to have one section Qualifications with the MQ details, and maybe another section Requirements for the substitution statement? But that may be thin. Let's think: The substitution statement is about experience/education equivalence; it's a requirement/qualification nuance. Could be included under Qualifications as a note.
Thus we can have a single section Qualifications (or Requirements) containing:
- Education: Requires a thorough understanding of both theoretical and practical aspects of an analytical, technical or professional discipline; or the basic knowledge of more than one professional discipline. Knowledge of the discipline is normally obtained through a formal, directly job-related 4 year degree from a college or university or an equivalent in-depth specialized training program that is directly related to the type of work being performed.
- Experience: Requires a minimum of one (1) year of directly job-related experience.
- Certification/Licensing: None.
- Experience will be considered in lieu of education. Education will be considered in lieu of experience.
We could also note that all positions are security sensitive etc but we remove boilerplate.
Now we need to decide about Benefits, Pay, Schedule: Not present, so omit.
Now About the role: we could use first sentence of description as a short paragraph. That is specific content. Let's do that.
Thus final HTML:
About the role
Manages the day-to-day operations of a large university program or department, including the supervision of staff employees, student workers, programs or processes.
Responsibilities
- Plans and develops procedures for administering a large or complex department or program.
- Manages fiscal activities, including
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. 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.
Thus we need to decide which sections to include. The posting has description (responsibilities), additional posting info (more responsibilities), experience/education/MQ (qualifications). No explicit skills list. Could we infer skills from responsibilities? Better not to invent. So we may omit Skills section if no explicit list.
We could have:
About the role
Manages the day-to-day operations of a large university program or department, including supervision of staff, student workers, programs or processes; plans and develops procedures; manages fiscal activities; provides guidance and evaluates performance; prepares reports, proposals, manuals; administers grants; develops policies; may serve as property custodian.
But that is essentially summarizing description; we risk summarizing away detail? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Summarizing may be okay if we keep all details? But summarizing may lose detail. Better to keep the responsibilities as a list (- ) under Responsibilities section. Then About the role could be a short prose that is not required but we could include a brief overview from the first sentence? However that may be considered summarizing. The instruction says "Prefer a few substantive sections over many thin ones." So maybe we just have one section Responsibilities with all duties listed, and another section Requirements/Qualifications for education/experience. About the role may be thin if we just have a short sentence; maybe we can omit About the role if we don't have specific content beyond responsibilities. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we should not create About the role if we don't have specific content beyond what we already put in Responsibilities. However we could put a brief overview that is directly from the posting content: maybe the first sentence of description: "Manages the day-to-day operations of a large university program or department, including the supervision of staff employees, student workers, programs or processes." That is specific content. So we could have About the role as a
with that sentence. Then Responsibilities as a
with the rest of duties (including additional posting info). That would preserve all detail.
Let's extract duties:
From Description:
- Manages the day-to-day operations of a large university program or department, including the supervision of staff employees, student workers, programs or processes.
- Plans and develops procedures for administering a large or complex department or program.
- Manages fiscal activities, including procurement and budget analysis.
- Provides guidance to subordinate staff and evaluates performance.
- Prepares abstracts, research reports, funding proposals, operations and procedure manuals, and other written material and documentation.
- Creates and reviews reports of expenditures and activities.
- May administer grants and grant-related related communications, scholarships and other operations.
- Develops, implements and maintains appropriate policies and procedures.
- May serve as property custodian for the department.
- Performs other job-related duties as assigned.
From Additional Posting Information:
- Process and manage contract agreements and associated invoice payments, ensuring compliance with institutional policies and contractual requirements.
- Process Procurement Card (P-Card) purchases and maintain accurate documentation and reconciliation records.
- Coordinate and process gift card purchases for both human subjects and non-human subjects research studies in accordance with applicable regulations and procedures.
- Verify and review monthly financial reconciliations for faculty grant cost centers to ensure accuracy and compliance with university financial guidelines.
- Oversee budgets, procurement activities, and financial analysis.
- Use Pivot database to identify funding opportunities for faculty.
- Review faculty grant applications for readability.
- Serve as backup for pre-award research administrator, including reviewing funders’ requests for applications to ensure eligibility and understand requirements, developing grant budgets, compiling all components of grant applications, submitting grants on behalf of the University, and ensuring adherence to applicable internal and federal regulations.
- Prepare research reports, abstracts, funding proposals, operational documents, and other written materials.
- Administer grants and grant-related communications when applicable.
- Develop, implement, and maintain policies and procedures that support program goals and compliance requirements.
Note some duplicates: "Prepare research reports, abstracts, funding proposals, operational documents, and other written materials." similar to earlier "Prepares abstracts, research reports, funding proposals, operations and procedure manuals, and other written material and documentation." and "Develops, implements and maintains appropriate policies and procedures." similar to later "Develop, implement, and maintain policies and procedures that support program goals and compliance requirements." We should preserve all but we can deduplicate? The instruction: "Remove duplicated lines". So we should eliminate duplicate sentences. Let's identify duplicates:
- Prepares abstracts, research reports, funding proposals, operations and procedure manuals, and other written material and documentation.
- Prepare research reports, abstracts, funding proposals, operational documents, and other written materials.
These are similar but not identical; one mentions operations and procedure manuals, the other operational documents. Could be considered distinct but overlapping. Might keep both? The instruction says remove duplicated lines. If they are not exact duplicates, we keep both. However we could combine? Safer to keep both as they are not exact duplicates.
- Develops, implements and maintains appropriate policies and procedures.
- Develop, implement, and maintain policies and procedures that support program goals and compliance requirements.
Again similar but not exact; one says appropriate policies and procedures, the other says policies and procedures that support program goals and compliance requirements. Keep both.
Now Responsibilities list will be long. We'll output as - items.
Now Requirements/Qualifications: We have MQ: Education, Experience, Certification/Licensing: None. Also "Experience Will Be Considered In Lieu Of Education. Education will be considered in lieu of experience." That's a statement about substitution. We'll include that as part of Requirements.
We could have a section Requirements (or Qualifications). The instruction lists both Requirements and Qualifications as possible headings. We need to decide which to use. The posting has MQ (minimum qualifications) which includes Education and Experience. So we could use Qualifications for MQ, and Requirements for the experience/education substitution statement? Or combine. Better to have one section Qualifications with the MQ details, and maybe another section Requirements for the substitution statement? But that may be thin. Let's think: The substitution statement is about experience/education equivalence; it's a requirement/qualification nuance. Could be included under Qualifications as a note.
Thus we can have a single section Qualifications (or Requirements) containing:
- Education: Requires a thorough understanding of both theoretical and practical aspects of an analytical, technical or professional discipline; or the basic knowledge of more than one professional discipline. Knowledge of the discipline is normally obtained through a formal, directly job-related 4 year degree from a college or university or an equivalent in-depth specialized training program that is directly related to the type of work being performed.
- Experience: Requires a minimum of one (1) year of directly job-related experience.
- Certification/Licensing: None.
- Experience will be considered in lieu of education. Education will be considered in lieu of experience.
We could also note that all positions are security sensitive etc but we remove boilerplate.
Now we need to decide about Benefits, Pay, Schedule: Not present, so omit.
Now About the role: we could use first sentence of description as a short paragraph. That is specific content. Let's do that.
Thus final HTML:
About the role
Manages the day-to-day operations of a large university program or department, including the supervision of staff employees, student workers, programs or processes.
Responsibilities
- Plans and develops procedures for administering a large or complex department or program.
- Manages fiscal activities, including
for prose. 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. Thus we need to decide which sections to include. The posting has description (responsibilities), additional posting info (more responsibilities), experience/education/MQ (qualifications). No explicit skills list. Could we infer skills from responsibilities? Better not to invent. So we may omit Skills section if no explicit list. We could have:
About the role
Manages the day-to-day operations of a large university program or department, including supervision of staff, student workers, programs or processes; plans and develops procedures; manages fiscal activities; provides guidance and evaluates performance; prepares reports, proposals, manuals; administers grants; develops policies; may serve as property custodian.
But that is essentially summarizing description; we risk summarizing away detail? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Summarizing may be okay if we keep all details? But summarizing may lose detail. Better to keep the responsibilities as a list (- ) under Responsibilities section. Then About the role could be a short prose that is not required but we could include a brief overview from the first sentence? However that may be considered summarizing. The instruction says "Prefer a few substantive sections over many thin ones." So maybe we just have one section Responsibilities with all duties listed, and another section Requirements/Qualifications for education/experience. About the role may be thin if we just have a short sentence; maybe we can omit About the role if we don't have specific content beyond responsibilities. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we should not create About the role if we don't have specific content beyond what we already put in Responsibilities. However we could put a brief overview that is directly from the posting content: maybe the first sentence of description: "Manages the day-to-day operations of a large university program or department, including the supervision of staff employees, student workers, programs or processes." That is specific content. So we could have About the role as a
with that sentence. Then Responsibilities as a
- with the rest of duties (including additional posting info). That would preserve all detail.
Let's extract duties:
From Description:
- Manages the day-to-day operations of a large university program or department, including the supervision of staff employees, student workers, programs or processes.
- Plans and develops procedures for administering a large or complex department or program.
- Manages fiscal activities, including procurement and budget analysis.
- Provides guidance to subordinate staff and evaluates performance.
- Prepares abstracts, research reports, funding proposals, operations and procedure manuals, and other written material and documentation.
- Creates and reviews reports of expenditures and activities.
- May administer grants and grant-related related communications, scholarships and other operations.
- Develops, implements and maintains appropriate policies and procedures.
- May serve as property custodian for the department.
- Performs other job-related duties as assigned.
From Additional Posting Information:
- Process and manage contract agreements and associated invoice payments, ensuring compliance with institutional policies and contractual requirements.
- Process Procurement Card (P-Card) purchases and maintain accurate documentation and reconciliation records.
- Coordinate and process gift card purchases for both human subjects and non-human subjects research studies in accordance with applicable regulations and procedures.
- Verify and review monthly financial reconciliations for faculty grant cost centers to ensure accuracy and compliance with university financial guidelines.
- Oversee budgets, procurement activities, and financial analysis.
- Use Pivot database to identify funding opportunities for faculty.
- Review faculty grant applications for readability.
- Serve as backup for pre-award research administrator, including reviewing funders’ requests for applications to ensure eligibility and understand requirements, developing grant budgets, compiling all components of grant applications, submitting grants on behalf of the University, and ensuring adherence to applicable internal and federal regulations.
- Prepare research reports, abstracts, funding proposals, operational documents, and other written materials.
- Administer grants and grant-related communications when applicable.
- Develop, implement, and maintain policies and procedures that support program goals and compliance requirements.
Note some duplicates: "Prepare research reports, abstracts, funding proposals, operational documents, and other written materials." similar to earlier "Prepares abstracts, research reports, funding proposals, operations and procedure manuals, and other written material and documentation." and "Develops, implements and maintains appropriate policies and procedures." similar to later "Develop, implement, and maintain policies and procedures that support program goals and compliance requirements." We should preserve all but we can deduplicate? The instruction: "Remove duplicated lines". So we should eliminate duplicate sentences. Let's identify duplicates:
- Prepares abstracts, research reports, funding proposals, operations and procedure manuals, and other written material and documentation.
- Prepare research reports, abstracts, funding proposals, operational documents, and other written materials.
These are similar but not identical; one mentions operations and procedure manuals, the other operational documents. Could be considered distinct but overlapping. Might keep both? The instruction says remove duplicated lines. If they are not exact duplicates, we keep both. However we could combine? Safer to keep both as they are not exact duplicates.
- Develops, implements and maintains appropriate policies and procedures.
- Develop, implement, and maintain policies and procedures that support program goals and compliance requirements.
Again similar but not exact; one says appropriate policies and procedures, the other says policies and procedures that support program goals and compliance requirements. Keep both.
Now Responsibilities list will be long. We'll output as
- items.
Now Requirements/Qualifications: We have MQ: Education, Experience, Certification/Licensing: None. Also "Experience Will Be Considered In Lieu Of Education. Education will be considered in lieu of experience." That's a statement about substitution. We'll include that as part of Requirements.
We could have a section Requirements (or Qualifications). The instruction lists both Requirements and Qualifications as possible headings. We need to decide which to use. The posting has MQ (minimum qualifications) which includes Education and Experience. So we could use Qualifications for MQ, and Requirements for the experience/education substitution statement? Or combine. Better to have one section Qualifications with the MQ details, and maybe another section Requirements for the substitution statement? But that may be thin. Let's think: The substitution statement is about experience/education equivalence; it's a requirement/qualification nuance. Could be included under Qualifications as a note.
Thus we can have a single section Qualifications (or Requirements) containing:
- Education: Requires a thorough understanding of both theoretical and practical aspects of an analytical, technical or professional discipline; or the basic knowledge of more than one professional discipline. Knowledge of the discipline is normally obtained through a formal, directly job-related 4 year degree from a college or university or an equivalent in-depth specialized training program that is directly related to the type of work being performed.
- Experience: Requires a minimum of one (1) year of directly job-related experience.
- Certification/Licensing: None.
- Experience will be considered in lieu of education. Education will be considered in lieu of experience.
We could also note that all positions are security sensitive etc but we remove boilerplate.
Now we need to decide about Benefits, Pay, Schedule: Not present, so omit.
Now About the role: we could use first sentence of description as a short paragraph. That is specific content. Let's do that.
Thus final HTML:
About the role
Manages the day-to-day operations of a large university program or department, including the supervision of staff employees, student workers, programs or processes.
Responsibilities
- Plans and develops procedures for administering a large or complex department or program.
- Manages fiscal activities, including
- items.
Now Requirements/Qualifications: We have MQ: Education, Experience, Certification/Licensing: None. Also "Experience Will Be Considered In Lieu Of Education. Education will be considered in lieu of experience." That's a statement about substitution. We'll include that as part of Requirements.
We could have a section Requirements (or Qualifications). The instruction lists both Requirements and Qualifications as possible headings. We need to decide which to use. The posting has MQ (minimum qualifications) which includes Education and Experience. So we could use Qualifications for MQ, and Requirements for the experience/education substitution statement? Or combine. Better to have one section Qualifications with the MQ details, and maybe another section Requirements for the substitution statement? But that may be thin. Let's think: The substitution statement is about experience/education equivalence; it's a requirement/qualification nuance. Could be included under Qualifications as a note.
Thus we can have a single section Qualifications (or Requirements) containing:
- Education: Requires a thorough understanding of both theoretical and practical aspects of an analytical, technical or professional discipline; or the basic knowledge of more than one professional discipline. Knowledge of the discipline is normally obtained through a formal, directly job-related 4 year degree from a college or university or an equivalent in-depth specialized training program that is directly related to the type of work being performed.
- Experience: Requires a minimum of one (1) year of directly job-related experience.
- Certification/Licensing: None.
- Experience will be considered in lieu of education. Education will be considered in lieu of experience.
We could also note that all positions are security sensitive etc but we remove boilerplate.
Now we need to decide about Benefits, Pay, Schedule: Not present, so omit.
Now About the role: we could use first sentence of description as a short paragraph. That is specific content. Let's do that.
Thus final HTML: