Senior Financial Analyst

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, "Who Are We" is company description; not needed as a heading per rules? It's not listed as a section heading we must use; we can include as prose maybe under About the role? But "About The Role" heading is present. So we should have

About the role

and then prose summarizing that section (the paragraph after "About The Role"). Then responsibilities: bullet list under "What You’ll Do". So we need

Responsibilities

with

• items. Then requirements/qualifications: The posting has "What You’ll Bring" with must-have and nice-to-have. We need to decide sections: Requirements, Qualifications, Skills. The instruction: use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those with real content. We have must-have and nice-to-have items. Could split: Requirements (must-have), Qualifications (nice-to-have?), Skills (maybe specific skills like Excel, SaaS metrics, etc). But we need to avoid thin sections. Perhaps combine must-have and nice-to-have into Requirements and Qualifications? Let's think. The posting includes: - Must-have: BA/BS in Finance, Accounting, or related field, or equivalent experience. 3–5 years of quantitative or highly analytical work experience in FP&A, revenue analytics, private equity, or investment banking. Strong Excel modeling skills. Solid working knowledge of SaaS metrics and subscription economics: ARR, NRR/GRR, CAC, LTV, pipeline coverage, conversion rates, and velocity. Hands-on experience with Salesforce or comparable CRM. Track record of partnering with Revenue Operations and/or GTM teams. Outstanding communication and presentation skills. Proactive, organized, self-sufficient. - Nice-to-have: Experience with ERP systems (NetSuite) and EPM/planning tools (Adaptive Insights). Working proficiency with BI and reporting tools such as Power BI, Tableau, or Looker. Background specifically in SaaS FP&A or GTM finance at a high-growth technology company. We could map: Requirements: must-have items. Qualifications: nice-to-have items. Skills: maybe the specific technical skills like Excel, SaaS metrics, Salesforce, BI tools, etc. But that may duplicate. Better: Use Requirements for must-have, Qualifications for nice-to-have, and maybe Skills not needed if content overlaps. But we need to avoid empty sections. If we don't have specific content for Skills, we should omit it. Pay: The posting includes compensation details: "The all-in total compensation for this role is $120,000 and $137,500, and is specific to the United States. A reasonable estimate of the base salary range would be $110,000 - $125,000 plus applicable bonus/benefit offerings, etc., as those similarly situated within the Company." Also later: "The Pay Range For This Role Is 110,000 - 125,000 USD per year (Arlington Office) 110,000 - 125,000 USD per month (New York)". That's contradictory but we need to preserve all substantive information. We should include Pay section with that info. Benefits: Not explicitly listed besides "applicable bonus/benefit offerings". No specific benefits described. So we should not create Benefits section because no specific content. Schedule: Not mentioned. Omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay. We need to ensure we don't repeat job title as heading. Not needed. We need to strip boilerplate: EEO, visa sponsorship, scam warning, etc. Remove those. Also remove navigation, cookie, legal, duplicated lines. We need to preserve all substantive information: company description maybe not needed as it's not under a heading; but we could include a short paragraph under About the role? Actually About the role section should contain the paragraph after "About The Role". The company description "Who Are We" could be considered as part of About the role? Not exactly. 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 didn't say we cannot include other headings not listed; but we should prefer the listed headings. The company description could be placed as a

  before the headings? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid extra paragraphs outside headings. But we should aim to follow the structure: use headings for sections; we can have a leading

  for company overview if we want. However, the instruction says "Prefer a few substantive sections over many thin ones." Including a company overview paragraph may be okay but not under a heading. Might be considered filler? It's substantive info about the company. Could be included as a

  before the first heading. But maybe better to incorporate it into About the role section? The About the role section currently has the paragraph describing the role. We could prepend company overview to that same section? That would mix company and role. Might be okay but could be considered not strictly about the role. However, the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other content outside those headings. But to be safe, we can include a brief

  before the first heading describing the company (Who Are We). Then

  About the role

  with the role description. Let's extract the role description paragraph: "Comply is looking for a Senior Financial Analyst to connect the full funnel — from pipeline to revenue — and give the GTM organization the financial clarity it needs to grow faster and smarter. In this top-line-focused role, you’ll partner closely with Revenue Operations, Sales, Marketing, and Customer Success, building the ARR reporting, pipeline analytics, and GTM efficiency models that drive decision-making at every level of the commercial business. You’ll bring a strong FP&A foundation, fluency in SaaS metrics, and the communication skills to translate data into narratives that move leaders to action. You’ll love this role if you thrive at the intersection of finance and go-to-market, enjoy owning complex models end to end, and want your analysis to directly influence how a fast-growing SaaS company allocates resources and closes deals." That's the prose. Now responsibilities list: each bullet starts with a bold phrase? We'll extract each sentence after "What You’ll Do". The list: - Build and maintain the monthly ARR waterfall — consolidating ARR across the business, establishing a single source of truth, and explaining actuals vs. budget with clear attribution to retention, churn, expansion, and contraction. - Measure key SaaS metrics and perform retention, churn, and ad hoc analysis, surfacing the insights that inform commercial and strategic decisions. - Analyze GTM efficiency and unit economics — CAC, CAC payback, LTV, cost per pipeline dollar — and translate findings into concrete recommendations on Sales and Marketing investment. - Partner with Revenue Ops and GTM leaders to track the full pipeline funnel from lead generation through bookings to revenue, measuring conversion rates, pipeline coverage, velocity, and win rates. - Build and maintain the bookings and pipeline forecast alongside Revenue Operations and Sales leadership, improving forecast accuracy and top-line visibility over time. - Support pricing and discounting analysis — assessing the impact on bookings, ARR, and unit economics to inform deal decisions and pricing strategy. - Contribute to annual budgeting, quarterly re-forecasting, and multi-year planning, building the revenue and pipeline models that support budget owners across the business. - Use AI and BI tools to automate reporting, build self-serve dashboards, and accelerate insight generation — freeing up time for higher-value analysis across Finance and RevOps. Now Requirements (must-have) list: - BA or BS in Finance, Accounting, or a related field, or equivalent experience. - 3–5 years of quantitative or highly analytical work experience in FP&A, revenue analytics, private equity, or investment banking. - Strong Excel modeling skills — you can build detailed, well-structured financial models from scratch and maintain them as the business evolves. - Solid working knowledge of SaaS metrics and subscription economics: ARR, NRR/GRR, CAC, LTV, pipeline coverage, conversion rates, and velocity. - Hands-on experience with Salesforce or a comparable CRM for pipeline, bookings, pricing, and revenue data. - Track record of partnering with Revenue Operations and/or GTM teams (Sales, Marketing, Customer Success) to align on data definitions and support commercial decisions. - Outstanding communication and presentation skills — you translate complex models into clear narratives for revenue leaders and senior stakeholders. - Proactive, organized, and self-sufficient — you identify what needs to be done and drive it without waiting to be told. Now Qualifications (nice-to-have) list: - Experience with ERP systems (NetSuite) and EPM/planning tools (Adaptive Insights). - Working proficiency with BI and reporting tools such as Power BI, Tableau, or Looker. - Background specifically in SaaS FP&A or GTM finance at a high-growth technology company. Now Pay section: include the compensation details. We need to preserve all substantive information: The posting includes two statements about compensation: "The all-in total compensation for this role is $120,000 and $137,500, and is specific to the United States. A reasonable estimate of the base salary range would be $110,000 - $125,000 plus applicable bonus/benefit offerings, etc., as those similarly situated within the Company. It takes into account a wide range of factors that are considered in making compensation decisions, including, but not limited to, skill sets, training, licensure and certification, and experience." Then later: "The Pay Range For This Role Is 110,000 - 125,000 USD per year (Arlington Office) 110,000 - 125,000 USD per month (New York)". This seems contradictory (monthly vs yearly). We must preserve both statements as they are substantive. We'll include them as a paragraph. We should not include the boilerplate about EEO, visa, scam warning, etc. Now we need to output HTML fragment. Structure:

  Who Are We Comply is the leading provider of compliance SaaS and consulting services for the global financial services sector. With more than 5,000 clients and hundreds of employees across the globe, Comply empowers Chief Compliance Officers and their teams to proactively manage regulatory obligations, mitigate risk, and scale with efficiency and confidence. Comply serves thousands of global financial services clients including broker-dealers, insurers, investment banks, private funds, RIAs, and wealth managers who rely on Comply offerings to power their compliance programs. To learn more about Comply, visit comply.com

  About the role

  [role description]

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Pay

  [compensation paragraphs]

  We should not include Benefits or Schedule. Check for any duplicated lines: we need to avoid repeating same content. Ensure we didn't include the "