Revenue Analyst - Sales

We need to output HTML fragment with sections: About the role? Actually the posting includes intro paragraphs about company, then role description. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to parse content. First, we have intro about company culture: "At Constant Contact, we are seriously awesome people..." This could be "About the role"? Actually "About the role" is usually description of role. But we have "What You'll Do:" which is responsibilities. "Who You Are:" is qualifications/requirements. Also there is "Why You’ll Love Us:" which could be Benefits? Actually benefits described later: health and welfare benefits, paid leave, generous PTO, competitive benefits package. Also "Pay Transparency - All Full Time Employees $63,420—$79,275 USD". So we have Pay section. Schedule: "This is a hybrid role with work from our Waltham, MA office on Mondays and Wednesdays weekly*". So schedule info. We also have "Application Deadline: 30 days." etc but we should remove application instructions. Also remove boilerplate EEO etc. We need to preserve all substantive information, not invent. We need to use

• for any list of duties/requirements/benefits. So we need to turn bullet points into lists. Let's extract sections: About the role: maybe a brief summary: The role description intro: "We have an opening for a high-energy, detail-oriented Financial Analyst to join our Revenue organization with a primary focus on Deal Desk operations. In this role, you will be the strategic partner to our Sales team, helping to structure complex deals, optimize pricing strategies, and ensure all contracts align with our financial and legal guardrails. You aren't just a "gatekeeper"; you are a deal architect. You will balance the need for aggressive growth with the necessity of maintaining healthy margins and scalable revenue practices." That seems like about the role. Responsibilities: bullet list under "What You'll Do:" includes multiple sentences each starting with a verb. We'll turn each into
• . Requirements/Qualifications/Skills: The "Who You Are:" section includes experience, adept with revenue planning systems, experience building models, proficient with Excel, familiar with Salesforce, excited about leveraging technology, ability to use AI to build predictive models, etc. Could split into Requirements (experience, education) and Skills (technical). But we can combine into one section maybe "Requirements". However we have headings for Requirements, Qualifications, Skills. We need to decide which to use based on content. The posting includes: "A highly collaborative and detail-oriented professional with 3+ years of experience in a Finance, Accounting, or similar analytical role." That's experience requirement. "Adept with revenue planning systems and possess strong foundational knowledge of profit and loss statements." That's skill/knowledge. "Experience building and managing financial models, with a focus on detailed variance analyses that drive actionable insights." Skill. "Proficient with Microsoft Excel and skilled in data analysis and financial modeling." Skill. "Familiar with Salesforce or similar CRM systems." Skill. "Excited about leveraging technology to drive efficiency and accuracy. You have the ability to use AI to build predictive models for revenue forecasting and are keen to explore and utilize new tools to enhance your work." Skill/attribute. We could put all under "Requirements" or "Qualifications". Since we have both headings, we need to decide which to emit. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine into one section "Requirements" that includes experience and skills. Or we could have "Requirements" for experience, "Skills" for technical. But that would be two sections; still okay if both have substantive content. However we need to avoid thin sections. Both would have content. But we also have "Benefits": health and welfare benefits including paid leave, generous paid time off policy, competitive benefits package. Also maybe "We celebrate one another’s differences..." that's culture not benefits. But we have benefits specifics. Pay: salary range $63,420—$79,275 USD, plus mention of potential commission/bonus. Schedule: hybrid role with work from Waltham, MA office on Mondays and Wednesdays weekly. We also have location mention: Waltham, MA. We need to not repeat job title as heading. We need to output only HTML fragment. Let's craft:

  About the role

  We have an opening for a high-energy, detail-oriented Financial Analyst to join our Revenue organization with a primary focus on Deal Desk operations. In this role, you will be the strategic partner to our Sales team, helping to structure complex deals, optimize pricing strategies, and ensure all contracts align with our financial and legal guardrails. You aren't just a "gatekeeper"; you are a deal architect. You will balance the need for aggressive growth with the necessity of maintaining healthy margins and scalable revenue practices.

  Responsibilities

  • Serve as the primary point of contact for the GTM team for deal structuring, pricing, and commercial terms.
  • Review and approve quotes and order forms, ensuring accuracy in pricing, discounts, and billing terms.
  • Develop and track Deal Desk KPIs (e.g., average discount rates, approval turnaround time, and deal velocity).
  • Assist in the tracking, reporting, and forecasting of operational KPIs and key business metrics, providing timely and accurate information to stakeholders.
  • Build and maintain financial models to evaluate deal profitability, Customer Lifetime Value (CLV), and Customer Acquisition Cost (CAC).
  • Analyze historical deal data to identify pricing trends and provide recommendations for optimizing "floor," "target," and "list" pricing.
  • Perform impact analysis on various discount structures to protect gross margins.
  • Own end to end reporting for International Revenue Initiatives.
  • Collaborate with the Director of Revenue Analytics to support various ad-hoc financial projects and analyses as needed.

  Requirements

  • 3+ years of experience in a Finance, Accounting, or similar analytical role.
  • Adept with revenue planning systems and possess strong foundational knowledge of profit and loss statements.
  • Experience building and managing financial models, with a focus on detailed variance analyses that drive actionable insights.
  • Proficient with Microsoft Excel and skilled in data analysis and financial modeling.
  • Familiar with Salesforce or similar CRM systems.
  • Excited about leveraging technology to drive efficiency and accuracy; ability to use AI to build predictive models for revenue forecasting and keen to explore and utilize new tools to enhance work.

  Benefits

  • Health and welfare benefits including paid leave.
  • Generous paid time off policy.
  • Competitive benefits package supporting health and well‑being of you and your family.

  Pay

  Pay transparency: $63,420—$79,275 USD for full‑time employees. Some roles may be eligible for additional on‑target commission pay or bonus.

  Schedule

  Hybrid role: work from the Waltham, MA office on Mondays and Wednesdays weekly.

  We need to ensure we didn't include any boilerplate like EEO, application deadline, etc. We removed those. Check for any repeated content: we included all substantive info. We didn't include "Why You'll Love Us" culture content; but that could be considered benefits? However we already have benefits section; culture could be omitted as not required. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should include the "Why You’ll Love Us" content somewhere. It's about culture, diversity, inclusion, growth opportunities, etc. Could be placed under a section like "About the company" but we don't have that heading. We could add a section "Why you’ll love us" but not in allowed headings list. The allowed headings are limited to those enumerated. We could incorporate that content into "Benefits" or "About the role"? The instruction says use those headings for section headings. It doesn't forbid other headings, but says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, but we should likely stick to those. However we need to preserve all substantive information; if we omit the "Why You’ll Love Us" paragraph, we lose substantive info about culture, growth opportunities, etc. That would violate preserving all substantive info. So we need to include it somewhere, perhaps under a heading like "About the role" or "Benefits". But "Why You’ll Love Us" is more about culture and perks; could fit under "Benefits" as non‑monetary benefits (culture, growth opportunities). We can add bullet points under Benefits for those. Thus expand Benefits bullet list to include: - Culture of diversity and inclusion, programs that bring employees together on important issues and provide educational opportunities. - Opportunities to grow your career: encouragement to learn different aspects of the business, take on stretch assignments, seek coaching and professional development. - Dedication to improving product quality from a customer standpoint and enabling success of businesses, non‑profits, and community groups. We should keep the original benefits as well. Thus Benefits section will have multiple bullet points. Now ensure we didn't miss any other substantive info: The line "Vision6 Pty Limited is an affiliate of Constant Contact, Inc. and a part of the Constant Contact group of brands." That's maybe not substantive for the role; could be considered boilerplate? It's a corporate structure detail; maybe not needed for applicant. Could be considered metadata but not essential. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not exactly those categories, but it's still corporate info. Might be considered not essential. However it's substantive info about the company. The instruction says preserve ALL substantive information; but also says remove boilerplate. This line might be considered boilerplate (affiliate info). I'd lean to remove it as not directly relevant to the job. However it's not explicitly listed as boilerplate to remove. Safer to keep? The instruction says "remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This line is not those. So we should keep it if it's substantive. But it's not about the role; still could be considered company info. I'd keep it as a short paragraph maybe under About the role? But we already have About the role paragraph; we could add a sentence after that. But the instruction also says "Prefer a few substantive sections over many thin ones." Adding a small sentence may be okay. Let's add after About the role paragraph: "Vision6 Pty Limited is an affiliate of Constant Contact, Inc. and part of the Constant Contact group of brands." Now check for any other substantive info: "Application Deadline: 30 days. We may fill this job opening prior to the deadline if a candidate is selected by us." That's application instruction; remove. Also "We may fill this job opening prior to the deadline if a candidate is selected by us." That's also application instruction. Also "The contractor will not discharge or in any other manner discriminate..." that's legal boilerplate; remove. Also "However, employees who have access to the compensation information..." legal; remove. Also "It is unlawful in Massachusetts to require or administer a lie detector test..." legal; remove. Also "At Constant Contact, we respect personnel privacy..." legal/privacy; remove. Also "Notice to