Executive Assistant

We need to output HTML fragment with sections for headings present: About the role (but note: The page already shows job title, we should not repeat job title as heading. The posting includes "About Nooks" and "About The Role". We should not repeat job title as heading. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we need to include headings for sections that have real content. We have content: About Nooks (company description) maybe not needed? The instruction says use headings for sections like About the role, Responsibilities, etc. "About Nooks" is not listed but could be considered "About the role"? Actually there is "About Nooks" describing company. Could be considered "About the role"? Not exactly. But we can include a section "About Nooks" as maybe not required but we can include as a heading? The instruction says use h3 for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but we should follow the pattern. Probably we should include "About Nooks" as a heading? Might be considered "About the role"? Actually "About The Role" is present. So we should have heading "About The Role". Also we have "Key Responsibilities" which can be Responsibilities. Also "What Success Looks Like In This Role" maybe not needed. Also "Cross-Functional Expectations". Also "The Skillset" which could be Skills/Qualifications. Also "Preferred Background". Also "Eligibility & Clearance". Also "Salary Range". Also maybe "Benefits"? Not present. So we should include sections where there is real content: About The Role, Responsibilities, Skills/Qualifications (maybe combine Skillset and Preferred Background), Eligibility & Clearance, Salary Range. Also maybe "Cross-Functional Expectations" could be part of Responsibilities? But we can include as its own section if content is substantive. The instruction: Prefer a few substantive sections over many thin ones. So we might combine some. We need to use

• for any list of duties/requirements/benefits. So for responsibilities we should list as
  • . For skillset we can list as
    • . For eligibility maybe not a list. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to output only HTML fragment, no /, no markdown fences. Let's extract content: About Nooks: description of company. Could be included as a paragraph under maybe "About Nooks" heading? Not required but we can include as a paragraph maybe under a heading "About Nooks". However instruction says use h3 for section headings (e.g. About the role...). It doesn't say we cannot have other headings, but we should likely include "About Nooks" as a heading? The example list includes About the role, not About the company. But we could still include it as a heading; it's not prohibited. However to be safe, we could treat "About Nooks" as part of the role description? Might be considered extraneous. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it." It doesn't forbid other headings. So we can include "About Nooks" as a heading if we want. But we need to preserve all substantive information. So we should include that paragraph. Let's structure:

      About Nooks

      ... description ...

      About The Role

      ... description ...

      Responsibilities

      • ... each bullet ...
      We need to capture all responsibilities bullet points from "Key Responsibilities" section. Let's extract them: - Own the CEO’s calendar and inbox, scheduling across a West Coast principal and a distributed leadership team. - Present logistical decision in a way that quickly forces clarity and simplicity, providing ease to planning the week ahead. - Derisk the CEO’s calendar of conflicts, missed meetings, or moderate priorities being repeatedly or extensively bumped. - Coordinate frequent domestic travel, often multi-site within a single trip, anticipating what each trip requires before it is requested. - Manage expense reporting and light financial administration to a current and clean standard. - Manage conference registrations, dining reservations, event coordination, property visits, and other activities during travel. - Close the gap between what the CEO says is important and what his calendar and to-do list actually reflect, aggressively protecting the important. - Read how priorities move across a week, whether stated plainly or visible only in a shift of tone or attention, and reshape the calendar, preparation, and follow-ups to match. - Flag and help reconcile misaligned prioritization in the day to day, surfacing genuine conflicts rather than resolving them silently. - Protect the CEO’s focus by deciding what reaches him, what waits, and what routes to someone else. - Partner with Chief of Staff to delegate meetings and tasks that are better supported by other leaders. - Serve as the system of record for open items, document flow, decisions, and commitments, working with Chief of Staff to drive them to conclusion. - Move documents through review and signature so nothing stalls from inattention. - Deliver context to the people whose decisions depend on it, acting as a connector rather than only a filter. - Work with Chief of Staff to ensure priority discussion topics are surfaced ahead of critical meetings with internal leadership and external stakeholders. - Build the CEO’s preparation for leadership, customer, board, and government meetings so he arrives knowing what he needs to know. - Capture decisions, translate them into owned follow-ups, and support those follow-ups to completion. - Execute projects scoped and assigned by the Chief of Staff, delivering defined work on time and to standard. That's many. We'll keep them as list items. Next, maybe "What Success Looks Like In This Role" could be considered part of Responsibilities or separate? It's descriptive of success metrics. Could be its own section "Success Metrics". But instruction prefers few substantive sections. Could combine into Responsibilities? Might be okay to have a separate section "What Success Looks Like". But we need to decide. We also have "Cross-Functional Expectations". Could be its own section. We have "The Skillset" (requirements) and "Preferred Background". Could combine into "Qualifications" or "Skills". We'll make a section "Qualifications" with required and preferred. We have "Eligibility & Clearance". We'll make a section "Eligibility". We have "Salary Range". We'll make a section "Pay". We must not include sections with filler like "commensurate with experience". Salary range is present. We must not include Benefits or Schedule unless present. Not present. Thus sections: About Nooks, About The Role, Responsibilities, Qualifications, Eligibility, Pay. Possibly also Cross-Functional Expectations and What Success Looks Like could be merged into Responsibilities or omitted? But they contain substantive info not covered elsewhere. Could add as separate sections but that increases number. The instruction: Prefer a few substantive sections over many thin ones. So we might incorporate Cross-Functional Expectations and What Success Looks Like into Responsibilities or a new section "Expectations". But we already have Responsibilities covering duties; Cross-Functional Expectations is about relationships, could be part of Responsibilities. What Success Looks Like is about outcomes, could be part of Responsibilities or a separate "Performance Expectations". To keep few sections, we could add a section "Expectations" that includes both Cross-Functional Expectations and What Success Looks Like. But we need to decide. Let's see content: Cross-Functional Expectations paragraph: describes working with CEO, Chief of Staff, ELT, etc. What Success Looks Like: bullet points about outcomes. We could make a section "Expectations" with two subparts? But we only allowed

      headings and

      • for lists. We could have a paragraph for cross-functional expectations and a list for success looks like. Thus we could have:

        Expectations

        Cross-functional expectations paragraph...

        • ... success looks like bullets ...
        That would be one section. Thus final sections: About Nooks, About The Role, Responsibilities, Qualifications, Expectations, Eligibility, Pay. That's 7 sections, maybe okay. Now we need to extract exact text for each. Let's copy paragraphs exactly as in posting, removing boilerplate. About Nooks: "About Nooks Nooks is pioneering Classified-Infrastructure-as-a-Service (CIaaS) — designing, building, and operating Sensitive Compartmented Information Facilities (SCIFs) and other secured, classified environments for the defense and national security community. We work with the agencies, contractors, and mission-driven organizations that keep the nation safe, delivering the physical infrastructure that makes classified work possible. We’re growing fast, operating across multiple markets, and building a company that takes both the mission and the business seriously." We need to ensure no extra spaces. We'll put in

        . About The Role: "About The Role You will own the CEO’s calendar, inbox, travel, and follow-through, and you will do it at an altitude most executive support roles never reach. Most of these roles are measured on whether the calendar is accurate. This one is measured on whether it is right. The CEO moves quickly across customers, government stakeholders, investors, and the team. New priorities arise in the middle of a conversation or the end of a long travel day. They do not always find their own way onto a calendar or into a document queue. Your job is to close the distance between what the CEO has said matters and what his week actually reflects. You will report administratively to the Chief of Staff and support the CEO directly and Executive Leadership Team indirectly. You’ll partner closely with the Chief of Staff to keep the CEO’s time and Nooks’ operating priorities aligned. Be clear-eyed about the environment you are stepping into. While this role has defined ownership areas, priorities shift quickly and often without announcement. What looked settled on Monday can be reordered by Tuesday night, and you will be expected to register that shift and adjust Thursday accordingly without being told to. You will support a demanding principal at a company that is building fast, and you will step into whatever needs to be done. The people who thrive in this seat are unusually observant, hold their read of a situation loosely enough to revise it, and are comfortable acting on incomplete information rather than waiting for certainty that is not coming." We need to ensure we keep the text exactly. Might have line breaks; we can keep as a single paragraph. Responsibilities: list items as extracted. Qualifications: combine "The Skillset" and "Preferred Background". Let's extract: The Skillset bullet points: - Five or more years in an executive assistant or executive operations role supporting a chief executive or multiple senior executives. - A demonstrated track record of setting tactical priority order and acting on it without waiting for direction. - Proven ability to notice unstated shifts in priority or attention and adjust before being asked. - Experience representing an executive with board members, investors, or senior external stakeholders. - Absolute discretion with sensitive personnel, financial, and strategic information. - Availability for weekday after-hours support, comfort coordinating complex domestic travel, and residence in the Mountain or Central time zone. Preferred Background: - Background in a high-growth startup, defense, or national security environment. - Experience supporting a Program Management Office (PMO) or a comparable project tracking function. - Experience supporting a principal located in a different time zone from the broader team. We'll list all as

      • under Qualifications. Expectations: cross-functional expectations paragraph and success looks like list. Cross-Functional Expectations paragraph: "You will work most closely with the CEO, whom you support directly, and with the Chief of Staff, who is both your manager and your closest working partner in keeping the CEO’s time aligned to Nooks’ priorities. In doing so,