Executive Assistant II Deputy Clerk

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job posting. Job Title: Executive Assistant II Deputy Clerk (but we should not repeat as heading). Department: Communications Public Information. Reports To: Chief Communication Officer. FLSA Status: Non Exempt. Work Calendar: All 12 Month Staff. Salary Scale: Clerical Salary Scale. Job Summary And Purpose: description. Work Objectives/Essential Functions: list of duties. Education and Experience: required and preferred. Industry Licensure or Certifications (Required/Preferred). Additional Knowledge, Skills, And Abilities. Core Expectations of All Stafford Schools Employees. Weight Demands (physical demands table). Physical Demands table. Classification Details (HR) includes Job Family, Calendar, Pay Structure, Position, FLSA Status, Job Grade, Job Code, Status. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. There's none explicit. We need to preserve all substantive info. We need to decide sections. Potential sections: - About the role (could combine Job Summary and Purpose, maybe Department, Reports To, etc.) - Responsibilities (Work Objectives/Essential Functions) - Requirements (Education and Experience, Licensure/Certifications) - Qualifications (maybe same as Requirements? But we can combine.) - Skills (Additional Knowledge, Skills, And Abilities + Core Expectations? Could be separate.) - Benefits (none given, so omit) - Pay (Salary Scale given: Clerical Salary Scale. That's substantive? It says Salary Scale: Clerical Salary Scale. Not a specific number, but it's a scale. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Salary Scale: Clerical Salary Scale. That is a statement of pay structure, albeit not a number. Should we include Pay section? It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Salary Scale. So we can include Pay section with that info. - Schedule: Work Calendar: All 12 Month Staff. That's a schedule statement. So we can include Schedule section. We need to avoid filler like "commensurate with experience". Not present. We need to use

