Chief of Staff

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule as appropriate. Use

for headings. Use

• for lists. Use

  for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Content: - About Kick: description of company. This is not a section heading? Could be "About the role"? Actually "About Kick" is company description. Could be part of "About the role"? The instructions: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have sections: About the role (maybe includes description of role and company?), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Let's extract: About the role: The posting includes "About The Role" paragraph: "Kick is growing fast and is planning to soon raise capital to rapidly scale the organization. Our most important problems are cross functional and we need a high-agency problem solver to help us scale. You'll work directly with our CEO and Head of Finance & Operations to drive finance, operations and GTM projects to completion with high ownership so they scale to 100X without you." That's about the role. Responsibilities: "What You'll Do" list: bullet points (examples). So we can list responsibilities. Ideal Candidate: includes qualifications, requirements, skills. We need to separate into Requirements, Qualifications, Skills maybe. The posting says: Ideal Candidate 3–7 years post-grad, with experience in MBB, investment banking, or a former chief of staff role. Strong financial acumen building models from scratch and understands how ARR, NRR, gross margin and rev rec connect. Hands-on builder who ships working dashboards, automations and processes on their own. AI-native: uses Claude or ChatGPT daily and has built workflows with tools like Clay, n8n, Zapier or Claude Code. High agency: runs several projects at once and makes progress without a playbook. Clear writer and communicator, credible with the CEO, investors and candidates. Bonus If You Have Worked in venture, growth equity or been an operator at a high-growth startup (Seed to Series B) Experience starting new businesses and/or ventures Is highly proficient in using AI tools (e.g., Claude, etc.) We can treat Requirements as the core: 3-7 years post-grad, experience in MBB, investment banking, or former chief of staff. Strong financial acumen building models from scratch and understands ARR, NRR, gross margin, rev rec. Hands-on builder who ships dashboards, automations, processes. AI-native: uses Claude/ChatGPT daily and built workflows with tools like Clay, n8n, Zapier or Claude Code. High agency: runs several projects at once and makes progress without a playbook. Clear writer and communicator, credible with CEO, investors, candidates. Qualifications could be the bonus? Or maybe we treat Bonus as Qualifications? Actually "Qualifications" often includes education/experience. Could combine. But we need to avoid filler. We can have Requirements (mandatory) and Qualifications (bonus). Skills maybe list specific technical skills: financial modeling, dashboard building, automation tools (Clay, n8n, Zapier, Claude Code), AI tools usage, etc. Benefits: "What We Offer": Top-of-market $170,000-$220,000 total compensation + meaningful equity; Employee-friendly equity (QSBS eligible, early exercise, extended exercise); 100% employer paid medical, dental, and vision benefits (employee + dependents); Apple laptop/headset, health/commuter stipends; Daily lunch and unlimited Verve coffee. Pay: The compensation range is given: $170,000-$220,000 total compensation + meaningful equity. So we can have Pay section with that. Schedule: Not mentioned. Location: In person Palo Alto, CA (Preferred) with in person in NYC or Toronto for the right candidate. That's location, not schedule. No schedule info, so we omit Schedule section. We also have "About Kick" description at top. Could be part of About the role? Might be better to have a separate "About the company" but not in allowed headings. The instruction says use those headings as examples, but we can also have other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those. Probably we should stick to those. The "About Kick" could be placed under About the role as a brief intro. Or we could create a separate "About the company" but not listed; maybe better to include under About the role. Thus structure:

  About the role

  for each section. We need to output only HTML fragment. Let's craft:

  About the role

  Kick is an applied AI company building the first self-driving accounting experience. We've raised $20M from OpenAI, General Catalyst and Google Ventures to help millions of Business Owners and Accountants automate the boring stuff, so they can focus on what matters most. Kick is growing fast and is planning to soon raise capital to rapidly scale the organization. Our most important problems are cross functional and we need a high-agency problem solver to help us scale. You'll work directly with our CEO and Head of Finance & Operations to drive finance, operations and GTM projects to completion with high ownership so they scale to 100X without you.

  Responsibilities

  • Optimize our finance tech stack to operate near autonomously (e.g., upgrade billing process, optimize vendor evaluation & payment processes)
  • Drive key reporting efforts (e.g., improved live ARR tracking, margin analyses, projections, etc.)
  • Support fundraising and investor relations, from the model and data room to investor updates
  • Build our RevOps foundation: document the sales process and CRM setup, own funnel reporting, and find what drives conversion as outbound scales
  • Optimize our customer support workflows, improving our agents to deliver best-in-class service
  • Build AI agents and automations that give the team leverage, like surfacing buying signals from LinkedIn and X
  • Run key hires from sourcing to close, including designing work trials
  • Upgrade HR operations, from the tech stack to our first performance management framework
  • Jump on whatever matters most next, with direct visibility into CEO priorities

  Requirements

  • 3–7 years post-grad experience
  • Experience in MBB, investment banking, or a former chief of staff role
  • Strong financial acumen building models from scratch and understands how ARR, NRR, gross margin and rev rec connect
  • Hands-on builder who ships working dashboards, automations and processes on their own
  • AI-native: uses Claude or ChatGPT daily and has built workflows with tools like Clay, n8n, Zapier or Claude Code
  • High agency: runs several projects at once and makes progress without a playbook
  • Clear writer and communicator, credible with the CEO, investors and candidates

  Qualifications (Bonus)

  • Worked in venture, growth equity or been an operator at a high-growth startup (Seed to Series B)
  • Experience starting new businesses and/or ventures
  • Highly proficient in using AI tools (e.g., Claude, etc.)

  Skills

  • Financial modeling and analysis (ARR, NRR, gross margin, revenue recognition)
  • Dashboard and reporting creation
  • Process automation and workflow building (Clay, n8n, Zapier, Claude Code)
  • AI tool proficiency (Claude, ChatGPT)
  • Project management and cross-functional leadership
  • Strong written and verbal communication
  • CRM and sales process documentation
  • Customer support optimization
  • HR operations and performance framework design

  Benefits

  • Top-of-market $170,000-$220,000 total compensation + meaningful equity
  • Employee-friendly equity (QSBS eligible, early exercise, extended exercise)
  • 100% employer paid medical, dental, and vision benefits (employee + dependents)
  • Apple laptop/headset, health/commuter stipends
  • Daily lunch and unlimited Verve coffee

  Pay

  $170,000–$220,000 total compensation + meaningful equity

  We omitted Schedule as not present. Check for any duplicate or boilerplate removed: We removed "Location In person Palo Alto, CA (Preferred) with in person in NYC or Toronto for the right candidate" - that's location, not schedule. Should we include location? Not in allowed headings but could be part of About the role? Might be relevant but not required. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include location info somewhere. Where? Could add a short paragraph under About the role or maybe a separate section like "Location". But not in allowed headings. However we could incorporate location into About the role paragraph. That would preserve it. Let's add location info to About the role paragraph. Update About the role paragraph to include location: "Kick is an applied AI company ... Kick is growing fast ... You'll work directly with our CEO ... Location: In person Palo Alto, CA (Preferred) with in person in NYC or Toronto for the right candidate." We need to ensure we didn't repeat job title. Good. Check for any other boilerplate: "We're building a world-class team of creative thinkers and doers from diverse backgrounds. If you're excited by this role, even if your experience isn't a perfect match, we'd love to hear from you." That's encouraging to apply; could be considered application instruction? It's not exactly instructions but more of a closing encouragement. Might be considered boilerplate? The instruction says remove application instructions. This is not exactly instructions but could be considered a call to apply. Safer to remove it. It's not substantive info about role. So we can drop. Now ensure we didn't include any filler like "commensurate with experience". Not present. Check Pay section: we have both Benefits includes compensation range and Pay section duplicates. Might be redundant but both are present in posting. Benefits includes compensation range; Pay section also includes same. Could combine but we need to preserve all substantive info; having both is okay but could be considered duplication. However we could keep Pay as separate with just the range, and Benefits list other benefits. The compensation range appears in Benefits bullet; we could keep it there and also in Pay. It's not harmful but maybe considered duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not removing detail, it's okay. But we could avoid duplication by moving compensation to Pay only and not listing in Benefits. However Benefits bullet includes "Top-of-market $170,000-$220,000 total compensation + meaningful equity". That is a benefit. If we remove it from Benefits, we lose that detail from Benefits section. But we still have it in Pay section. The instruction says preserve ALL substantive information; as long as it's present somewhere