Project Manager, Campus Construction

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, etc. Also remove navigation, cookie, etc. Must not create sections with filler like "commensurate with experience" etc. For Pay: we have Salary Range: $90,000-$95,000 annualized, commensurate with education, experience, and qualifications. That's specific numbers, so we can include Pay section with that range. However note "commensurate with education, experience, and qualifications" is somewhat filler but still part of description. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we cannot have Pay section if the content is just "commensurate with experience"? But we have actual range $90k-$95k. That's specific. The phrase "commensurate with education, experience, and qualifications" is additional but not placeholder. It's okay. So we can include Pay. Schedule: The posting mentions "Full Time" and maybe no explicit schedule details like hours. It says Job Type: Full Time. No schedule details like M-F 9-5. So we should not create Schedule section because no specific schedule info. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Schedule, we have only "Full Time" which is job type, not schedule. Might be considered schedule? Probably not enough detail. Safer to omit Schedule. Benefits: Not mentioned. So omit Benefits. About the role: Could be the introductory paragraph about UT San Antonio? That's about the institution, not the role. The "Job Summary" is about the role. So we can have About the role section maybe using the Job Summary paragraph. Or we could treat "Job Summary" as About the role. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role with the Job Summary text. Responsibilities: The "Core Responsibilities" bullet list. Requirements: Might be "Required Qualifications" (Bachelor's degree, 5 years experience, driver's license, etc). Also "Required Application Materials" (Resume required, Cover Letter preferred) but that's application instructions, which we must remove. So we should not include application instructions. So Requirements section could include Required Qualifications (education, experience, driver's license). Also maybe "Verification of a valid driver’s license and Motor Vehicle Record (MVR) may be completed as applicable." That's part of qualifications. Skills: "Knowledge, Skills, And Abilities" list. We also have "Working Conditions", "Physical Demands", "Ability to telecommute or apply a flex work schedule." Those could be part of Requirements or maybe separate but we only have set headings. Could incorporate into Requirements or Skills? Probably better to include under Requirements (or maybe under Skills). But we have limited headings. Could add a section "Working Conditions" but not in allowed list. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the expected headings. It says "Prefer a few substantive sections over many thin ones." So we should stick to those headings. So we need to map content to those. Thus: - About the role: Job Summary paragraph. - Responsibilities: Core Responsibilities list (maybe as