for section headings. We need to use

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

  for prose. We need to not repeat job title as heading. We need to not put Job ID/requisition numbers as headings; fold minor metadata into short

  or drop it. We need to preserve all substantive info. We need to output only HTML fragment. Let's structure:

  About the role

  Department: Communications Public Information. Reports To: Chief Communication Officer. FLSA Status: Non Exempt. Work Calendar: All 12 Month Staff. Salary Scale: Clerical Salary Scale.

  Job Summary And Purpose: The Executive Assistant provides clerical and operational support to the Chief Communications Officer and the Department of Communications. This role ensures smooth department operations, accurate recordkeeping, and timely communication with internal and external stakeholders. The successful candidate demonstrates strong attention to detail, excellent written communication skills, and professionalism when interacting with colleagues and the public.

  But maybe we should separate summary into its own paragraph. Alternatively, we could have About the role include summary and purpose. Then Responsibilities:

  Responsibilities

  • Prepares, drafts, edits, and distributes written materials across newsletters, emails, websites, and other communications channels.
  • Maintains archives, databases, and administrative systems to ensure accurate and accessible records.
  • Welcomes, screens, and assists visitors and callers, addressing inquiries or directing requests to appropriate staff.
  • Processes and tracks purchase orders, reconciles financial records, and provides documentation to auditors or the Department of Finance.
  • Collects, verifies, and compiles data for reports and records, ensuring accuracy and compliance with Stafford Schools standards.
  • Supports department operations and initiatives by coordinating workflow, improving administrative systems, and assisting colleagues as needed.
  • Serves as Deputy Clerk for School Board meetings.
  • Engages in professional development, models professionalism and collaboration, and adheres to all District and School Board policies.
  Requirements: Education and Experience, Licensure/Certifications. We could have

  Requirements

  with subpoints? But we need to use
  • for any list. So we can list each requirement as
  • . But we also have preferred vs required. We need to preserve all info. Could separate required and preferred within list items with notation. Let's list: - Education Attainment (Required): High school diploma or equivalent - Education Attainment (Preferred): Associate’s degree from an accredited college or university - Relevant Experience (Required): Two (2) years of professional administrative or clerical experience - Relevant Experience (Preferred): Experience in a K-12 school division and/or a placement similar to an educational setting. Prior experience in communications support. - Industry Licensure or Certifications (Required): Valid Virginia Driver’s License - Industry Licensure or Certifications (Preferred): (none listed) Actually there is no preferred licensure listed; just "Additional Knowledge, Skills, And Abilities" later. So we can omit preferred licensure if none. We could also include "Additional Knowledge, Skills, And Abilities" under Skills section. Qualifications: maybe same as Requirements? But we could have Qualifications section for Education and Experience and Licensure. But we already have Requirements. To avoid duplication, we could combine Requirements and Qualifications into one section called "Qualifications". But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should have both Requirements and Qualifications if content exists. However, we need to avoid thin sections. We could put Education and Experience under Requirements, and Licensure/Certifications under Qualifications. Or we could put both under Requirements and leave Qualifications empty (but we must not emit heading with filler). So we need to decide. Better: Requirements: Education and Experience. Qualifications: Licensure and Certifications. Skills: Additional Knowledge, Skills, And Abilities + Core Expectations. Let's do that. Requirements (Education and Experience):
    • Education Attainment (Required): High school diploma or equivalent
    • Education Attainment (Preferred): Associate’s degree from an accredited college or university
    • Relevant Experience (Required): Two (2) years of professional administrative or clerical experience
    • Relevant Experience (Preferred): Experience in a K-12 school division and/or a placement similar to an educational setting. Prior experience in communications support.
    Qualifications (Licensure/Certifications):
    • Industry Licensure or Certifications (Required): Valid Virginia Driver’s License
    Skills: We have "Additional Knowledge, Skills, And Abilities" bullet points (three items) and "Core Expectations of All Stafford Schools Employees" (list of items). We'll combine them into Skills section as a list. List items: - Strong oral and written communication skills, including the ability to present information clearly and facilitate discussions. - Ability to collaborate effectively with staff, leaders, and community partners to achieve shared goals. - Skill in prioritizing tasks, managing multiple initiatives, and adapting to changing needs in a dynamic work environment. - Engage in ongoing professional development relevant to position. - Respond to written and oral requests for information promptly and thoroughly. - Maintain a clean, neat appearance and dress appropriate to position and duties. - Maintain a record of appropriate attendance and punctuality. - Serve as a role model for students, colleagues, and the general public. - Work in close harmony with supervisor(s) and colleagues. - Comply with all division policies and regulations, including but not limited to guidelines for confidentiality and professional conduct, as well as all site-based procedures and protocols. We could also include Weight Demands and Physical Demands maybe under a separate section like "Physical Requirements"? But not in the allowed headings list. The allowed headings are limited to those eight. We could possibly put physical demands under Requirements or Qualifications? But they are not exactly requirements; they are physical demands. The instruction says to use those headings only; we could omit physical demands if no appropriate heading. But we must preserve ALL substantive information. So we need to include them somewhere. Perhaps we can include them under Requirements as additional items, or under Qualifications. Since they are not explicitly listed under those headings, but we can still include them as list items under Requirements or Qualifications. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, but we should use those headings for sections. It doesn't forbid other headings, but says use those for section headings. Likely we should stick to those headings only. So we need to fit physical demands into one of those sections. Perhaps under Requirements (as physical requirements) or Qualifications. I'd put them under Requirements as additional bullet points. Similarly Weight Demands table could be included as list items. Thus Requirements section will include education, experience, licensure? Actually we separated licensure to Qualifications. But we could also put licensure under Requirements. But we already have Qualifications for licensure. Let's keep Qualifications for licensure/certs. Then Requirements will include education, experience, physical demands, weight demands. But we need to avoid too thin sections. Let's see. Requirements: Education and Experience + Physical Demands + Weight Demands. Qualifications: Licensure/Certifications. Skills: Additional Knowledge, Skills, And Abilities + Core Expectations. Pay: Salary Scale: Clerical Salary Scale. Schedule: Work Calendar: All 12 Month Staff. Now we need to format physical demands and weight demands as list items. Physical Demands list from table: - Standing: X (Frequently? Actually table: Physical Demands Rarely Occasionally Frequently; Standing X under Frequently? Let's read: Physical Demands Physical Demands Rarely Occasionally Frequently Standing X Sitting X Walking X Reaching X Turning/Twisting X Balancing/Climbing X Stooping/Kneeling X Crouching/Crawling X It seems each has an X under Frequently? Actually the layout: columns Rarely, Occasionally, Frequently. Then rows: Standing, Sitting, Walking, Reaching, Turning/Twisting, Balancing/Climbing, Stooping/Kneeling, Crouching/Crawling. Under each row there is an X under Frequently column? The snippet shows "Standing X Sitting X Walking X Reaching X Turning/Twisting X Balancing/Climbing X Stooping/Kneeling X Crouching/Crawling X". It seems each has X under Frequently (maybe). So we can interpret as Frequently required for all those. We'll just list them as "Frequently: Standing, Sitting, Walking, Reaching, Turning/Twisting, Balancing/Climbing, Stooping/Kneeling, Crouching/Crawling." Weight Demands table: Weight Demands Weight Demands Rarely Occasionally Frequently Lifting – 1–25 lbs X Lifting – 26–50 lbs X Lifting – 50+ lbs X Carrying – 1–25 lbs X Carrying – 26–50 lbs X Carrying – 50+ lbs X Pushing/Pulling – 1–25 lbs X Pushing/Pulling – 26–50 lbs X Pushing/Pulling – 50+