Executive Assistant to the CEO
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate (EEO, fraud notice, etc). Also remove "How We Work Together", "A Note On Pace", maybe keep if substantive? It's about work style but not required headings. Could be omitted as not matching headings.
We need to include Pay section with compensation range.
We need to include Schedule? Not present, so omit.
Benefits? Not present, omit.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay.
But we need to decide what goes where.
About the role: paragraph from "About The Role" section.
Responsibilities: list from "What You'll Do".
Requirements: maybe "What You’ve Done" (mandatory experience). That's 3+ years experience etc.
Qualifications: maybe "Nice to Have" (optional). Could also include "AI-native" etc but those are in requirements. We'll treat Nice to Have as Qualifications.
Skills: maybe extract skills like "detail-oriented", "strong writer", "proactive communication", "travel", "calendar management", etc. But we must not invent. Could list skills mentioned: "detail-oriented AF", "natural anticipator", "excellent operator", "strong, clean writer", "willing and able to travel frequently", "proficiency with Zoom, Slack, Google Suite, HubSpot, DocuSign, Asana". Those are in Nice to Have. Could put them under Skills.
But we must not duplicate content. We'll keep responsibilities as list, requirements as list, qualifications as list (nice to have), skills as list (maybe combine with qualifications? But we need separate headings). We'll try to allocate.
Better: Use Requirements for mandatory experience (3+ years, AI-native, detail-oriented, anticipator, operator, writer, travel willingness). Qualifications for nice-to-have (experience supporting CEO, multiple hats, proficiency with tools). Skills could be extracted from both but we might just put skills under Qualifications? However instructions: Use headings only when posting has real specific content for it. If we put skills heading but content is just repeating, maybe okay if we have specific content. We have specific skills: "proficiency with Zoom, Slack, Google Suite, HubSpot, DocuSign, Asana". Also "strong, clean writer". Could be skills.
Thus we can have Skills section listing those.
Let's extract:
Mandatory (What You’ve Done):
- 3+ years of experience as an Executive Assistant, Chief of Staff, or similar operator supporting executives at startups.
- AI-native: you use AI tools daily and are always looking for new and simpler ways to improve your work.
- Detail-oriented AF. We mean it. You spot typos, ace tests, move fast, and do it in a way that makes others marvel.
- A natural anticipator with high discretion: you see what's needed and handle it before being asked, you come with recommendations rather than just questions, and you treat confidential information with absolute professionalism.
- An excellent operator: you manage competing priorities, follow through without reminders, communicate proactively when things change, and keep important work from falling through the cracks.
- A strong, clean writer: you draft concise communications in active voice, catch errors others miss, and take pride in the craft of clear writing.
- Willing and able to travel frequently on short notice with the CEO to conferences, investor meetings, offsites, and other events.
Nice to Have:
- Experience supporting a CEO, founder, or senior executive at a high-growth startup.
- Experience wearing multiple hats across operations, events, office management, or founder support.
- Proficiency with Zoom, Slack, Google Suite, HubSpot, DocuSign, and Asana.
- Comfort operating in Slack-heavy, AI-forward, high-urgency environments.
Skills could be: proficiency with tools, strong writer, detail-oriented, anticipator, operator, travel, etc. But we already have those in requirements. To avoid duplication, maybe we put skills as the tool proficiencies and writer etc. But we risk duplication. However instructions: preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's present in posting? It might be considered repeating but not inventing. It's okay to repeat if it's in posting. But we should try to avoid unnecessary duplication but not required.
We could assign:
- Responsibilities: list from What You'll Do.
- Requirements: list from What You’ve Done (mandatory).
- Qualifications: list from Nice to Have (optional).
- Skills: maybe we can list specific technical proficiencies (Zoom, Slack, Google Suite, HubSpot, DocuSign, Asana) and "strong, clean writer". But those are also in Nice to Have and Requirements. Might be okay.
Pay: compensation range.
Let's craft HTML.
We'll start with
About the role
then ...
.
Responsibilities: Responsibilities
- ...
Requirements: Requirements
- ...
Qualifications: Qualifications
- ...
Skills: Skills
- ...
Pay: Pay
$140K - $200K
We must not include schedule or benefits.
Now write content.
About the role paragraph: "You'll work directly with the CEO and Co-founder as her operational right hand, managing everything from calendar and travel to meeting prep, communications, and office operations. This is a high-visibility role for someone who is fast, precise, highly discreet, and energized by working closely with a founder who moves quickly, communicates directly, and cares deeply about details. Your ability to anticipate needs, bring order to ambiguity, and keep the CEO focused on the highest-impact work will directly affect how quickly we scale. Travel with the CEO is a regular part of the job."
That's the prose.
Responsibilities list items from "What You'll Do":
- Own the CEO's calendar: schedule meetings, protect focus time, manage competing priorities, and make sure her time maps to the highest-impact work.
- Serve as the CEO's communication hub: triage Slack and email, surface what needs attention, draft responses in her voice, and track next steps through completion.
- Coordinate travel logistics and frequently travel with the CEO to provide real-time support at conferences, investor meetings, offsites, and other events.
- Drive meeting operations: set agendas, prepare briefing materials, ensure every meeting has the right context and Zoom link, take notes, and track follow-ups.
- Support key initiatives with research, data analysis, progress tracking, and clear summaries that help the CEO make faster decisions.
- Run the San Mateo office: greet visitors, prep meeting rooms, keep the space tidy and high-functioning, and collaborate with the workplace manager once hired.
- Build and improve lightweight systems that reduce CEO drag, create clarity, and help the company move faster.
Requirements list from "What You’ve Done":
- 3+ years of experience as an Executive Assistant, Chief of Staff, or similar operator supporting executives at startups.
- AI-native: you use AI tools daily and are always looking for new and simpler ways to improve your work.
- Detail-oriented AF. We mean it. You spot typos, ace tests, move fast, and do it in a way that makes others marvel.
- A natural anticipator with high discretion: you see what's needed and handle it before being asked, you come with recommendations rather than just questions, and you treat confidential information with absolute professionalism.
- An excellent operator: you manage competing priorities, follow through without reminders, communicate proactively when things change, and keep important work from falling through the cracks.
- A strong, clean writer: you draft concise communications in active voice, catch errors others miss, and take pride in the craft of clear writing.
- Willing and able to travel frequently on short notice with the CEO to conferences, investor meetings, offsites, and other events.
Qualifications list from "Nice to Have":
- Experience supporting a CEO, founder, or senior executive at a high-growth startup.
- Experience wearing multiple hats across operations, events, office management, or founder support.
- Proficiency with Zoom, Slack, Google Suite, HubSpot, DocuSign, and Asana.
- Comfort operating in Slack-heavy, AI-forward, high-urgency environments.
Skills list: we could list specific technical proficiencies and writing skill. But we already have proficiency in qualifications. To avoid duplication, maybe we list skills like "strong, clean writer", "detail-oriented", "anticipator", "operator". But those are in requirements. Hmm.
Maybe we can omit Skills section if no distinct content not already covered. But we need to decide: The instruction: "Prefer a few substantive sections over many thin ones." If Skills would be thin or duplicate, better to omit. However we have a heading Skills; we need real specific content for it. We could extract skills like "proficiency with Zoom, Slack, Google Suite, HubSpot, DocuSign, Asana" and "strong, clean writer". Those are specific. Even if they appear elsewhere, it's okay to repeat. But we might be duplicating content; still preserving all substantive information (not removing). Duplication is not removing information, it's repeating. It's allowed? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication. So we can include Skills with those items.
Thus Skills list:
- Proficiency with Zoom, Slack, Google Suite, HubSpot, DocuSign, and Asana.
- Strong, clean writer: drafting concise communications in active voice, catching errors, taking pride in clear writing.
- Detail-oriented: spotting typos, acing tests, moving fast while impressing others.
- Natural anticipator with high discretion: seeing needs before being asked, providing recommendations, handling confidential information professionally.
- Excellent operator: managing competing priorities, following through without reminders, proactive communication, preventing work from falling through cracks.
- Willing and able to travel frequently on short notice.
But that's basically repeating requirements. Might be too thin? But it's still substantive.
Given the instruction to prefer few substantive sections over many thin ones, maybe better to combine Skills into Qualifications or Requirements. But we already have Qualifications (nice to have) and Requirements (mandatory). Skills could be merged into either. However the instruction says to use headings only when posting has real specific content for it. If we put Skills heading, we need to have content that is not just filler
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate (EEO, fraud notice, etc). Also remove "How We Work Together", "A Note On Pace", maybe keep if substantive? It's about work style but not required headings. Could be omitted as not matching headings. We need to include Pay section with compensation range. We need to include Schedule? Not present, so omit. Benefits? Not present, omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. But we need to decide what goes where. About the role: paragraph from "About The Role" section. Responsibilities: list from "What You'll Do". Requirements: maybe "What You’ve Done" (mandatory experience). That's 3+ years experience etc. Qualifications: maybe "Nice to Have" (optional). Could also include "AI-native" etc but those are in requirements. We'll treat Nice to Have as Qualifications. Skills: maybe extract skills like "detail-oriented", "strong writer", "proactive communication", "travel", "calendar management", etc. But we must not invent. Could list skills mentioned: "detail-oriented AF", "natural anticipator", "excellent operator", "strong, clean writer", "willing and able to travel frequently", "proficiency with Zoom, Slack, Google Suite, HubSpot, DocuSign, Asana". Those are in Nice to Have. Could put them under Skills. But we must not duplicate content. We'll keep responsibilities as list, requirements as list, qualifications as list (nice to have), skills as list (maybe combine with qualifications? But we need separate headings). We'll try to allocate. Better: Use Requirements for mandatory experience (3+ years, AI-native, detail-oriented, anticipator, operator, writer, travel willingness). Qualifications for nice-to-have (experience supporting CEO, multiple hats, proficiency with tools). Skills could be extracted from both but we might just put skills under Qualifications? However instructions: Use headings only when posting has real specific content for it. If we put skills heading but content is just repeating, maybe okay if we have specific content. We have specific skills: "proficiency with Zoom, Slack, Google Suite, HubSpot, DocuSign, Asana". Also "strong, clean writer". Could be skills. Thus we can have Skills section listing those. Let's extract: Mandatory (What You’ve Done): - 3+ years of experience as an Executive Assistant, Chief of Staff, or similar operator supporting executives at startups. - AI-native: you use AI tools daily and are always looking for new and simpler ways to improve your work. - Detail-oriented AF. We mean it. You spot typos, ace tests, move fast, and do it in a way that makes others marvel. - A natural anticipator with high discretion: you see what's needed and handle it before being asked, you come with recommendations rather than just questions, and you treat confidential information with absolute professionalism. - An excellent operator: you manage competing priorities, follow through without reminders, communicate proactively when things change, and keep important work from falling through the cracks. - A strong, clean writer: you draft concise communications in active voice, catch errors others miss, and take pride in the craft of clear writing. - Willing and able to travel frequently on short notice with the CEO to conferences, investor meetings, offsites, and other events. Nice to Have: - Experience supporting a CEO, founder, or senior executive at a high-growth startup. - Experience wearing multiple hats across operations, events, office management, or founder support. - Proficiency with Zoom, Slack, Google Suite, HubSpot, DocuSign, and Asana. - Comfort operating in Slack-heavy, AI-forward, high-urgency environments. Skills could be: proficiency with tools, strong writer, detail-oriented, anticipator, operator, travel, etc. But we already have those in requirements. To avoid duplication, maybe we put skills as the tool proficiencies and writer etc. But we risk duplication. However instructions: preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's present in posting? It might be considered repeating but not inventing. It's okay to repeat if it's in posting. But we should try to avoid unnecessary duplication but not required. We could assign: - Responsibilities: list from What You'll Do. - Requirements: list from What You’ve Done (mandatory). - Qualifications: list from Nice to Have (optional). - Skills: maybe we can list specific technical proficiencies (Zoom, Slack, Google Suite, HubSpot, DocuSign, Asana) and "strong, clean writer". But those are also in Nice to Have and Requirements. Might be okay. Pay: compensation range. Let's craft HTML. We'll start with
About the role
then...
. Responsibilities:Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
Skills
- ...
Pay
$140K - $200K
We must not include schedule or benefits. Now write content. About the role paragraph: "You'll work directly with the CEO and Co-founder as her operational right hand, managing everything from calendar and travel to meeting prep, communications, and office operations. This is a high-visibility role for someone who is fast, precise, highly discreet, and energized by working closely with a founder who moves quickly, communicates directly, and cares deeply about details. Your ability to anticipate needs, bring order to ambiguity, and keep the CEO focused on the highest-impact work will directly affect how quickly we scale. Travel with the CEO is a regular part of the job." That's the prose. Responsibilities list items from "What You'll Do": - Own the CEO's calendar: schedule meetings, protect focus time, manage competing priorities, and make sure her time maps to the highest-impact work. - Serve as the CEO's communication hub: triage Slack and email, surface what needs attention, draft responses in her voice, and track next steps through completion. - Coordinate travel logistics and frequently travel with the CEO to provide real-time support at conferences, investor meetings, offsites, and other events. - Drive meeting operations: set agendas, prepare briefing materials, ensure every meeting has the right context and Zoom link, take notes, and track follow-ups. - Support key initiatives with research, data analysis, progress tracking, and clear summaries that help the CEO make faster decisions. - Run the San Mateo office: greet visitors, prep meeting rooms, keep the space tidy and high-functioning, and collaborate with the workplace manager once hired. - Build and improve lightweight systems that reduce CEO drag, create clarity, and help the company move faster. Requirements list from "What You’ve Done": - 3+ years of experience as an Executive Assistant, Chief of Staff, or similar operator supporting executives at startups. - AI-native: you use AI tools daily and are always looking for new and simpler ways to improve your work. - Detail-oriented AF. We mean it. You spot typos, ace tests, move fast, and do it in a way that makes others marvel. - A natural anticipator with high discretion: you see what's needed and handle it before being asked, you come with recommendations rather than just questions, and you treat confidential information with absolute professionalism. - An excellent operator: you manage competing priorities, follow through without reminders, communicate proactively when things change, and keep important work from falling through the cracks. - A strong, clean writer: you draft concise communications in active voice, catch errors others miss, and take pride in the craft of clear writing. - Willing and able to travel frequently on short notice with the CEO to conferences, investor meetings, offsites, and other events. Qualifications list from "Nice to Have": - Experience supporting a CEO, founder, or senior executive at a high-growth startup. - Experience wearing multiple hats across operations, events, office management, or founder support. - Proficiency with Zoom, Slack, Google Suite, HubSpot, DocuSign, and Asana. - Comfort operating in Slack-heavy, AI-forward, high-urgency environments. Skills list: we could list specific technical proficiencies and writing skill. But we already have proficiency in qualifications. To avoid duplication, maybe we list skills like "strong, clean writer", "detail-oriented", "anticipator", "operator". But those are in requirements. Hmm. Maybe we can omit Skills section if no distinct content not already covered. But we need to decide: The instruction: "Prefer a few substantive sections over many thin ones." If Skills would be thin or duplicate, better to omit. However we have a heading Skills; we need real specific content for it. We could extract skills like "proficiency with Zoom, Slack, Google Suite, HubSpot, DocuSign, Asana" and "strong, clean writer". Those are specific. Even if they appear elsewhere, it's okay to repeat. But we might be duplicating content; still preserving all substantive information (not removing). Duplication is not removing information, it's repeating. It's allowed? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication. So we can include Skills with those items. Thus Skills list: - Proficiency with Zoom, Slack, Google Suite, HubSpot, DocuSign, and Asana. - Strong, clean writer: drafting concise communications in active voice, catching errors, taking pride in clear writing. - Detail-oriented: spotting typos, acing tests, moving fast while impressing others. - Natural anticipator with high discretion: seeing needs before being asked, providing recommendations, handling confidential information professionally. - Excellent operator: managing competing priorities, following through without reminders, proactive communication, preventing work from falling through cracks. - Willing and able to travel frequently on short notice. But that's basically repeating requirements. Might be too thin? But it's still substantive. Given the instruction to prefer few substantive sections over many thin ones, maybe better to combine Skills into Qualifications or Requirements. But we already have Qualifications (nice to have) and Requirements (mandatory). Skills could be merged into either. However the instruction says to use headings only when posting has real specific content for it. If we put Skills heading, we need to have content that is not just filler