Executive & Personal Assistant to CEO
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading (the page already shows it). Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting and extract sections.
The posting includes:
- Intro about Appodeal (company description) repeated twice. This is likely "About the company" but not required heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only include those headings if content exists. The "About the role" section is present: "About The Role ...". So we need an About the role
with prose.
Then "Key Responsibilities" -> we can map to Responsibilities heading.
Then "What We're Looking For" includes Experience, Systems and Data, Tools, Soft Skills, Nice to Have. This could be Requirements/Qualifications/Skills. We need to decide which headings to use. The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include sections only when there is real specific content.
We have content for Responsibilities (Key Responsibilities). We have content for Requirements (Experience, Systems and Data, Tools, Soft Skills). Could combine into Requirements heading. Could also separate Qualifications and Skills but we can keep it simple: one Requirements section with sub-lists? The instruction says use - for any list of duties/requirements/benefits. So we can have a
Requirements
with - items.
We also have "How Success Is Measured" maybe could be considered something else but not in allowed headings. Could be omitted or maybe put under Responsibilities? Probably better to omit as not a standard heading. But we need to preserve ALL substantive information; we cannot drop it unless we incorporate into another section. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. Could be placed under a heading like "Performance Expectations" but not allowed. However we could incorporate into Responsibilities or Requirements? The success metrics are about how success measured; could be considered part of Responsibilities? Might be okay to add a section "How Success Is Measured" but not in allowed list. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. But they also say "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could create a section for "How Success Is Measured" if we want, but it's not in the list; risk of being considered not following instruction. Safer to map that content into existing sections, maybe under Responsibilities (as part of what the role entails) or under a new heading "Performance" but not allowed. I'd incorporate into Responsibilities as bullet points about success metrics.
Also we have "Location and Travel" info. Could be placed under a heading "Location" but not in list. Could be incorporated into Responsibilities? Not really. Could be a short paragraph after Responsibilities maybe as a
without heading? The instruction says use
for section headings (list). It doesn't forbid other headings, but says use for section headings (e.g. ...). It may be okay to use other headings but they gave examples. Safer to stick to those headings and put location info in a
after Responsibilities maybe under a heading "About the role"? But that's already used.
We could treat location as part of "About the role" description. But we already have About the role section describing role. Could add location info there.
We also have "You'll Work Closely With" and "What Makes Someone Successful". Those could be incorporated into Requirements or Responsibilities.
We need to preserve all substantive info. So we need to include all details: company description, role description, responsibilities, requirements (experience, systems/data, tools, soft skills, nice to have), success measurement, location/travel, working closely with, what makes someone successful.
We must not repeat duplicated lines. The posting has duplicated intro paragraphs; we need to include only once.
We must remove boilerplate like cookie/navigation/legal/EEO etc. Not present.
We must not include application instructions (like "How to apply") - not present.
We must not include headings with filler text.
Thus we need to craft HTML:
About the role
... description of role (the About The Role paragraph) plus maybe location and work closely with etc? But we might separate.
Better:
About the role
We're hiring an Executive & Personal Assistant to the CEO to protect the CEO's quality time and reduce the number of decisions he personally has to make. You'll own his calendar, his working and living environment, travel, health and wellness operations, household and office administration, finance administration across personal and corporate spend, and the coordination of the small support team that executes all of it. The executive and personal sides of a founder's life are one system here, so this role covers both — you direct execution while keeping ownership of the outcome. And here's what makes this role different: you're not only running the operation, you're building the system that runs it. Meeting capture, transcription and OKR check-in data already happen automatically, and travel booking runs against a written playbook. What doesn't exist yet is a scorecard covering everyone in the support perimeter, fed by logs that collect themselves rather than by hand, and a way for the CEO to see the state of your work on a Monday morning without asking for it. Building both is a core expectation, not a nice extra — and as more of the administrative layer automates, this role shifts further toward reviewing what the systems produce, catching exceptions early, and managing the people and vendors around the automation. You'll report directly to the CEO.
Then Responsibilities
- Calendar and meeting discipline: Own the CEO's professional and personal calendar as a single integrated schedule — meetings, travel, training, treatments, family; Enforce meeting discipline: agendas prepared, correct attendees, pre-reads circulated 24 hours ahead, action items captured and closed before the next meeting; Manage requests for the CEO's time with judgement — decline, defer, delegate or escalate; Resolve calendar conflicts independently and report the resolution rather than returning the decision.
- Scorecards, reporting and automation: Build and maintain a personal scorecard and a team scorecard covering every person and vendor in the support perimeter, with digital logs of dates, responsibility areas and reports; Hold a weekly and biweekly reporting rhythm that doesn't slip when operational demand rises; Work inside the company's OKR system, track commitments and follow through to closure; Automate recurring work with AI tooling — meeting notes and action items, scheduling, reporting, document drafting — and progressively reduce the manual load of the role itself.
- Environment management: Make sure the Parkland office, the Barcelona setup and the CEO's home are ready before he arrives: climate, light, air quality, noise, cleanliness, food, connectivity; Resolve environment problems on the spot rather than routing them, including when the responsible person is unavailable.
- Travel, events and hospitality: Own business and personal travel end to end, with a travel assistant executing bookings against a playbook covering class, hotels and budget; Manage conferences, quarterly business reviews, executive meetings, family occasions and milestones, gifts and deliveries; Handle disruption — cancellations, reroutes, ground transport failures — as it happens.
- Health, sport and wellness operations: Coordinate medical, dental and concierge medical appointments and follow-ups, keeping continuity of care across providers; Manage the training schedule and wellness treatments, and manage nutrition with chefs in Parkland and Barcelona; Protect wellbeing decisions actively, including against schedules that are locally normal and personally wrong.
- Support perimeter and office operations: Coordinate the support team — travel assistant, house manager, driver, handyman — plus office and household vendors, without formal line authority over them; Hire and onboard supporting roles, starting with an office manager; Run payroll for hourly staff on a biweekly cycle, verifying timesheets before approval; Keep vendor contracts, renewals and service quality under review, and supervise office operations including lease matters, setup and improvement.
- Finance administration: Corporate card management: receipts, notes, monthly close; Personal and family payments through a dedicated account, with regular reporting and funding requests; Light bookkeeping and cost review across the support perimeter.
- Legal and personal projects: Drive immigration, visa and documentation matters to completion, including in-house filings and deadline tracking; Household administration: security and camera systems, maintenance, insurance and service contracts; Family support requests, with CEO approval.
Then Requirements
We need to include Experience, Systems and Data, Tools, Soft Skills, Nice to Have, What Makes Someone Successful, You'll Work Closely With, How Success Is Measured.
We can break into subheadings? But only allowed for sections; we could use
with bold? But instruction says use
- for any list of duties/requirements/benefits. So we can make a
with items that are paragraphs containing details.
We could structure as:
Requirements
- Experience: Prior experience supporting a founder or CEO across both business and personal domains — not a scheduling-only or office-management-only background. Coordinating people and vendors without formal authority: household or office staff, contractors, service providers. International travel coordination — flights, hotels, visas, ground transport.
- Systems and Data: You can build and maintain a scorecard or dashboard from scratch: define what's tracked, get the data in automatically where possible, and explain what the numbers mean to someone who wasn't involved. A track record of holding a reporting rhythm under operational pressure, evidenced by artefacts you built and maintained yourself. Demonstrated AI experience in this domain — scheduling, meeting notes and action items, reporting, document drafting — with the ability to describe the workflows you improved, the results they delivered, and how you validated the output.
- Tools: Advanced Google Workspace; Slack; Zoom. A corporate expense platform such as Ramp, and payroll for hourly employees such as Rippling, with light bookkeeping.
- Soft Skills: Exceptional attention to detail and very high personal standards. The resilience to absorb a high volume of competing tasks without letting the reporting
for prose. Do NOT repeat job title as heading (the page already shows it). Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting and extract sections. The posting includes: - Intro about Appodeal (company description) repeated twice. This is likely "About the company" but not required heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only include those headings if content exists. The "About the role" section is present: "About The Role ...". So we need an About the role
with prose.
Then "Key Responsibilities" -> we can map to Responsibilities heading.
Then "What We're Looking For" includes Experience, Systems and Data, Tools, Soft Skills, Nice to Have. This could be Requirements/Qualifications/Skills. We need to decide which headings to use. The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include sections only when there is real specific content.
We have content for Responsibilities (Key Responsibilities). We have content for Requirements (Experience, Systems and Data, Tools, Soft Skills). Could combine into Requirements heading. Could also separate Qualifications and Skills but we can keep it simple: one Requirements section with sub-lists? The instruction says use - for any list of duties/requirements/benefits. So we can have a
Requirements
with - items.
We also have "How Success Is Measured" maybe could be considered something else but not in allowed headings. Could be omitted or maybe put under Responsibilities? Probably better to omit as not a standard heading. But we need to preserve ALL substantive information; we cannot drop it unless we incorporate into another section. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. Could be placed under a heading like "Performance Expectations" but not allowed. However we could incorporate into Responsibilities or Requirements? The success metrics are about how success measured; could be considered part of Responsibilities? Might be okay to add a section "How Success Is Measured" but not in allowed list. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. But they also say "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could create a section for "How Success Is Measured" if we want, but it's not in the list; risk of being considered not following instruction. Safer to map that content into existing sections, maybe under Responsibilities (as part of what the role entails) or under a new heading "Performance" but not allowed. I'd incorporate into Responsibilities as bullet points about success metrics.
Also we have "Location and Travel" info. Could be placed under a heading "Location" but not in list. Could be incorporated into Responsibilities? Not really. Could be a short paragraph after Responsibilities maybe as a
without heading? The instruction says use
for section headings (list). It doesn't forbid other headings, but says use for section headings (e.g. ...). It may be okay to use other headings but they gave examples. Safer to stick to those headings and put location info in a
after Responsibilities maybe under a heading "About the role"? But that's already used.
We could treat location as part of "About the role" description. But we already have About the role section describing role. Could add location info there.
We also have "You'll Work Closely With" and "What Makes Someone Successful". Those could be incorporated into Requirements or Responsibilities.
We need to preserve all substantive info. So we need to include all details: company description, role description, responsibilities, requirements (experience, systems/data, tools, soft skills, nice to have), success measurement, location/travel, working closely with, what makes someone successful.
We must not repeat duplicated lines. The posting has duplicated intro paragraphs; we need to include only once.
We must remove boilerplate like cookie/navigation/legal/EEO etc. Not present.
We must not include application instructions (like "How to apply") - not present.
We must not include headings with filler text.
Thus we need to craft HTML:
About the role
... description of role (the About The Role paragraph) plus maybe location and work closely with etc? But we might separate.
Better:
About the role
We're hiring an Executive & Personal Assistant to the CEO to protect the CEO's quality time and reduce the number of decisions he personally has to make. You'll own his calendar, his working and living environment, travel, health and wellness operations, household and office administration, finance administration across personal and corporate spend, and the coordination of the small support team that executes all of it. The executive and personal sides of a founder's life are one system here, so this role covers both — you direct execution while keeping ownership of the outcome. And here's what makes this role different: you're not only running the operation, you're building the system that runs it. Meeting capture, transcription and OKR check-in data already happen automatically, and travel booking runs against a written playbook. What doesn't exist yet is a scorecard covering everyone in the support perimeter, fed by logs that collect themselves rather than by hand, and a way for the CEO to see the state of your work on a Monday morning without asking for it. Building both is a core expectation, not a nice extra — and as more of the administrative layer automates, this role shifts further toward reviewing what the systems produce, catching exceptions early, and managing the people and vendors around the automation. You'll report directly to the CEO.
Then Responsibilities
- Calendar and meeting discipline: Own the CEO's professional and personal calendar as a single integrated schedule — meetings, travel, training, treatments, family; Enforce meeting discipline: agendas prepared, correct attendees, pre-reads circulated 24 hours ahead, action items captured and closed before the next meeting; Manage requests for the CEO's time with judgement — decline, defer, delegate or escalate; Resolve calendar conflicts independently and report the resolution rather than returning the decision.
- Scorecards, reporting and automation: Build and maintain a personal scorecard and a team scorecard covering every person and vendor in the support perimeter, with digital logs of dates, responsibility areas and reports; Hold a weekly and biweekly reporting rhythm that doesn't slip when operational demand rises; Work inside the company's OKR system, track commitments and follow through to closure; Automate recurring work with AI tooling — meeting notes and action items, scheduling, reporting, document drafting — and progressively reduce the manual load of the role itself.
- Environment management: Make sure the Parkland office, the Barcelona setup and the CEO's home are ready before he arrives: climate, light, air quality, noise, cleanliness, food, connectivity; Resolve environment problems on the spot rather than routing them, including when the responsible person is unavailable.
- Travel, events and hospitality: Own business and personal travel end to end, with a travel assistant executing bookings against a playbook covering class, hotels and budget; Manage conferences, quarterly business reviews, executive meetings, family occasions and milestones, gifts and deliveries; Handle disruption — cancellations, reroutes, ground transport failures — as it happens.
- Health, sport and wellness operations: Coordinate medical, dental and concierge medical appointments and follow-ups, keeping continuity of care across providers; Manage the training schedule and wellness treatments, and manage nutrition with chefs in Parkland and Barcelona; Protect wellbeing decisions actively, including against schedules that are locally normal and personally wrong.
- Support perimeter and office operations: Coordinate the support team — travel assistant, house manager, driver, handyman — plus office and household vendors, without formal line authority over them; Hire and onboard supporting roles, starting with an office manager; Run payroll for hourly staff on a biweekly cycle, verifying timesheets before approval; Keep vendor contracts, renewals and service quality under review, and supervise office operations including lease matters, setup and improvement.
- Finance administration: Corporate card management: receipts, notes, monthly close; Personal and family payments through a dedicated account, with regular reporting and funding requests; Light bookkeeping and cost review across the support perimeter.
- Legal and personal projects: Drive immigration, visa and documentation matters to completion, including in-house filings and deadline tracking; Household administration: security and camera systems, maintenance, insurance and service contracts; Family support requests, with CEO approval.
Then Requirements
We need to include Experience, Systems and Data, Tools, Soft Skills, Nice to Have, What Makes Someone Successful, You'll Work Closely With, How Success Is Measured.
We can break into subheadings? But only allowed for sections; we could use
with bold? But instruction says use
- for any list of duties/requirements/benefits. So we can make a
with items that are paragraphs containing details.
We could structure as:
Requirements
- Experience: Prior experience supporting a founder or CEO across both business and personal domains — not a scheduling-only or office-management-only background. Coordinating people and vendors without formal authority: household or office staff, contractors, service providers. International travel coordination — flights, hotels, visas, ground transport.
- Systems and Data: You can build and maintain a scorecard or dashboard from scratch: define what's tracked, get the data in automatically where possible, and explain what the numbers mean to someone who wasn't involved. A track record of holding a reporting rhythm under operational pressure, evidenced by artefacts you built and maintained yourself. Demonstrated AI experience in this domain — scheduling, meeting notes and action items, reporting, document drafting — with the ability to describe the workflows you improved, the results they delivered, and how you validated the output.
- Tools: Advanced Google Workspace; Slack; Zoom. A corporate expense platform such as Ramp, and payroll for hourly employees such as Rippling, with light bookkeeping.
- Soft Skills: Exceptional attention to detail and very high personal standards. The resilience to absorb a high volume of competing tasks without letting the reporting
Requirements
with- items.
We also have "How Success Is Measured" maybe could be considered something else but not in allowed headings. Could be omitted or maybe put under Responsibilities? Probably better to omit as not a standard heading. But we need to preserve ALL substantive information; we cannot drop it unless we incorporate into another section. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. Could be placed under a heading like "Performance Expectations" but not allowed. However we could incorporate into Responsibilities or Requirements? The success metrics are about how success measured; could be considered part of Responsibilities? Might be okay to add a section "How Success Is Measured" but not in allowed list. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples, not exclusive? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. But they also say "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could create a section for "How Success Is Measured" if we want, but it's not in the list; risk of being considered not following instruction. Safer to map that content into existing sections, maybe under Responsibilities (as part of what the role entails) or under a new heading "Performance" but not allowed. I'd incorporate into Responsibilities as bullet points about success metrics. Also we have "Location and Travel" info. Could be placed under a heading "Location" but not in list. Could be incorporated into Responsibilities? Not really. Could be a short paragraph after Responsibilities maybe as a
without heading? The instruction says use
for section headings (list). It doesn't forbid other headings, but says use
for section headings (e.g. ...). It may be okay to use other headings but they gave examples. Safer to stick to those headings and put location info in a
after Responsibilities maybe under a heading "About the role"? But that's already used. We could treat location as part of "About the role" description. But we already have About the role section describing role. Could add location info there. We also have "You'll Work Closely With" and "What Makes Someone Successful". Those could be incorporated into Requirements or Responsibilities. We need to preserve all substantive info. So we need to include all details: company description, role description, responsibilities, requirements (experience, systems/data, tools, soft skills, nice to have), success measurement, location/travel, working closely with, what makes someone successful. We must not repeat duplicated lines. The posting has duplicated intro paragraphs; we need to include only once. We must remove boilerplate like cookie/navigation/legal/EEO etc. Not present. We must not include application instructions (like "How to apply") - not present. We must not include headings with filler text. Thus we need to craft HTML:
About the role
... description of role (the About The Role paragraph) plus maybe location and work closely with etc? But we might separate. Better:
About the role
We're hiring an Executive & Personal Assistant to the CEO to protect the CEO's quality time and reduce the number of decisions he personally has to make. You'll own his calendar, his working and living environment, travel, health and wellness operations, household and office administration, finance administration across personal and corporate spend, and the coordination of the small support team that executes all of it. The executive and personal sides of a founder's life are one system here, so this role covers both — you direct execution while keeping ownership of the outcome. And here's what makes this role different: you're not only running the operation, you're building the system that runs it. Meeting capture, transcription and OKR check-in data already happen automatically, and travel booking runs against a written playbook. What doesn't exist yet is a scorecard covering everyone in the support perimeter, fed by logs that collect themselves rather than by hand, and a way for the CEO to see the state of your work on a Monday morning without asking for it. Building both is a core expectation, not a nice extra — and as more of the administrative layer automates, this role shifts further toward reviewing what the systems produce, catching exceptions early, and managing the people and vendors around the automation. You'll report directly to the CEO.
ThenResponsibilities
- Calendar and meeting discipline: Own the CEO's professional and personal calendar as a single integrated schedule — meetings, travel, training, treatments, family; Enforce meeting discipline: agendas prepared, correct attendees, pre-reads circulated 24 hours ahead, action items captured and closed before the next meeting; Manage requests for the CEO's time with judgement — decline, defer, delegate or escalate; Resolve calendar conflicts independently and report the resolution rather than returning the decision.
- Scorecards, reporting and automation: Build and maintain a personal scorecard and a team scorecard covering every person and vendor in the support perimeter, with digital logs of dates, responsibility areas and reports; Hold a weekly and biweekly reporting rhythm that doesn't slip when operational demand rises; Work inside the company's OKR system, track commitments and follow through to closure; Automate recurring work with AI tooling — meeting notes and action items, scheduling, reporting, document drafting — and progressively reduce the manual load of the role itself.
- Environment management: Make sure the Parkland office, the Barcelona setup and the CEO's home are ready before he arrives: climate, light, air quality, noise, cleanliness, food, connectivity; Resolve environment problems on the spot rather than routing them, including when the responsible person is unavailable.
- Travel, events and hospitality: Own business and personal travel end to end, with a travel assistant executing bookings against a playbook covering class, hotels and budget; Manage conferences, quarterly business reviews, executive meetings, family occasions and milestones, gifts and deliveries; Handle disruption — cancellations, reroutes, ground transport failures — as it happens.
- Health, sport and wellness operations: Coordinate medical, dental and concierge medical appointments and follow-ups, keeping continuity of care across providers; Manage the training schedule and wellness treatments, and manage nutrition with chefs in Parkland and Barcelona; Protect wellbeing decisions actively, including against schedules that are locally normal and personally wrong.
- Support perimeter and office operations: Coordinate the support team — travel assistant, house manager, driver, handyman — plus office and household vendors, without formal line authority over them; Hire and onboard supporting roles, starting with an office manager; Run payroll for hourly staff on a biweekly cycle, verifying timesheets before approval; Keep vendor contracts, renewals and service quality under review, and supervise office operations including lease matters, setup and improvement.
- Finance administration: Corporate card management: receipts, notes, monthly close; Personal and family payments through a dedicated account, with regular reporting and funding requests; Light bookkeeping and cost review across the support perimeter.
- Legal and personal projects: Drive immigration, visa and documentation matters to completion, including in-house filings and deadline tracking; Household administration: security and camera systems, maintenance, insurance and service contracts; Family support requests, with CEO approval.
Requirements
We need to include Experience, Systems and Data, Tools, Soft Skills, Nice to Have, What Makes Someone Successful, You'll Work Closely With, How Success Is Measured. We can break into subheadings? But onlyallowed for sections; we could use
with bold? But instruction says use
- for any list of duties/requirements/benefits. So we can make a
- with items that are paragraphs containing details.
We could structure as:
- Experience: Prior experience supporting a founder or CEO across both business and personal domains — not a scheduling-only or office-management-only background. Coordinating people and vendors without formal authority: household or office staff, contractors, service providers. International travel coordination — flights, hotels, visas, ground transport.
- Systems and Data: You can build and maintain a scorecard or dashboard from scratch: define what's tracked, get the data in automatically where possible, and explain what the numbers mean to someone who wasn't involved. A track record of holding a reporting rhythm under operational pressure, evidenced by artefacts you built and maintained yourself. Demonstrated AI experience in this domain — scheduling, meeting notes and action items, reporting, document drafting — with the ability to describe the workflows you improved, the results they delivered, and how you validated the output.
- Tools: Advanced Google Workspace; Slack; Zoom. A corporate expense platform such as Ramp, and payroll for hourly employees such as Rippling, with light bookkeeping.
- Soft Skills: Exceptional attention to detail and very high personal standards. The resilience to absorb a high volume of competing tasks without letting the reporting
Requirements