VP, Finance

before any heading? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't forbid extra paragraphs outside headings. It said use

for section headings (e.g. 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. Thus we can include a

  for company description (About Plenful) before any headings. That is prose. So we should include a

  with that description. Also the "What you'll do" and "What we're looking for" sections are lists; we will use

  • . The "Why You'll Love Working Here" is also a list of benefits; we will use
    • . We need to ensure we don't create sections with filler like "commensurate with experience". Not present. Thus final HTML:

      About Plenful Plenful is on a mission to transform healthcare operations from the inside out. Fresh off our $50M Series B and backed by Notable Capital, Bessemer Venture Partners, TQ Ventures, Susa/Kivu Ventures, and other leading investors, we’re building the category-defining AI workflow automation platform that healthcare teams rely on to operate smarter, faster, and more efficiently. Our technology empowers healthcare operators across hospital and health systems, pharmacies and payors to eliminate manual work, reduce administrative burden, and improve compliance, all while unlocking critical revenue to fund programs for their in-need patient populations. Built by healthcare operators for healthcare operators, Plenful is driven by a deep understanding of the challenges facing today’s care teams. We’re passionate about equipping healthcare workers with world-class tools that deliver real, measurable impact, and we’re proud to serve 90+ leading health systems across the country. If you’re excited to help shape the future of healthcare, we’d love to meet you. Apply now to join our growing team.

      But we need to remove application instructions: "Apply now to join our growing team." That's application instruction; should be removed. So we should strip that sentence. Also maybe "If you’re excited to help shape the future of healthcare, we’d love to meet you." That's also a call to action; maybe considered application instruction? It's more like invitation but could be considered boilerplate. Safer to remove both sentences that are calls to action. Keep the descriptive mission etc. Let's keep the description up to "we’re proud to serve 90+ leading health systems across the country." Then stop. So we need to trim. Thus

      About Plenful Plenful is on a mission to transform healthcare operations from the inside out. Fresh off our $50M Series B and backed by Notable Capital, Bessemer Venture Partners, TQ Ventures, Susa/Kivu Ventures, and other leading investors, we’re building the category-defining AI workflow automation platform that healthcare teams rely on to operate smarter, faster, and more efficiently. Our technology empowers healthcare operators across hospital and health systems, pharmacies and payors to eliminate manual work, reduce administrative burden, and improve compliance, all while unlocking critical revenue to fund programs for their in-need patient populations. Built by healthcare operators for healthcare operators, Plenful is driven by a deep understanding of the challenges facing today’s care teams. We’re passionate about equipping healthcare workers with world-class tools that deliver real, measurable impact, and we’re proud to serve 90+ leading health systems across the country.

      Now Responsibilities section. We'll create

      Responsibilities

      • Own the plan. Annual operating plan and rolling forecast, built on multi-scenario revenue and headcount models leadership actually uses to commit to hires and investments.
      • Own capital allocation. Bring a recommendation, not a menu. Where the next $1M goes, what it has to return, and what we stop doing to fund it.
      • Own the economics. Unit economics, CAC and payback, gross margin by product, and the pricing and deal structures that move them. AI means the model has real complexity — that's the interesting part.
      • Own cash and runway. Burn, scenarios, and a clear read on how much time each plan buys us.
      • Be the partner leaders actually want in the room. Go-to-market, engineering, and operations leaders should bring you the decision before it's made, not the invoice after.
      • Own leadership and board reporting. The monthly numbers and metrics leadership runs on, and the financial narrative in the board package.
      • Build the decision layer. Our core systems are already in place. Connect ERP, expense, payroll, and CRM data into one reporting layer everyone trusts, and mature the processes running on top of them.
      • Build the team. Lead, coach, and grow the finance and accounting team.
      Now Requirements section.

      Requirements

      • 8+ years in finance, including running finance or FP&A at a high-growth B2B SaaS company at Series A through Series C scale
      • A track record of taking a functioning finance team to the next level of rigor: sharper forecasting, stronger scenario modeling, management reporting leadership relies on
      • Player-coach. You build the model yourself and you develop the people who will eventually own it
      • Solid technical accounting foundation, including ASC 606 revenue recognition on complex or milestone-based contracts.
      • A sharp business partner. You've told a senior leader something they didn't want to hear and kept the relationship
      • Comfort with ambiguity, high ownership