Executive Operations Partner
Gusto · Scottsdale, AZ · 1 mo ago
Management$82k–$101k/yrFull-time
We need to output HTML fragment with sections using for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove generic statements like "commensurate with experience" etc. Must not create sections with filler.
We need to parse the posting.
Key sections:
- About Gusto (company description) maybe not needed as a heading? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. "About Gusto" maybe not needed; but we could include as part of "About the role"? Actually "About The Role" is present. So we should have
inside
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove generic statements like "commensurate with experience" etc. Must not create sections with filler.
We need to parse the posting.
Key sections:
- About Gusto (company description) maybe not needed as a heading? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. "About Gusto" maybe not needed; but we could include as part of "About the role"? Actually "About The Role" is present. So we should have About the role
with content from "About The Role" paragraph.
- About The Team maybe could be part of About the role? But we could include as part of About the role or maybe as separate? The instruction says only those headings; we can include other headings if they map to those categories? Probably we should stick to those headings only. So we need to extract content for:
About the role: description of role, mission, etc.
Responsibilities: bullet list of duties (Here’s What You’ll Do Day-to-day). That's a list.
Requirements: maybe "Here’s What We're Looking For" bullet list.
Qualifications: maybe overlapping with requirements; but we can treat requirements as qualifications? The instruction says use both if there is distinct content. We have "Here’s What We're Looking For" which includes experience, AI fluency, autonomous style, influence, organization, communication, culture builder, proficiency. That could be both Requirements and Qualifications and Skills. We need to split appropriately.
Skills: maybe proficiency with Google Suite and AI Tooling.
Benefits: The posting mentions "All full-time employees receive competitive base pay, benefits, and equity (RSUs)". Also "Offer amounts are determined by role, level, and location." Also "Learn more about our Total Rewards philosophy." Also "Our cash compensation amount for this role is $82,130 to $101,294 in Scottsdale & most major metro locations." Also office expectations: hybrid 2-3 days per week. Also mention of physical offices. Also mention of secure internet for remote days. Also mention of equity (RSUs). So we have Pay, Benefits, Schedule.
We need to include Pay section only if posting states them. It does: cash compensation amount range. So include Pay.
Benefits: mention of competitive base pay, benefits, equity (RSUs). Also maybe "All full-time employees receive competitive base pay, benefits, and equity (RSUs)". That's benefits. Also maybe "Learn more about our Total Rewards philosophy." but that's vague. We'll include benefits: competitive base pay, benefits, equity (RSUs). Also maybe mention of office spaces? Not benefit.
Schedule: mention of hybrid expectation: employees based in Denver, SF, NY expected to work from office designated days approx 2-3 days per week (or more depending on role). Same office expectations apply to all Symmetry roles, whose physical office is in Scottsdale. Also note about remote days requiring secure internet. So we can include Schedule.
We must not include sections with filler like "commensurate with experience". Not present.
We must not include duplicated lines.
We must not include boilerplate like EEO etc. So we need to strip those paragraphs.
Now produce HTML:
About the role
Symmetry Software is seeking an autonomous, forward-thinking Executive Operations Partner to sit at the center of how Symmetry runs. You will be the strategic right hand to our CEO, Elizabeth Oviedo, taking ownership of leadership operating rhythms, complex scheduling, and the operational support for the Symmetry steering committee as it navigates a pivotal growth transformation. This is a senior, high-impact role for a leader who anticipates needs by default, reduces friction before it surfaces, and wants the fast pace of a small, high-growth team with the backing of a mature, profitable business.
Maybe also include About The Team? Could be part of About the role? But we could add a separateAbout the team
but not in allowed list. Probably better to incorporate into About the role paragraph? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are examples; we could still use other headings if needed, but better to stick to those. However we have relevant content about team: Symmetry Software is the payroll infrastructure... Could be part of About the role or maybe a separate "About the team" but not required. We could incorporate into About the role as additional paragraph. Thus About the role paragraph can include both role description and team description. Now Responsibilities: list from "Here’s What You’ll Do Day-to-day". We need to preserve all substantive information. Let's extract bullet points: - Own calendar management and meeting rhythms. - Anticipate complex scheduling needs, streamline calendars for maximum impact, and eliminate conflicts before they form for CEO and Head of Engineering. - Partner closely with the Insights & Operations Partner to operationalize meeting cadences and follow through - Embed AI-enabled systems into how Symmetry runs. Use AI to draft, synthesize, and accelerate the work meeting summaries and action-item extraction, inbox triage, first-draft comms and decks, research and briefing prep — then build the repeatable workflows, prompt libraries, and documentation that make the whole leadership team faster. Apply human judgment and Symmetry’s AI policies to everything that ships. - Act as an extension of the leaders you support. Triage inboxes and prioritize responses so clients, employees, and key stakeholders get fast, high-quality answers; represent the CEO with external partners on priorities, timelines, and availability. - Draft executive presentations, company-wide comms, and off-site materials in partnership with the CEO for a range of internal and external audiences. - Lead complex travel and events. Coordinate quarterly travel for the CEO, Head of Engineering, and leadership team, and lead onsite and event planning with cross-org coordination for team off-sites, celebrations, and Symmetry traditions. - Ensure seamless expense and budget processes for key executives including the CEO and Head of Engineering in close coordination with finance partners, and establish new or improve existing administrative systems and processes. - Serves as a trusted thought partner, frames decisions and offers options; Proactively helps leaders and teams identify risks, surface solutions, and shape workflows to prevent issues and adapt to change. - Acts with delegated authority on behalf of leader, making calls on routine decisions and requests. - Serves as a culture carrier and strengthens team identity through your interactions with individuals and teams. - Influences beyond direct leaders across the business, anticipating needs and future risks. We need to put each as
- .
Now Requirements: maybe from "Here’s What We're Looking For" but we need to separate into Requirements, Qualifications, Skills. Let's parse:
- 4+ years supporting VP-level or above executives, including calendaring for multiple executives, complex travel, and event planning — or equivalent relevant experience.
- Demonstrated AI fluency you have built systems around. You can walk us through specific AI workflows you designed, documented, and got others to adopt — not just tools you have tried. You write structured prompts with real context and constraints, you critically review output before it reaches an executive, and you protect sensitive data by default.
- An autonomous, strategic working style. You find ways to add value to the CEO and the leadership team without prompting or significant guidance. You navigate ambiguity, balance tradeoffs in high-stakes projects, and see around corners.
- Influence across leaders and teams. You build trust with executives and cross-functional partners through clarity, follow-through, and discretion, and you mentor others in the craft.
- Outstanding organization and judgment under pressure. Incredibly detail-oriented, able to prioritize competing assignments, and calm when responsibilities shift — with a great deal of common sense and a bias toward "find a way."
- Strong written and spoken communication, plus project management from conception to completion, and complete confidentiality, tact, and discretion on all business matters.
- Culture builder. A strong instinct for bringing people together and collaborating with the workplace experience team.
- Proficiency with Google Suite and AI Tooling: Gmail, Calendar, Drive, Docs, Sheets, Notion, ChatGPT, Gemini, Claude or others
We could treat the first bullet as Requirements (experience). The next few as Qualifications (AI fluency, autonomous style, influence, organization/judgment, communication, culture builder). The last as Skills (proficiency with Google Suite and AI Tooling). But we need to avoid duplication.
Let's decide:
Requirements: 4+ years supporting VP-level or above executives, including calendaring for multiple executives, complex travel, and event planning — or equivalent relevant experience.
Qualifications: Demonstrated AI fluency you have built systems around...; An autonomous, strategic working style...; Influence across leaders and teams...; Outstanding organization and judgment under pressure...; Strong written and spoken communication...; Culture builder...
Skills: Proficiency with Google Suite and AI Tooling...
We must ensure we don't include filler like "or equivalent relevant experience" is okay.
Now Benefits: "All full-time employees receive competitive base pay, benefits, and equity (RSUs) — because everyone who helps build Gusto should share in its success." Also maybe mention of "Learn more about our Total Rewards philosophy." but that's vague. We'll include benefits: competitive base pay, benefits, equity (RSUs). Also maybe mention of office spaces? Not benefit.
Pay: "Our cash compensation amount for this role is $82,130 to $101,294 in Scottsdale & most major metro locations. Final offer amounts are determined by multiple factors including candidate location, experience and expertise and may vary from the amounts listed above."
Schedule: "Gusto has physical office spaces in Denver, San Francisco, and New York City. Employees who are based in those locations will be expected to work from the office on designated days approximately 2-3 days per week (or more depending on role). The same office expectations apply to all Symmetry roles, Gusto's subsidiary, whose physical office is in Scottsdale. Note: The San Francisco office expectations encompass both the San Francisco and San Jose metro areas. When approved to work from a location other than a Gusto office, a secure, reliable, and consistent internet connection is required. This includes non-office days for hybrid employees."
We'll put that in Schedule.
Now we need to output only HTML fragment, no markdown fences.
Let's construct.
We'll include
About the role
with paragraphs. We'll includeResponsibilities
with- .
We'll include
Requirements
with- (maybe just one li).
We'll include
Qualifications
with- (multiple li).
We'll include
Skills
with- (one li maybe multiple items but we can list as one li with comma-separated list or split). Better to split each tool? Could be one li with list. We'll keep as one li.
We'll include
Benefits
with- maybe one li.
We'll include
Pay
with. We'll include
Schedule
with. Make sure not to include any boilerplate. Now produce final HTML. Check for