Administrative Support Assistant II
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can choose which headings to use based on content. We have content for About the role (position purpose). Responsibilities (duties). Requirements (required qualifications). Qualifications (maybe preferred qualifications). Benefits. Pay. Possibly Skills? Could embed skills within qualifications. Better to not create Skills if not separate.
We must not include headings with filler. So we need to ensure each heading has substantive content.
Let's plan:
About the role
Position purpose plus maybe workplace type, FT/PT, temporary end date, pay plan.
Responsibilities
- ... list each duty? The duties are long paragraphs; we could break into bullet points summarizing each duty but must preserve ALL substantive information; we cannot invent or summarize away detail. We need to preserve all substantive information; we can keep the paragraphs as
but instruction says use
- for any list of duties/requirements/benefits. The duties are not a list but a description; we could keep as
. However they said "Use
- for any list of duties/requirements/benefits". If we have a list, we should use ul/li. The duties are many bullet-like sentences but currently in paragraph form. We could convert each duty sentence into a list item to satisfy rule while preserving info. That would be a list of duties. That seems acceptable.
Similarly for Required Qualifications: we have education & experience and SKAs list; we can make ul/li.
Preferred Qualifications: also list.
Benefits: we have a sentence describing benefits; could be
or ul/li if we break into items. The benefits list includes medical plans, dental, vision, retirement, tuition waiver, vacation days, sick leave, holidays. Could make ul/li. Pay: we have anticipated hiring range and CSU classification salary range and pay basis monthly. Could be
. We must not include sections like Schedule. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The text includes a lot of boilerplate at end about EEO etc. We need to drop those. Also drop "CANDIDATES ELIGIBLE TO APPLY: Open to all qualified applicants" maybe not needed? It's minor metadata; could be folded into short p or dropped. Probably drop. Also drop "CLASSIFICATION TITLE: Administrative Support Assistant II UNION CODE: R07 TEMPORARY END DATE: ..." That's metadata; we could fold into short p under About the role? But instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short p with classification title, union code, temporary end date, FT/PT, pay plan, workplace type maybe. But we already have About the role p; we could incorporate those details there. We must preserve ALL substantive information; not invent or summarize away detail. So we need to keep all details from the posting, except boilerplate. That includes classification title, union code, temporary end date, FT/PT, pay plan, workplace type, anticipated hiring range, pay basis, benefits description, position purpose, duties & responsibilities, required qualifications (education & experience, SKAs), preferred qualifications, physical demands, environmental factors, special conditions (screening, background check, education code, sensitive position, general information). Also we must keep the statement about offer amount commensurate? That's vague but it's substantive? It's a statement; we could include in Pay section as a note. It's not filler like "commensurate with experience" is allowed? The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") . So we cannot have a Pay section that only says "commensurate with experience". But we have actual range, so we can include that plus note that offer will be commensurate. That's okay. We must not create Pay/Schedule/Benefits sections unless posting actually states them. We have Pay and Benefits stated, so okay. Now we need to output only HTML fragment. Let's craft:
About the role
Classification Title: Administrative Support Assistant II; Union Code: R07; Temporary position ending on or before June 30, 2027; Full-time; 12-month pay plan; On-site (work in-person at business location). Under general supervision of the College of Natural Sciences, Mathematics and Engineering Director of Grants and Outreach and the California Energy Research Center Director, the Grants and Events Assistant provides administrative support for externally funded projects and related outreach activities. The position coordinates assigned event and grant-administration activities; processes personnel, purchasing, travel, reimbursement, and other financial documentation; maintains grant and event records; monitors deadlines and budget-related information; and applies established university and grant procedures. The Grants and Events Assistant also assists with the planning and implementation of NSME GO outreach events, CERC events, and the annual conference; serves as a resource for routine administrative and logistical questions; coordinates with campus offices and vendors; and identifies and resolves routine issues within established guidelines.
That includes classification details and position purpose. Now Responsibilities: we need to list duties. The duties are long; we can break into list items each covering a duty paragraph. Let's extract each duty paragraph from the text: From "Duties & Responsibilities" section: - Assist with planning and coordinating of annual outreach events by developing and maintaining event timelines, tracking assigned tasks, coordinating logistical arrangements, and following up with participants and campus service providers. - Assist with planning and coordinating community outreach events outlined in the grant proposal including coordinating schedules, locations, supplies, services, registration materials, and other event-related requirements. - Monitor and adhere to event timelines, maintain budget records, and communicate status, outstanding items, and anticipated issues to the appropriate Director. - Review event-related purchasing, reimbursement, and risk-management documentation for completeness and compliance with established university and grant requirements. Identify missing or inconsistent information and coordinate corrections before submitting documents for approval. - Prepare and process requisitions, payment requests, reimbursement documents, and related financial records for outreach events and activities. Track transactions, reconcile event-related expenditures, and follow up on routine discrepancies. - Serve as a primary contact for routine event logistics questions from faculty, staff, students, vendors, community participants, and campus offices. Provide information regarding established procedures and refer complex or non-routine matters to the appropriate Director. - Maintain event calendars, directories, websites, and social media platforms to promote engagement by entering current information, updating event details, removing outdated content, and coordinating corrections as needed. - Assist in collecting post-event feedback to evaluate event outcomes. - Review, scan, and log all budget related documentation of events and activities for accuracy and compliance prior to obtaining appropriate approvals. - Grant Administrative Support: Prepare routine email distributions, meeting materials, and correspondence; schedule grant-related meetings; maintain calendars; and communicate changes, deadlines, and follow-up requirements to participants. - Prepare and process grant personnel forms, including contracts, special consultant forms, faculty, and student hire forms. Review documents for completeness, obtain required supporting information, and route materials for appropriate review and approval. - Track and document grant-related administrative activities. Notify the Directors of upcoming due dates, missing information, delayed actions, and routine issues requiring follow-up. - Organize, maintain, and update electronic and paper grant files, including approvals, contracts, personnel documents, purchasing records, travel documentation, correspondence, reports, and financial records. - Arrange domestic and international travel for authorized grant personnel and students in accordance with university travel procedures and grant requirements. Prepare travel-related documentation, coordinate transportation and lodging, and maintain supporting records. - Assist with purchasing grant-related supplies by obtaining required information, preparing requisitions or purchase requests, tracking orders, maintaining documentation, and following up with vendors or campus offices regarding routine issues. - Coordinate with campus offices, including procurement, accounts payable, travel, human resources, academic departments, and other administrative units, to obtain information, resolve routine processing issues, and complete grant-related transactions. That's many items. We'll put each as - . Now Required Qualifications: Education & Experience – High school diploma or GED and three (3) years of recent (within five years) experience in an office environment. SKAs list: many bullet-like statements. We'll break each into
- .
Preferred Qualifications: Two (2) years professional experience in a higher education setting. Demonstrated skills in an institutional/educational environment possessing a customer-oriented and service-centered attitude.
Physical Demands: SEDENTARY WORK – involves mainly sitting; minimal walking and standing; lifting light weight objects limited to 15 pounds.
Environmental Factors: N/A (that's placeholder; we should not include a section with just N/A). So we can skip Environmental Factors section.
Special Conditions: Screening, Background Check, Education Code 89521 Requirements, Sensitive Position, General Information. We'll include these as a section maybe "Special Conditions" or we could fold into Requirements? But we have heading "Special Conditions" not in the example list but we can use if content exists. The instruction gave examples but not limited to those; we can use other headings if needed. However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should stick to those examples; but we could also use other headings if needed? Safer to stick to those. We could incorporate special conditions into Requirements or Qualifications? Might be better to have a "Requirements" section that includes required qualifications, and maybe "Qualifications" for preferred. Special conditions could be part of Requirements? Not ideal. But we could create a "Requirements" section that includes both required qualifications and special conditions (screening, background check, etc.) as list items. However the instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other
- for any list of duties/requirements/benefits". If we have a list, we should use ul/li. The duties are many bullet-like sentences but currently in paragraph form. We could convert each duty sentence into a list item to satisfy rule while preserving info. That would be a list of duties. That seems acceptable.
Similarly for Required Qualifications: we have education & experience and SKAs list; we can make ul/li.
Preferred Qualifications: also list.
Benefits: we have a sentence describing benefits; could be
- for any list of duties/requirements/benefits. The duties are not a list but a description; we could keep as