• ). - Requirements: Could combine Required Qualifications (education, experience, driver's license) plus maybe "Ability to telecommute or apply a flex work schedule." and "Physical Demands" etc. But we need to decide. - Qualifications: Might be similar to Requirements; but we have both headings. Could separate: Requirements = mandatory qualifications (education, experience, driver's license). Qualifications = preferred or additional? The posting has "Required Qualifications" and also "Knowledge, Skills, And Abilities". So we can map: - Requirements: Required Qualifications (Bachelor's degree, 5 years experience, valid driver's license, ability to maintain security, etc.) - Qualifications: Knowledge, Skills, And Abilities (Verbal and Written Communication, Customer Service, Microsoft Office, Cost Estimating, Scheduling, and Design Software, Building Codes, Fire and Life Safety Codes, Procurement Processes, Regulatory Compliance). Also maybe "Ability to telecommute or apply a flex work schedule." but that's more of a condition. But we also have "Working Conditions", "Physical Demands", "Ability to telecommute or apply a flex work schedule." Could be placed under Requirements or Qualifications. Might be better to put under Requirements as they are job conditions. But we need to avoid filler. All content is specific. Pay: Salary Range. We must not include sections like Benefits, Schedule. Thus final HTML:

  About the role

  The Project Manager, Campus Construction is responsible for setting up project success by developing scopes of work, planning projects, and managing construction activities through project close-out. This role works under the general supervision of and reporting to the Director of Institutional Construction and in direct collaboration with Campus Planning, leads project definition coordination, project budget & schedule development, and customer service efforts.

  Responsibilities

  • Meets with users to develop scopes of work and develop project schedules and budgets.
  • Communicates with internal stakeholders and Real Estate and Property Management leadership by performing project analysis and reporting methodologies.
  • Prepares cost estimates and obtain approvals necessary to begin a project.
  • Coordinates/assists in selecting professional design firms and coordinates comments to drawings and specifications during the design process.
  • Coordinates/assists in the preparation of bid documents for procurement of construction services, and the selection of contractors.
  • Coordinates design review with internal Authority Having Jurisdiction (AHJ) and Project Management Team.
  • Coordinates Pre-Construction Conferences.
  • Ensures that design documents and construction activities comply with university standards, federal and state regulations, and applicable codes and standards.
  • Reviews, processes, and approves construction-related RFIs, ASIs, cost proposals, change orders, invoices, pay applications, and other related project documents.
  • Conducts team meetings, owner/architect meetings, and budget reviews.
  • Monitors and complies with project budgets and schedules.
  • Monitors construction for quality, coordinates punch lists and warranties and assists maintenance with warranty issues for one year.
  • Coordinates inspections and the involvement of the University’s trade shops and departments associated with the project.
  • Schedules, coordinates and communicates utility outages.
  • Coordinates planned construction activities with affected building occupants and UTSA service departments.
  • Assists contractors in gaining access to occupied buildings.
  • Collects and disseminates a complete set of project closeout documentation.
  • Supports the Real Estate and Property Management (RPM) Team in business activities.
  • Establishes and maintains effective relationships and communication with the client, construction manager, project team, consultants/architect/engineers, subcontractors, and adjacent community.
  • Performs other duties as assigned.

  Requirements

  • Bachelor’s degree in a related field.
  • Five (5) years of related work experience.
  • Valid driver's license.
  • Ability to maintain the security and integrity of UT San Antonio and its infrastructure.
  • Ability to telecommute or apply a flex work schedule.
  • Physical demands: ability to lift up to 25 pounds occasionally; work may require odd hours, weekend work, extreme heat, inclement weather, bending, climbing, crawling, working at heights, confined spaces, rotating machinery, energized systems, biohazards, chemicals; occasional off-site meetings/training; frequent travel to multiple university-owned campuses and leased spaces; travel and parking expenses are employee’s responsibility.

  Qualifications

  • Verbal and Written Communication.
  • Customer Service.
  • Microsoft Office.
  • Cost Estimating, Scheduling, and Design Software.
  • Building Codes, Fire and Life Safety Codes.
  • Procurement Processes.
  • Regulatory Compliance.

  Pay

  Salary Range: $90,000-$95,000 annualized, commensurate with education, experience, and qualifications.

  We must not include any extra sections like Benefits, Schedule. Check for any boilerplate: we removed EEO, navigation, etc. Also removed "Job Details", "Job Summary" heading (we used About the role). Also removed "Required Application Materials". Also removed "Posting Close Date", "Job Type", etc. Those are minor metadata; we could fold into a short p or drop. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we could optionally include a short paragraph with Job Type, Posting Close Date, etc. But we prefer few substantive sections; we could drop them. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Is Posting Close Date substantive? It's metadata about application timeline. Might be considered substantive but minor. The instruction says fold minor metadata into a short

  or drop it. So we could include a short p after About the role maybe. But we already have About the role with job summary; we could add a small p with "Job Type: Full Time. Posting close date: 09/30/2026." However that might be considered minor metadata. It's okay to include as a short p. But we must not create a heading for it. So we can add a

  after About the role containing that info. Similarly, we could include "Job Type: Full Time" and "Posting Close Date: Applications will be accepted through 11:59 PM CDT on 09/30/2026." Also note "At the discretion of the hiring department, this posting may close once a sufficient number of qualified applications have been received." That's also minor metadata. We could include a short paragraph: "

  Job Type: Full Time. Applications will be accepted through 11:59 PM CDT on 09/30/2026; the posting may close earlier if a sufficient number of qualified applications are received.

  " That preserves the info. We must not include "Required Application Materials" (Resume required, Cover Letter preferred) as that's application instructions, which we must remove. Thus final HTML includes About the role paragraph, then a small metadata p, then Responsibilities, Requirements, Qualifications, Pay. Check that we didn't miss any substantive info: The "Job Summary" we used. The "Core Responsibilities" we used. The "Required Qualifications" we used. The "Knowledge, Skills, And Abilities" we used. The "Working Conditions" and "Physical Demands" we folded into Requirements (maybe as a list item). The "Ability to telecommute or apply a flex work schedule." we included. The "Verification of a valid driver’s license and Motor Vehicle Record (MV