Principal Financial Analyst, Revenue

We need to output HTML fragment with sections: About the role (already present as heading? The posting includes "About The Role". We should use

for section headings. Do NOT repeat the job title as a heading (the page already shows it). So we start with

About the Role

then content. We need to include sections only when posting has real specific content: Responsibilities (What You'll Do), Requirements (Qualifications), Benefits, maybe Pay? Not present. Schedule? Not present. Skills? Not explicit separate; but we can embed within Qualifications. Could have a Skills section if we extract but not needed. We'll follow: About the Role, Responsibilities, Requirements, Benefits. Possibly also "Core Values"? Might be considered but not requested; but we could include if specific content. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says we can use those headings. We should include sections only when posting has real specific content. The posting includes "About Vasion" (company overview) but that's not a required heading; we could include as "About Vasion" but not in list. Probably ignore boilerplate. The "About Vasion" is introductory but could be considered "About the company". Not required. We'll focus on role. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO statement at end, also "More About Vasion Visit https://www.vasion.com to learn more about Vasion." and "Additional Information Vasion is an equal opportunity employer..." etc. Also "Our Core Values" maybe keep? It's substantive but not a standard heading; could be included as a section "Core Values". The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings, but says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for those sections; but we could also add other headings if needed. Safer to stick to those. Thus we will have sections: About the Role, Responsibilities, Requirements (or Qualifications), Benefits. Possibly also "Skills" but we can incorporate into Qualifications. We need to use

• for any list of duties/requirements/benefits. So for responsibilities we need to break into bullet points. The responsibilities are described in paragraphs; we need to extract bullet points preserving detail. Must not invent or summarize away detail. We need to convert each duty into a list item, preserving the detail. Could be many bullet points; we need to ensure we don't lose any detail. Let's parse responsibilities section: Under "What You'll Do" there are headings: Revenue & Sales Metrics Ownership, Forecasting & Revenue Planning, Contract, Deal & Pricing Analysis, Cross-Functional Partnership, Revenue Recognition & Board Reporting. Each has bullet-like sentences. We need to produce a list under Responsibilities that captures each duty. Could break each sentence into separate
• . Must preserve all substantive information. Let's extract: Revenue & Sales Metrics Ownership: - Own and be the company's authoritative voice on all sales and revenue metrics (NRR, GRR, CAC payback, ARR attainment by product/segment/source, logo retention, etc.) - Define and maintain metric methodology so numbers are consistent, defensible, and audit-ready across Finance, Sales, and the board - Build and maintain executive-facing dashboards and KPI reporting packages that track performance against targets and prior periods Forecasting & Revenue Planning: - Partner with Sales and RevOps on the sales pipeline forecast — pressure-testing assumptions, coverage ratios, and rep-level inputs, and ensuring consistency between CRM activity and financial forecasts - Own the conversion of the sales forecast into the revenue forecast, translating bookings, ramp schedules, and churn assumptions into a P&L-ready number - Lead the annual revenue planning cycle and maintain a disciplined, driver-based rolling forecast on a monthly cadence - Reconcile forecast-to-actuals each period and explain variances to FP&A leadership and the CFO Contract, Deal & Pricing Analysis: - Review contract terms (ramp deals, multi-year agreements, non-standard billing, discounting) to understand their impact on revenue timing and recognition - Partner with Revenue Operations and Legal on structuring non-standard deals, flagging forecast and revenue-recognition implications before deals close - Provide finance input during deal negotiation on pricing, terms, and structure that affect revenue quality - Build scenario-based financial models to inform pricing decisions, GTM strategy refinements, and new-market-entry analyses - Proactively identify and quantify revenue leakage, deal structure risks, and margin compression drivers, bringing findings forward with recommended remediation Cross-Functional Partnership: - Serve as a close liaison to Revenue Operations and Sales leadership - Support territory planning, quota setting, and capacity models in partnership with RevOps - Translate finance-speak into sales-speak (and back) so both functions trust the same numbers - Support M&A diligence efforts or strategic partnership evaluations as they arise, contributing financial modeling and analytical support to transaction teams Revenue Recognition & Board Reporting: - Partner with Accounting to flag deals with revenue recognition complexity (ramps, professional services bundling, multi-element arrangements) before they close, and maintain alignment with ASC 606 across contract structures - Ensure forecast and reported revenue align with revenue recognition treatment across the deal base - Prepare revenue and sales metrics slides and supporting analysis for board decks and investor reporting - Serve as a go-to resource for leadership questions on revenue performance ahead of board meetings Now Requirements/Qualifications: Qualifications: - 4–7 years of experience in FP&A, revenue operations, investment banking, or a related analytical finance role, with meaningful top-line exposure - Bachelor's degree in Finance, Accounting, Economics, or a related field - Strong financial modeling skills, with the ability to build and defend forecast models from scratch - Strong experience modeling in Excel/Google Sheets - Strong knowledge of SaaS metrics and unit economics (ARR, NRR/GRR, CAC payback, LTV, cohort-based churn, etc.) - Comfort reading and interpreting contract terms and their financial implications - Fluency in the revenue funnel end to end — top-of-funnel pipeline through bookings and ARR to GAAP-recognized revenue — and the ability to explain how each stage converts into the next - Excellent communication skills — able to work fluently with Finance, Sales, and C-suite audiences alike Preferred Qualifications (we could include as part of Requirements or separate; but we can include as part of Requirements but maybe separate "Preferred Qualifications". The instruction says we can have Requirements heading; we could include both required and preferred under Requirements, but better to separate? The list of headings includes Qualifications, Skills. We could have a "Qualifications" section for required, and maybe a "Preferred Qualifications" subsection? But we need to follow instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have a

  Qualifications

  containing both required and preferred? Or we could have

  Requirements

  for required and

  Preferred Qualifications

  not in list but maybe okay. Safer to combine under Qualifications. Thus we will have

  Qualifications

  with
  • items for each bullet (including preferred). We'll keep the preferred bullets as separate list items. Benefits: list from posting: - Flexible work environment - Vacation - Bonus - Flexible paid time off - Paid parental leave - Competitive pay - A full suite of traditional benefits - Training/Advancement opportunities - 401k with company match and immediate vesting - Financial wellness education - Company-contributed HSA - On-site perks include gym, pickleball, snacks & drinks, arcade, theater room, etc. We need to preserve all detail; we can keep as bullet points. Now we need to output only HTML fragment, no /, no markdown fences. Thus:

    About the Role

    ... maybe a short paragraph summarizing? The posting includes a paragraph before "What You'll Do": "We are seeking a Senior Financial Analyst to join our FP&A team and serve as the analytical backbone of our revenue engine. This role sits at the intersection of Finance, Sales, Marketing, and Revenue Operations, owning the models, insights, and cross‑functional alignment that translate top‑of‑funnel activity into ARR, and ARR into GAAP revenue. This is a high-visibility individual contributor role with meaningful cross-functional reach. Day to day, you will work closely with Sales, RevOps, and GTM leadership to ensure revenue projections are grounded in pipeline reality and that the assumptions behind our plans are tested, transparent, and defensible. You'll lead the annual revenue planning cycle, manage rolling forecasts, and serve as a primary author of the executive-facing financial narratives that inform quarterly business reviews and board-level reporting. The right candidate is comfortable owning a number publicly, energized by shaping how the company thinks about revenue (not just reporting on it), and just as comfortable presenting to the C-suite as pressure-testing a rep-level pipeline assumption. Critically, you know the full path from top-of-funnel pipeline to GAAP-recognized revenue — how pipeline becomes bookings, bookings become ARR, and ARR becomes recognized revenue — and can explain that chain end to end." We should preserve that as prose under About the Role. Use

    . Then Responsibilities heading with

    • each duty. Then Qualifications heading with
      • each qualification (including preferred). Then Benefits heading with
        • each benefit. We must not include sections like Pay or Schedule because not present. We must not include duplicated lines. Check for any boilerplate: "About Vasion" paragraph at start: "For more than a decade, Vasion has been helping companies simplify their print infrastructure, automate business processes, and integrate their technology in a more secure environment. Our mission, to make digital transformation attainable for everyone, drives a culture of innovation and exploration. We have one simple goal: help organizations simplify processes through automation and integration. So we created simple, cost-effective, and easy-to-implement digital tools that work together, removing bottlenecks and improving efficiency. And we’re always on the lookout for new people who can help us innovate, grow, and reach our goal." This is company overview; not required but could be considered "About Vasion". Not in list of headings; we could ignore as it's not about the role. The instruction: "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." It doesn't forbid including company overview; but we should preserve ALL substantive information. However, the instruction also says "Prefer a few substantive sections over many thin ones." Including a company overview may be extra but it's substantive. However, the sections we are told to use are about the role etc. The company overview may be considered boilerplate? It's not navigation/legal/EEO; it's about the company. Might be okay to include as a short

          before About the Role. But the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should include it. Where to put? Could be a

          before the About the Role heading, or we could incorporate into About the Role section as an introductory paragraph. The About the Role heading currently we have a paragraph describing