ADMIN OFCR 2

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. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO etc). Must not invent or summarize away detail. Must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. We have posting content: Job Summary (first paragraph). Then details: "Applications from current UCD/UCDHS employees will be considered first..." etc. Then "Apply By Date: 9/26/2026 at 11:59 pm – Interviews and recruiting process may occur at any time". That's application instruction; we must remove application instructions. So drop that line. Then Minimum Qualifications list (bullets). Then Preferred Qualifications list. Then Key Responsibilities with percentages. Then Department Overview paragraph. Then POSITION INFORMATION includes Salary or Pay Range: $31.59 - $53.07, Salary Frequency: Hourly, Salary Grade: 135, UC Job Title, UC Job Code, Number of Positions, Appointment Type, Percentage of Time, Shift (Work Schedule): 8 hours, Location, Union Representation, Benefits Eligible: Yes, This position is hybrid (mix of on-site and remote work). Then Benefits section describing benefits. Then Physical Demands, Mental Demands, Work Environment, Special Requirements, etc. Many of these are boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Physical Demands etc might be considered part of job description; not explicitly prohibited. Should we keep them? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep substantive info like physical demands, mental demands, work environment, special requirements, etc. However we must only include sections when posting has real specific content for it. We have content for Pay (salary range), Schedule (Shift: 8 hours, hybrid), Benefits (detailed). Also we have About the role (Job Summary). Responsibilities (Key Responsibilities). Requirements (Minimum Qualifications). Qualifications (Preferred Qualifications). Skills maybe could be derived from qualifications but we could combine. However we need to decide which sections to output. We have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content: - About the role: Job Summary paragraph(s). Could combine first paragraph and maybe department overview? The "Job Summary" is about role. Department Overview could be part of About the role or separate but we don't have a heading for Department Overview. Could include under About the role. - Responsibilities: Key Responsibilities (65% - ADMINISTRATIVE, 35% - ANALYTICAL/PROJECT/COMMITTEE SUPPORT). Also maybe list of duties from Job Summary (research, analyze, compile, correspondence, etc). We'll include those as bullet list under Responsibilities. - Requirements: Minimum Qualifications (list). Could also include "Applications from current UCD/UCDHS employees will be considered first" but that's application instruction; remove. - Qualifications: Preferred Qualifications list. - Skills: Could extract from qualifications: technical proficiency, Outlook Calendar, Microsoft Office, etc. But we might not need separate Skills section if content overlaps; but we can create a Skills section summarizing specific skills mentioned: proficiency in multiple software, office hardware, computer systems; Outlook Calendar; Microsoft Office (Word, Excel, PowerPoint, Visio, etc.); project management; analytical; organizational; time management; multi-tasking; written/verbal communication; diplomacy; discretion; political acumen; etc. However we must not invent or summarize away detail; we can list them as bullet points directly from the posting. That's okay. - Benefits: The Benefits paragraph describing benefits. We'll include as

