Managing Controller & Client Liaison

We need to output HTML fragment with sections: headings

for section headings 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 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. 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. We need to parse the posting. The posting includes: - About Crew Finance (intro paragraph) - The Role (description) - What You'll Own & Improve (list of responsibilities) - What You Bring (requirements/qualifications) - Why Crew (benefits/culture) We need to map to sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have: - About the role: could be "The Role" paragraph describing role. That's about role. So we can have

  About the role

  with

  describing. - Responsibilities: "What You'll Own & Improve" includes bullet points (list). So we can have

  Responsibilities

  with
  • each bullet. - Requirements/Qualifications: "What You Bring" includes list of requirements: CPA required, 10+ years experience, deep technical knowledge, comfortable with certain software, experience with startup businesses, CPG experience required, strong communicator, able to manage multiple client engagements, high ownership mentality. Also maybe "CPA required — this is a non-negotiable". So we can have

    Requirements

    (or Qualifications). The instruction says we can use either Requirements or Qualifications. We need to decide which to include. Probably combine into one section "Requirements". Could also split into Requirements and Qualifications but they'd be thin. Prefer few substantive sections. So we can have one section "Requirements" containing all. - Skills: maybe we could extract skills like "US GAAP, revenue recognition, COGS, inventory, costing, QuickBooks Online, NetSuite, Bill.com, Gusto, Shopify". But those are already in requirements. Could create a Skills section but might be thin. Better to include them within Requirements. - Benefits: "Why Crew" includes benefits: working fractionally means you'll never be bored, wide range of industries, build expertise faster, we care about doing the work right, quality isn't just a checkbox, it's the whole point. Also maybe mention fractional work, variety, etc. So we can have

    Benefits

    with

    describing. - Pay and Schedule: not mentioned. So we should NOT include those sections. Thus we will output sections: About the role, Responsibilities, Requirements, Benefits. We need to ensure we preserve all substantive information. Let's extract details. About Crew Finance paragraph: "We are the financial backbone for startups in Consumer, Technology, and SaaS — some of the brightest emerging brands navigating the chaos of high growth. Based in Santa Monica with crewmates spread coast to coast, we don't just keep the books. We help founders make sense of their numbers, build financial infrastructure that scales, and stay focused on what matters most: the business. Our work is fractional by design. You'll never be siloed on a single client — you'll be navigating a fleet, bringing the same high standards to every set of financials you touch." The Role paragraph: "The Managing Controller & Client Liaison is a senior fractional Controller who combines client excellence with accountable people leadership. In addition to managing a portfolio of client relationships, the Managing Controller & Client Liaison leads and develops a small team (“pod”) of Controllers and Accounting Staff. This role ensures high-quality client delivery, strong team performance, sustainable capacity management, and clear accountability within the pod. Managing Controller & Client Liaison are critical to Crew’s operating model. They translate firm standards into consistent client execution while building genuine trust, clarity, and development pathways for their team members." What You'll Own & Improve: bullet list: - Client Leadership & Delivery - Serve as lead Controller for a portfolio of client engagements - Ensure timely, accurate, and high-quality financial reporting - Oversee month-end close processes and technical accounting matters - Partner with founders/CEOs to provide financial insight and clarity - Identify risks early and escalate appropriately - Maintain strong client relationships and uphold Crew’s brand standards - People Management - Managing Controller & Client Liaison are expected to operate as true people leaders, not simply senior reviewers. - Work toward genuine connection and trust within the pod - Lead by example by exemplifying Crew’s values and professional maturity - Help team members balance workload with meaningful learning opportunities - Foster a culture of accountability, curiosity, and support - Capacity & Staffing Management - Partner with firm leadership to: - Allocate work across pod members appropriately - Ensure expertise aligns with client needs (e.g., SaaS vs. CPG vs. services) - Maintain sustainable utilization levels - Flag bandwidth risks early - Advocate for team members when workload or fit concerns arise - Quality Control & Standards - Review work product from pod members to ensure accuracy and consistency through the internal audit process review - Maintain adherence to Crew’s accounting and reporting standards - Identify training needs within the pod - Ensure onboarding curves are supported appropriately for newer team members - Communication & Escalation - Act as the first point of escalation for client or team issues within the pod - Ensure client experience issues on pod-managed accounts are owned and addressed within the pod while providing visibility to firm leadership We need to preserve all these bullet points. We'll flatten into

    • items. Could keep sub-bullets but we can just list each as separate
    • . Might lose hierarchy but still preserve content. The instruction: Use
      • for any list of duties/requirements/benefits. It doesn't forbid nesting but we can keep simple. What You Bring: list: - CPA required — this is a non-negotiable for a role built on accounting precision - 10+ years of progressive accounting experience in a client services, outsourced accounting, or professional services environment - Deep technical knowledge: US GAAP, revenue recognition, COGS, inventory, costing — you're the one colleagues call when they're stuck - Comfortable with QuickBooks Online, NetSuite, Bill.com, Gusto, and Shopify (or willing to learn quickly) - Experience with startup businesses — you understand the startup accounting lifecycle and how fast things can change - Consumer Packaged Goods (CPG) experience is required — many of our clients are in this world - Strong communicator — you can translate accounting complexity into plain language for a founder who didn't go to business school - Able to manage multiple client engagements simultaneously without dropping the anchor - High ownership mentality: if something's broken, you fix it; if something's unclear, you clarify it Why Crew: paragraph: - Working fractionally means you'll never be bored. You'll encounter a wide range of industries, business models, and accounting challenges — and you'll build expertise faster than you would in any single-client role. - We care deeply about doing the work right. That's why this role exists. - And we're building the kind of firm where quality isn't just a checkbox — it's the whole point. - If you're ready to bring your accounting expertise to a team that takes the craft seriously, we'd love to talk. We'll put that in Benefits section. Now we need to output HTML fragment only, no /, no markdown fences. We'll produce:

        About the role

        ...

        Responsibilities

        • ...
        ...

        Requirements

        • ...
        ...

        Benefits

        ...

        Make sure we preserve all details. Let's craft the About the role paragraph: combine About Crew Finance and The Role? The About the role section likely should contain description of the role and maybe company overview. The instruction: "About the role" heading for section headings (e.g. About the role, Responsibilities...). So we can put the combined description of the role and company under About the role. But we have separate "About Crew Finance" and "The Role". We'll combine them into one

        maybe two paragraphs. That's fine. Let's write:

        We are the financial backbone for startups in Consumer, Technology, and SaaS — some of the brightest emerging brands navigating the chaos of high growth. Based in Santa Monica with crewmates spread coast to coast, we don't just keep the books. We help founders make sense of their numbers, build financial infrastructure that scales, and stay focused on what matters most: the business. Our work is fractional by design. You'll never be siloed on a single client — you'll be navigating a fleet, bringing the same high standards to every set of financials you touch.

        The Managing Controller & Client Liaison is a senior fractional Controller who combines client excellence with accountable people leadership. In addition to managing a portfolio of client relationships, the Managing Controller & Client Liaison leads and develops a small team (“pod”) of Controllers and Accounting Staff. This role ensures high-quality client delivery, strong team performance, sustainable capacity management, and clear accountability within the pod. Managing Controller & Client Liaison are critical to Crew’s operating model. They translate firm standards into consistent client execution while building genuine trust, clarity, and development pathways for their team members.

        Now Responsibilities: list each bullet. We'll produce
        with each bullet as
        • . We'll need to capture the subheadings like "Client Leadership & Delivery" maybe as part of
        • text. We'll just include them as part of the
        • . Eg:
        • Client Leadership & Delivery: Serve as lead Controller for a portfolio of client engagements; ensure timely, accurate, and high-quality financial reporting; oversee month-end close processes and technical accounting matters; partner with founders/CEOs to provide financial insight and clarity; identify risks early and escalate appropriately; maintain strong client relationships and uphold Crew’s brand standards.
        But we could break each into separate
        • . However the instruction: Use
          • for any list of duties/requirements/benefits. It doesn't require each bullet to be atomic; we can keep the original bullet grouping. Safer to keep each line as separate
          • . Let's extract each line: - Serve as lead Controller for a portfolio of client engagements - Ensure timely, accurate, and high-quality financial reporting - Oversee month-end close processes and technical accounting matters - Partner with founders/CEOs to provide financial insight and clarity - Identify risks early and escalate appropriately - Maintain strong client relationships and uphold Crew’s brand standards - Work toward genuine connection and trust within the pod - Lead by example by exemplifying Crew’s values and professional maturity - Help team members balance workload with meaningful learning opportunities - Foster a culture of accountability, curiosity, and support - Allocate work across pod members appropriately - Ensure expertise aligns with client needs (e.g., SaaS