Scheduler

The user wants me to reformat a job posting into clean semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections: - Company Description (but this is more of an intro, not a section heading per rules) - Job Description (overview) - Scope of Responsibilities (with sub-sections: Calendar & Scheduling Support, Travel Booking & Logistics, Expense Management) - Qualifications (with U.S. Citizenship required and Required Skills) The rules say: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

• for lists - Use

  for prose - Don't repeat job title as heading - Don't put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (EEO, equal opportunity, scam warnings, duplicated lines, application instructions) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no html/body, no markdown code fences Looking at the content: - Company Description: This is prose about the company. Could be "About the company" or "About the role"? The rules mention "About the role" as example heading. But this is company description. I'll use "About the company" or maybe just include as intro paragraph? The rules say use h3 for section headings like "About the role". Since there's a "Job Description" section that describes the role, I'll use "About the role" for that prose. - Job Description: The first paragraph after "Job Description" is a prose overview of the role. That fits "About the role". - Scope of Responsibilities: This has three sub-sections with bullet points. This maps to "Responsibilities". I'll make an h3 "Responsibilities" and then maybe sub-headings? But rules say use h3 for section headings. Could use h3 for each sub-section? The example headings include "Responsibilities" as a section. I think I should have one "Responsibilities" h3 and then use sub-lists or maybe h4? But rules only mention h3. I'll use h3 for each major responsibility area? The rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So "Responsibilities" is a section heading. The sub-sections (Calendar & Scheduling Support, Travel Booking & Logistics, Expense Management) are part of Responsibilities. I could make them h3 as well? But that would be multiple h3s. The example shows "Responsibilities" as one heading. I'll make "Responsibilities" as h3, then each sub-area as a sub-heading? But only h3 allowed. Could use

  but not specified. Safer to make each sub-area an h3? The rules say "use

  for section headings". It doesn't forbid multiple h3s. I'll treat each major responsibility area as a section heading: "Calendar & Scheduling Support", "Travel Booking & Logistics", "Expense Management". But they are under "Scope of Responsibilities". The posting says "Scope of Responsibilities" then lists three with bullet points. I'll create an h3 "Responsibilities" and then for each sub-area, maybe a

  ? But the instruction says use h3 for section headings. I think I'll make each sub-area an h3, as they are distinct sections. However, the example list includes "Responsibilities" as a heading. I'll follow the pattern: have an h3 "Responsibilities" and then use

  for the bullet points, but the bullet points are grouped under sub-headings. The content has sub-headings like "Calendar & Scheduling Support — Primary Responsibility" then bullet points. I'll keep those sub-headings as maybe

  or just bold? But the rule says use h3 for section headings. I'll use h3 for each of those sub-sections, as they are substantial. - Qualifications: This includes "U.S. Citizenship is required" and "Required Skills" with a list. This maps to "Qualifications" or "Requirements". The example includes both "Requirements" and "Qualifications". I'll use "Qualifications" as h3 and include the citizenship requirement and skills list. - There's duplicated EEO statement at the end. Remove boilerplate. - No Pay, Schedule, Benefits sections mentioned (except "full-time position based in Arlington, VA office. This role may require up to 10% travel." That's schedule/location info. Could be a "Schedule" section? The rules say never create Schedule section unless posting actually states them. It does state location and travel. But "Schedule" might refer to work schedule. The posting says "full-time position based in our Arlington, VA office. This role may require up to 10% travel." That's more about location and travel. Could be "Location & Travel" but not in example headings. The example headings include "Schedule". I'll include a "Schedule" section with that info? But the rule says never create Schedule section unless posting actually states them. It does state work arrangement. I'll include a "Schedule" section with that prose. - Benefits: Not mentioned. Skip. - Pay: Not mentioned. Skip. - Skills: The "Required Skills" list could be a "Skills" section. But the example includes "Skills" as a heading. However, the qualifications section already includes skills. I'll keep under Qualifications. Now, structure: 1. About the role (h3) - the job description prose. 2. Responsibilities (h3) - but with sub-sections. I'll make each sub-section an h3? Let's see: The posting has "Scope of Responsibilities" then three bullet groups with sub-headings. I'll create h3 for each sub-heading: "Calendar & Scheduling Support", "Travel Booking & Logistics", "Expense Management". That seems appropriate. 3. Qualifications (h3) - includes citizenship and required skills list. 4. Schedule (h3) - location and travel. But the rules say "Prefer a few substantive sections over many thin ones." So maybe combine Responsibilities into one section with sub-lists? But the sub-headings are meaningful. I'll keep them as h3. Also, the company description at top: "Company Description Air is the leader..." That's about the company. Could be "About the company" but not in example headings. The example includes "About the role". I'll include it as a prose paragraph before sections? Or make an h3 "About the company". The rules say use h3 for section headings like "About the role". I'll add "About the company" as h3. But the user said "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Scheduler". Not in the text provided? The posting starts with "Company Description". The job title might be elsewhere. I'll not include job title heading. Now, write HTML. I'll output:

  About the company

  Air is the leader in Enterprise Readiness. Our mission is to establish readiness as a real-time condition that is continuously achieved. Today, a dangerous Readiness Gap exists between what the front line needs and what is delivered. Our AI-native platform, Air Enterprise Readiness, aligns development, production, delivery, and sustainment into one coordinated execution system for government agencies and industrial suppliers. By revealing true capacity, exposing real constraints, coordinating resources, and executing at the speed of operational demands, the front line gets what it needs to succeed.

  About the role

  We are seeking an experienced Scheduler, to support 4-5 Executives, serving as a critical partner in enabling leadership effectiveness at a rapidly growing, mission-driven company. This role is ideal for someone who thrives in a high-growth environment, anticipates needs before they arise, and can seamlessly manage friction that can distract leaders from their highest-priority work. In order to do this job well you must be highly organized without being rigid, proactive without overstepping, and comfortable operating behind the scenes. You are someone who genuinely enjoys the craft of executive support. You thrive in a support capacity and understand that no detail is too small when it comes to enabling exceptional execution and advancing a critical mission. You take ownership, communicate clearly, and have a strong sense of urgency when it matters. Most importantly, you understand that excellent executive support is about more than completing tasks—it’s managing competing priorities and frequent changes, making sound decisions to protect executives’ time by creating the conditions for the Executive Team to operate at their best. This is a full-time position based in our Arlington, VA office. This role may require up to 10% travel.

  Calendar & Scheduling Support

  • Manage frequent calendar changes and last-minute requests with speed, professionalism, and minimal disruption.
  • Identify and resolve scheduling conflicts, using sound judgment and appropriate tradeoffs.
  • Coordinate recurring meetings, leadership meetings, 1:1s, interviews, customer meetings, and other high-priority engagements, ensuring schedules are organized, efficient, and aligned to business priorities.
  • Serve as a professional point of contact for internal and external stakeholders seeking time with supported executives.
  • Monitor calendars for gaps, conflicts, overbooking, and inefficient scheduling, proactively making recommendations and adjustments.
  • Track scheduling-related action items, commitments, and follow-ups to ensure nothing falls through the cracks.

  Travel Booking & Logistics

  • Coordinate end-to-end domestic and international travel that account for executive preferences including flights, hotels and ground transportation.
  • Develop a strong understanding of individual executive travel preferences and proactively apply them to future bookings.
  • Build travel schedules that account for meeting commitments, time zones, and realistic travel time.
  • Manage changes, cancellations, delays, and unexpected travel issues quickly and proactively.

  Expense Management

  • Own the expense reporting process for executives, ensuring expenses are submitted accurately, completely, and on time.
  • Partner with the Finance team and executives to address expense questions, reimbursements, and policy requirements.
  • Maintain organized records and proactively follow up on outstanding expense items.

  Qualifications

  U.S. Citizenship is required.

  • Demonstrated experience managing 4+ executive calendars or a similarly complex scheduling environment.
  • Strong expertise in complex calendar management, including scheduling across multiple time zones.
  • Significant experience coordinating domestic and international executive travel.
  • Experience managing executive expenses and working with Finance and expense management systems (Ramp preferably).
  • Experience working in ambiguous and fast-paced environments.
  • Experience with AI tools (e.g. Google Gemini, Claude) and embedding them to operational and organizational work.
  • Capable of producing high-quality content on short deadlines.
  • Fast learner and able to work independently with minimal supervision.
  • Exceptional attention to detail; ability to consistently produce timely and error-free work.
  • Excellent written and verbal communication skills.
  • Superb judgment and proven ability to handle confidential information.
  • Highly proactive and resourceful self-starter with a demonstrated ability to anticipate needs, solve problems independently, and operate effectively with minimal supervision.
  • Enthusiastic team member with a positive disposition and attitude.
  • Experience using AI tools such as Google Gemini, Claude, or similar tools to improve productivity and administrative workflows.