• items? The posting has prose describing benefits; we can keep as

  or break into list. The instruction: Use

  • for any list of duties/requirements/benefits, and

    for prose. Benefits is a list of items; we can convert each benefit sentence into

  • . But we must preserve all substantive information; we can keep as

    if it's prose. However the instruction says use

    • for any list of duties/requirements/benefits. So we should convert benefits to list. - Pay: Salary or Pay Range: $31.59 - $53.07, Salary Frequency: Hourly, Salary Grade: 135. We'll include as

      maybe. - Schedule: Shift (Work Schedule): 8 hours, Location: North Addition Office Building (HSP002), Hybrid (mix of on-site and remote work). Also maybe Percentage of Time: 100%. We'll include as

      or list. We must not repeat job title as heading. Already not. We must not put Job ID/requisition numbers as headings; we have UC Job Title, UC Job Code etc. Those are metadata; we should fold minor metadata into a short

      or drop it. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it." So we can include UC Job Title and UC Job Code in a short paragraph maybe under About the role or separate small paragraph. But we should not create a heading for them. We'll just include them in a

      maybe after About the role. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes EEO statement at end; we must remove that. Also includes "A Culture of Opportunity and Belonging" etc; that's maybe boilerplate? It's about UC values; could be considered boilerplate but not explicitly prohibited. However it's not substantive job info; might be considered fluff. The instruction says remove boilerplate; but not explicitly define what is boilerplate. The EEO statement is definitely boilerplate. The "A Culture of Opportunity and Belonging" paragraph might be considered promotional boilerplate; but it's not EEO. Might be okay to keep? Safer to remove promotional fluff as well? The instruction only mentions cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we can keep the culture paragraph. However it's not directly about the role; but it's not prohibited. We'll keep it maybe under About the role? But it's lengthy; might be considered filler. I'd lean to remove it because it's not substantive job info. But it's not explicitly listed; but to be safe, I'll keep it? The instruction says "Preserve ALL substantive information". That paragraph is not substantive about the role; it's more about UC values. Could be considered not substantive. I'd remove it to keep focus. Also remove "Physical Demands", "Mental Demands", "Work Environment", "Special Requirements" maybe they are substantive? They describe job demands; could be considered substantive. The instruction didn't say to remove them. So we keep them. But we need to fit into sections: we have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Where to put Physical Demands etc? Could be part of About the role or maybe a separate section not listed; but we only allowed those headings. We could incorporate them into About the role as additional paragraphs. Or we could create a separate section like "Working Conditions" but not allowed. So we need to fit them somewhere. Perhaps we can add them under About the role as extra paragraphs. Alternatively, we could create a section "Requirements" for physical demands? Not ideal. Better: Keep them under About the role as additional paragraphs describing the role's demands. Thus About the role will contain: Job Summary paragraph, Department Overview, Physical Demands, Mental Demands, Work Environment, Special Requirements (maybe condensed). But we must not lose info. We must also remove duplicated lines. There's no obvious duplication. Now craft HTML. Structure:

      About the role

      Job summary text...

      Department Overview text...

      Physical Demands: ...

      Mental Demands: ...

      Work Environment: ...

      Special Requirements: ...

      UC Job Title: ADMIN OFCR 2 CX; UC Job Code: 004263.

      Responsibilities

      • 65% - ADMINISTRATIVE
      • 35% - ANALYTICAL/PROJECT/COMMITTEE SUPPORT

      Utilize initiative, judgment and discretion in researching, analyzing and compiling necessary background information to assist executive leadership and support staff in responding to a wide variety of issues; research and initiate an array of correspondence on behalf of executive leadership; independently assume responsibility for issues that do not require the involvement of executive leadership; apply problem solving techniques to resolve various situations; and provide referrals to appropriate offices and authorities.

      As principal calendar, project and communication support to the CFO, respond through verbal and/or written communication to a wide variety of inquiries from faculty, staff, the public and the highest levels of the UC system; research requests for meetings and help to track correspondence; manage complex calendars to determine priorities of meetings and resolve scheduling conflicts; handle all aspects of travel arrangement and reimbursement.

      Partner with counterparts throughout UC Davis and UC Davis Health to fulfill daily operations as needed.

      Requirements

      • Bachelor's degree in related area or combination of equivalent experience or training.
      • Experience working in an executive-level office and providing high-level administrative support to executive leadership.
      • Proven experience managing complex, executive-level electronic calendars.
      • Minimum of 5 years experience working in c-suite level executive support.
      • Demonstrated political acumen and discretion in maintaining confidentiality.
      • Excellent written and verbal communication skills and diplomacy to handle sensitive and/or difficult situations.
      • Demonstrated project management skills to balance competing deadlines and successfully support multiple meetings and projects.
      • Demonstrated organizational and analytical skills to independently manage complex projects and events.
      • Strong time management and multi-tasking skills.
      • Strong analytical, research and problem-solving skills.
      • Excellent typing, writing, editing and proofreading skills to produce correspondence and other written materials.
      • High degree of proficiency using Outlook Calendar and Microsoft Office (e.g., Word, Excel, PowerPoint, Visio, etc.).

      Qualifications

      • Experience working at an academic medical institution or higher education environment.
      • Experience coordinating conferences/meetings and special events.
      • Experience working in a confidential environment with demonstrated understanding of HIPAA standards.
      • Knowledge of UC Davis and UC Davis Health policies and procedures.
      • Knowledge of UC Davis and UC Davis Health specific programs (AggieTravel, Aggie Service, IT Service Now, Conference Services, Aggie Enterprise, Lawson, BEATS, UC Path, JobBuilder, etc.).

      Skills

      • Technical proficiency in multiple software, office hardware and computer systems.
      • Proficiency with Outlook Calendar and Microsoft Office (Word, Excel, PowerPoint, Visio, etc.).
      • Project management skills.
      • Organizational and analytical skills.
      • Strong time management and multi-tasking abilities.