Assistant Manager of Operations

. Minimum Requirements: "A high school diploma and experience in computer operations or a related field." Responsibilities: There's a section "Responsibilities" then subheadings: JOB KNOWLEDGE, Supervisory Responsibilities, Budgetary Responsibilities, Physical Requirements, Working Conditions, Work Schedule, Compensation Information, Essential Personnel Level, JOB LOCATION, Application Deadline, Military And Veteran, Closing Statement. We need to include sections only when posting has real, specific content. Many of these are boilerplate or placeholder like percentages empty. We need to filter. Let's examine each: - JOB KNOWLEDGE: "Fundamental working knowledge of concepts, practices and procedures and ability to apply in varied situations." That's substantive. - Supervisory Responsibilities: "Not responsible for supervising employees." That's substantive (though maybe minimal). It's a statement; we could include under Responsibilities? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have a section "Responsibilities" with content. Under that we can list bullet points? The subheadings like JOB KNOWLEDGE etc could be turned into

or

• . Probably better to treat each as a bullet under Responsibilities. - Budgetary Responsibilities: "No fiscal responsibility for the department's budget." That's also substantive. - Physical Requirements: list of percentages but all blank: "% Position self to accomplish task (i.e. stoop, kneel, crawl): % Walk or move about: % Stand for Prolonged Period: %". These are placeholders with no numbers. According to rule: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Physical Requirements section is not in the list of allowed headings but we could still include if we want? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Physical Requirements is not in that list, but we could still include as a heading? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive. But we should prefer a few substantive sections over many thin ones. Physical Requirements has no actual numbers, just placeholders; that's filler. So we should omit Physical Requirements section. - Working Conditions: similar placeholders with percentages empty. Omit. - Work Schedule: "Standard Hours: 15". That's specific: 15 hours? Probably per week. That's substantive. So we can include a Schedule section. - Compensation Information: "Expected Salary Range 34 - 30 Salary is dependent upon several factors including, but not limited to, a candidate's previous experience, knowledge, skills and performance in accordance with Clemson's compensation guidelines." The range seems odd: 34 - 30 (maybe $34k-$30k?). It's still specific numbers. So we can include Pay section. - Essential Personnel Level: "Emergency Response - In the event of an emergency closure or modified operations, this position is required to respond in order to provide the University's initial response to the emergency situation, including the execution of mission essential functions. Some positions in this category may be required to work remotely or be on call." That's substantive; could be part of Responsibilities or a separate section like "Essential Functions". Not in allowed headings but we could include under Responsibilities. - JOB LOCATION: "Columbia, SC". That's substantive; could be part of a short p. - Application Deadline: "September 25, 2026". That's metadata; could be short p. - Military And Veteran: details about military equivalency and veteran preference. That's substantive; could be a section like "Veteran Preference" but not in allowed headings. Could be included under Requirements? Might be considered as part of Requirements or Qualifications. But we have a Requirements section already (minimum requirements). We could add a note about veteran preference under Requirements or as a separate section "Veteran Preference". The instruction: Prefer a few substantive sections over many thin ones. So maybe we incorporate veteran info into a short p under Requirements or as a note. - Closing Statement: EEO boilerplate; we should remove. Thus we need to produce HTML fragment with sections: maybe:

  Job Summary

  (but job title already shown; we can still have a summary paragraph). Use

  .

  Job Duties

  with
  • each duty.

    Minimum Requirements

    with

    .

    Responsibilities

    with
    • for each responsibility point (Job Knowledge, Supervisory Responsibilities, Budgetary Responsibilities, Essential Personnel Level maybe). Could also include other responsibilities like "Develop and maintain relationship with local law enforcement & emergency services" but that's already in duties. We need to avoid duplication. Let's list responsibilities from the posting: - JOB KNOWLEDGE: Fundamental working knowledge of concepts, practices and procedures and ability to apply in varied situations. - Supervisory Responsibilities: Not responsible for supervising employees. - Budgetary Responsibilities: No fiscal responsibility for the department's budget. - Essential Personnel Level: Emergency Response - In the event of an emergency closure or modified operations, this position is required to respond in order to provide the University's initial response to the emergency situation, including the execution of mission essential functions. Some positions in this category may be required to work remotely or be on call. We could also include "Develop and maintain relationship with local law enforcement & emergency services" but that's already a duty. Thus responsibilities section can have those four bullets. Now Schedule: "Standard Hours: 15". We'll put under

      Schedule

      Standard Hours: 15

      . Pay: "Expected Salary Range 34 - 30 Salary is dependent upon several factors including, but not limited to, a candidate's previous experience, knowledge, skills and performance in accordance with Clemson's compensation guidelines." We'll put under

      Pay

      Expected Salary Range 34 - 30. Salary is dependent upon several factors including, but not limited to, a candidate's previous experience, knowledge, skills and performance in accordance with Clemson's compensation guidelines.

      . Location: Could be a short p under maybe "Location". Not a standard heading but we could add

      Location: Columbia, SC

      maybe under a generic "About the role"? But we already have Job Summary. Could add a

      Location: Columbia, SC

      after summary. Application Deadline: Could be a

      Application Deadline: September 25, 2026

      . Veteran Preference: Could be a

      Veteran Preference: South Carolina provides employment preference to eligible veterans for qualifying full-time permanent positions. To be considered, applicants must meet the minimum qualifications, have been discharged under honorable conditions, and indicate their veteran status in the application by uploading a DD-214 for confidential review. A request for Veteran Preference can be made via the application process. Please contact hrjob@clemson.edu with any questions or issues.

      plus the Military Equivalency line. We need to decide whether to create a separate section for Veteran Preference. The instruction: Prefer a few substantive sections over many thin ones. So maybe we incorporate veteran info into a short p under Requirements or as a note. But we already have Minimum Requirements section; we could add a note there. But the veteran preference is not a requirement; it's a preference. Could be its own section but that would be thin. However it's substantive. Could be under a heading "Veteran Preference". The allowed headings list didn't include it but we can still use h3 for any section heading; they gave examples. I think it's okay to add a section for Veteran Preference. But we must avoid creating sections with filler. This is substantive. Thus final sections: Job Summary, Job Duties, Minimum Requirements, Responsibilities, Pay, Schedule, Location, Application Deadline, Veteran Preference (maybe also include Military Equivalency). We could combine Location and Application Deadline into a short p under Job Summary? Better to keep them separate small paragraphs. We must not repeat job title as heading. We are not. We must not include Job ID / requisition numbers as headings; we have Job Code AH75 Employee Type Temporary (TMP) Staff (Fixed Term). That's minor metadata; we can fold into a short p maybe under Job Summary or as a separate p "Job Code: AH75; Employee Type: Temporary (TMP) Staff (Fixed Term)". We'll include that. Now ensure we remove boilerplate: EEO/AA, etc. Also remove "Closing Statement". Remove "Military And Veteran" heading but we keep content. Now produce HTML. Let's craft:

      Job Summary

      This position involves managing building security systems, property gate systems, coordinating IT needs, TigerOne, A3Communication. Managing assets and inventories. Develop and maintain relationship with local law enforcement & emergency services, other duties as assigned. Job Code: AH75; Employee Type: Temporary (TMP) Staff (Fixed Term).

      Job Duties

      • 15% - Develop and maintain relationships with local law enforcement & emergency services. Monitor Sandhill and Children's Garden social media presence and respond to inquiries from the public. Manage Sandhill Fish Club.
      • 15% - Maintaining IT-related inventory. Coordinate needs with regional IT support staff. Provide general support for online presence, A/V needs.
      • 20% - Maintain equipment, building, and other asset inventories for reporting purposes. Provide information for property insurance claims.
      • 50% - As Building Security Coordinator - responsible for managing building security systems, property gate systems to include multiple occupied and unoccupied buildings alarm / camera systems. Managing the property gate systems, TigerOne and A3 Communications.

      Minimum Requirements

      A high school diploma and experience in computer operations or a related