Senior Administrative Associate

We need to output HTML fragment with sections: About the role? The posting includes "Purpose" which is like About the role. Also "Responsibilities" (multiple bullet points). "Required Qualifications". "Preferred Qualifications". "Salary Range". "Working Conditions". "Work Shift". "Required Materials". Also "General Notes" about benefits. Benefits section: we have benefits described. Should we create Benefits section? Yes, there is specific content about benefits: health insurance, retirement plans, paid leave, LinkedIn Learning, conference opportunities, employee discount, library/museum access, shuttle/CapMetro. So Benefits section. Pay: Salary Range $55,000 + depending on qualifications. So Pay section. Schedule: Work Shift Flexible between the hours of 7am - 6pm, onsite with potential for 1-2 days remote. Also Weekly Scheduled Hours: 40. So Schedule section. We must not repeat job title as heading. Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must remove boilerplate: EEO, legal, etc. Remove duplicated lines, application instructions, etc. Also remove navigation/cookie etc. Remove "Important for applicants..." etc. Remove "Employment Eligibility Verification", etc. Remove "Background Checks", "Retirement Plan Eligibility", etc? Actually retirement plan eligibility is part of benefits? It mentions retirement plan eligibility but we already have benefits. Might keep as part of benefits? But it's more detail about eligibility. Could include in Benefits? Might be considered boilerplate? It's specific to the position. However the instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Retirement plan eligibility is not exactly boilerplate but maybe considered part of benefits. We can keep it in Benefits or maybe separate? The instruction: Prefer a few substantive sections over many thin ones. So we can incorporate retirement plan eligibility into Benefits. We also need to include "General Notes" about benefits. So Benefits section will contain that. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from responsibilities, qualifications, etc. We must not create sections with filler like "commensurate with experience". Not needed. We need to output only HTML fragment, no /, no markdown. Let's structure:

  About the Role

  (or Purpose). Use "About the role" as heading per instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings. We need to map content: - About the role: purpose paragraph. - Responsibilities: list of duties (procurement, travel, document management, website/audit/inventory, scheduling, events coordination, additional tasks, room reservations, front office). We'll need to break into

  • . - Requirements: maybe Required Qualifications? They said Requirements heading. Could use Requirements for required qualifications. Or Qualifications heading for both required and preferred? They have Requirements, Qualifications, Skills as possible headings. We'll decide: Use Requirements for required qualifications. Use Qualifications for preferred qualifications? Or Skills for skills? But we have both required and preferred qualifications. Could put required under Requirements, preferred under Qualifications. Or combine? Better to follow instruction: include a section only when posting has real specific content. So we can have Requirements (required qualifications) and Qualifications (preferred qualifications). Also Skills maybe not needed. - Benefits: as described. - Pay: Salary Range. - Schedule: Weekly Scheduled Hours and Work Shift. We also have "Working Conditions": Standard office environment, repetitive use of keyboard. Could be part of Schedule or separate? Could be its own section but we prefer few substantive sections. Could incorporate into Schedule or maybe a separate "Working Conditions" section. The instruction list includes Working Conditions as an example? Not in the list but they gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So Working Conditions not listed; we could omit as separate section and maybe incorporate into Schedule or Benefits? But it's substantive. Could add as a section "Working Conditions" though not in examples but allowed? The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we can add other headings if needed. But they prefer few substantive sections. We could incorporate Working Conditions into Schedule or maybe a separate short section. I'd add a section "Working Conditions" as it's distinct. But we also have "Required Materials": resume, references, letter of interest. That's application instructions, which we should remove per instruction: remove application instructions. So we should omit Required Materials section. Indeed they said remove application instructions. So we exclude that. Also remove "Important for applicants..." etc. Thus final sections: About the role, Responsibilities, Requirements (required qualifications), Qualifications (preferred qualifications), Benefits, Pay, Schedule, Working Conditions. Now we need to extract content precisely. About the role: The purpose paragraph: "This position will provide high-level administrative and transactional support to the Department of Educational Leadership and Policy, which includes the Education Research Center, with a customer service emphasis as a staff team member in a large academic department. Ensure consistent application of all departmental, University, and UT systems policies and procedures." We'll put that in

    . Responsibilities: Need to list all duties. The responsibilities section is long with many bullet-like sentences. We'll convert each sentence or clause into

    . Must preserve all detail. Let's parse responsibilities block: "Procurement, Purchasing, & Payments: Responsible for Department and ERC purchasing, procurement, and payments, researcher access fees. Order and process Department-related expenses in a timely manner. Serve as the Department's ProCard holder. Request, collect, and upload receipts to UT Box for reconciliation. Responsible for creating payment vouchers (VP1, VP2, and VPE documents). Process Official Occasion Expense Forms as appropriate. Serve as department representative for contract processing in ContractsPlus." "Travel: Serve as the Department's coordinator for faculty, student, and visitor travel and ERC faculty and staff. Create VE5 documents in DEFINE prior to travel and create VP5 travel reimbursement documents. Work with the Accountant to ensure accurate processing." "Document and Request Management: Review, evaluate, and prepare incoming documents and ensure proper routing prepare transmittal documents, set up documents for signature complete file set-up and data entry create project status reports, and perform follow-up. Manage FERPA review requests. Manage proposal, extension, and amendment submissions, and researcher onboarding and project and researcher closeouts. Track and document data files each researcher is allowed to access. Routed researcher documents needing signatures through DocuSign. Coordinate with COE HR for any HR needs and appoint Graduate Research Assistants." "Website, Audit & Inventory: Update documents on the ERC website and send to the IT Coordinator to update the website. Monitor website for accuracy. Annual downloads from the state agency websites. Provide all necessary/requested documentation for the yearly audit. Maintain the ERC equipment inventory database. Track ERC assets, including WORQ Space reports, computer equipment inventory, and computer replacement schedule. Coordinate annual inventory with the Senior Admin Manager and prepare the report for submission." "Scheduling: Add researchers to the Google Calendar VM use. Keep track of training requirements and expiration, IRB dates, and project expiration. Track when payments need to be invoiced. Schedule FERPA reviews and by what date the reviews need to be completed." "Events Coordination: Assist in the coordination of events and meetings and logistics for department meetings and events (including new student orientation, semester receptions, retirement receptions, guest lectures, faculty recruiting, etc.)." "Additional tasks: Assist the Senior Administrative Manager with tasks and projects as needed. Support other Department Administrative Office staff and ERC faculty and staff by assisting with various projects. Other related duties as assigned." "Room Reservations: Responsible for assisting individuals with reserving ELP classrooms for non-class-related events. Maintain ELP-controlled classrooms and spaces to keep them ready for academic use." "Inventory: Assist Senior Administrative Manager with departmental equipment inventory." "Front Office: Serve as the first point of contact for ELP visitors when work study staff is not present. Answer the department's main line and direct calls to other offices or staff, and greet the public. Responsible for office supplies and keeping the lobby and kitchen tidy" We need to ensure we don't duplicate "Other related duties as assigned." appears multiple times; we can keep once maybe but it's duplicated. We should remove duplicated lines. So we can include it once. We'll create a

    with each responsibility as
    • . Might be long but okay. Now Requirements (required qualifications): The block: "Required Qualifications Bachelor's degree and three years of experience at the Administrative Associate level, or high school graduation or GED, and seven years of clerical experience, including one year of experience at the Administrative Assistant level. Strong interpersonal and problem-solving skills. Excellent oral and written communication skills. Ability to work independently and as part of a team. Ability to interact and maintain productive working relationships with a population of faculty, staff, and students, and maintain a positive and professional demeanor. Ability to assess workload, prioritize tasks, and meet deadlines to successfully manage concurrent projects for multiple areas with accuracy. Experience with MS Office suite. Ability to learn quickly and be flexible. Experience arranging events. Experience taking ownership of projects and seeing them through to successful completion. Ability to undertake and complete tasks with minimal supervision and exhibit individual initiative in meeting the functions of the position. Relevant education and experience may be substituted as appropriate." We'll put each sentence as
    • under
      . Preferred Qualifications: "Experience using UT mainframe accounting system and FRMS." That's it. Benefits: From General Notes: "The university provides employees a competitive benefits package that includes health insurance (premiums covered 100% for full-time benefits-eligible employees), retirement plans, and paid leave, in addition to other programs and services. We offer robust free training access through LinkedIn Learning, professional conference opportunities, an expansive employee discount program, including athletic tickets. Free access to UT Austin's libraries and museums with a staff ID card. Free rides on all UT Shuttle and Austin CapMetro buses with a staff ID card. For more details, please see: https://hr.utexas.edu/prospective/benefits and https://hr.utexas.edu/current/services/my-total-rewards" We should keep the URLs? Probably yes as they are substantive. We'll include them as part of

      maybe. Pay: "Salary Range $55,000 + depending on qualifications" Schedule: Weekly Scheduled Hours: 40. Work Shift Flexible between the hours of 7am - 6pm, onsite with the potential for 1-2 days remote. We'll combine:

      Weekly scheduled hours: 40. Work shift flexible between 7am‑6pm, onsite with potential for 1‑2 days remote.

      Working Conditions: "Standard office environment, Repetitive use of a keyboard at a workstation" We'll put that. Now ensure we don't include any boilerplate like EEO, etc. Now output HTML fragment. Let's craft:

      About the Role

      This position will provide high-level administrative and transactional support to the Department of Educational Leadership and Policy, which includes the Education Research Center, with a customer service emphasis as a staff team member in a large academic department. Ensure consistent application of all departmental, University, and UT systems policies and procedures.

      Responsibilities