Pricing & Order Operations Analyst

We need to output only HTML fragment, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info, no invented or summarized away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. Prefer few substantive sections over many thin ones. We need to parse the posting. Key sections: - About Us (but we shouldn't include as heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only include those headings if they have content. "About Us" is not in list; we could maybe treat as "About the role"? Actually there is "About The Role" heading. So we should include an

  About the role

  with content from that section. - There's also "About Us" earlier but that's company description; maybe we can incorporate into About the role? But instruction says only use those headings; we could still include other content in

  without heading? Probably we should keep substantive info but not create extra headings. So we can put company description in a

  before the About the role heading? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't forbid other tags like

  without heading. So we can include a

  for company overview. - Then "About The Role" content: includes description of role, reporting line, full-time remote position. We'll put that under

  About the role

  . - Then "Technologies You’ll Use" maybe could be considered part of Skills? But we have a Skills heading. Could include technologies under Skills? Or we could create a separate section? The instruction says prefer few substantive sections over many thin ones. Could combine Technologies into Skills or Responsibilities. Probably better to include under Skills heading as part of required skills. But we also have a separate "Skills We’re Looking For". So we can put technologies under Skills. - Then "What You’ll Do" with sub-sections: Pricing Operations & QTC Support, UAT & Testing, Order Operations. That's responsibilities. So we will have

  Responsibilities

  with
  • items. - Then "Skills We’re Looking For": list of skills. That's Skills heading. - Then compensation/pay: "The compensation range displayed on this job posting reflects..." plus "New York Pay Range $104,036—$124,848 USD". So we have pay info. So we should create

    Pay

    with that info. - Then "Perks And Benefits": list of benefits. So

    Benefits

    with
    • . - Then there is other content about values, diversity, accommodations etc. That's boilerplate? It's EEO/diversity statement; we should remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove that. - Also "Click here to learn more about Fivetran's Benefits by Region." maybe part of benefits but it's a link; we can keep as part of benefits? It's a link; but we can keep as

      maybe. However instruction: remove duplicated lines, application instructions. This is not application instruction but a link. Might be okay to keep as part of benefits. - Also "We’re honored to be valued at over $5.6 billion..." etc. That's company info; could be included in a

      before About the role? Might be considered boilerplate? It's not EEO; it's about company. Might be okay to keep as a brief overview. But we already have company description earlier. Might be duplicate. We can keep one. - Also "To learn more about Fivetran’s culture..." etc. That's also boilerplate; maybe remove. - Also "To learn more about our candidate privacy policy..." etc. That's legal; remove. - Also "We are committed to ensuring that all candidates have an equal opportunity..." that's EEO; remove. Thus final HTML: maybe start with a

      company overview (from first paragraph). Then

      About the role

      with

      content. Then

      Responsibilities

      with
      . Then

      Skills

      with
      . Then

      Pay

      with

      . Then

      Benefits

      with
      . Possibly also

      Schedule

      if schedule info present: "This is a full-time remote position." That's schedule info (full-time, remote). So we could include Schedule heading with that. But we already mentioned full-time remote in About the role; but we could still create Schedule heading. However instruction: prefer few substantive sections over many thin ones. Could combine schedule into About the role or Pay? But schedule is separate info; we could include Schedule heading with that sentence. However we already have full-time remote in About the role; we could avoid duplication by not repeating. But we need to preserve all substantive info; we can keep it in About the role and not create Schedule heading if it's redundant. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". If we already have schedule info in About the role, we could still create Schedule heading but would duplicate content. Better to not create Schedule heading to avoid thin section. So we will not include Schedule. Now let's extract content. Company overview: first paragraph: "From Fivetran’s founding until now, our mission has remained the same: to make access to data as simple and reliable as electricity. With Fivetran, customer data arrives in their warehouses, canonical and ready to query, with no engineering or maintenance required. We’re proud that more organizations continue to leverage our technology every day to become truly data-driven." Then "About Us Fivetran and dbt Labs are bringing together two industry-leading companies with a shared mission: helping organizations unlock the full value of their data. Together, we’re delivering the data infrastructure layer that helps organizations move, transform, and trust their data — from the moment data moves, through every transformation, to the context teams and AI systems rely on. Fivetran helps organizations automate data movement across the systems, clouds, engines, and tools they rely on. dbt Labs pioneered analytics engineering, helping teams transform data into reliable, governed insights. Together, we support thousands of organizations as they build a trusted foundation for analytics, AI, and better business decisions. As we bring our teams and technology together, we’re building on both companies' strengths while continuing to deliver the products and experiences our customers know and trust. It’s an exciting time to join us: we’re creating a company with the scale, talent, and technology to help more organizations put their data to work with greater speed, confidence, and impact. During this transition period, you may see references to both Fivetran and dbt Labs throughout our recruiting process as we integrate our teams, systems, and career sites." That's a lot; we can keep as

      maybe combined. Now About the role: heading

      About the role

      . Content: "Fivetran is building data pipelines to power the modern data stack for thousands of companies. We’re looking for a Pricing & Order Operations Analyst to join our Order Operations & Monetization team. This role restores dedicated capacity for pricing and order operations testing, quote-to-cash (QTC) release validation, and order execution support. You’ll help ensure system changes are tested, validated, and operationally ready before they go live. You’ll provide Pricing and Order Operations subject-matter expertise and execute assigned business validation across signature packets, bookings, marketplace offers, and booking-to-order management handoffs. This role partners closely with Order Operations & Monetization, IT’s business systems team, Pricing Operations, Sales, and Deal Desk. Reporting & Prioritization Reports to the Order Operations & Monetization lead, Jamie Calkins.The Senior Pricing Operations Manager may help prioritize pricing-related test cases and QTC issues tied specifically to pricing and quoting.The Order Operations & Monetization lead owns final prioritization of the analyst’s workload across order operations, assigned non-pricing UAT participation, and pricing-related support work. This is a full-time remote position." We need to keep that as

      maybe multiple paragraphs but we can combine. Now Responsibilities: we have "What You’ll Do" with subheadings. We'll create

      • items for each bullet. Let's list bullet points: Under Pricing Operations & QTC Support: - Support pricing operations changes through business requirement review, data validation, configuration checks, and documentation, helping ensure pricing logic is accurately reflected in QTC workflows. - Validate pricing-related QTC changes across quoting, approvals, discounting logic, product configuration, and downstream order execution. - Help confirm that pricing changes are operationally ready before launch, including impacts to Sales, Deal Desk, Order Operations, Billing, Revenue, and marketplace workflows. - Partner with the Senior Pricing Operations Manager to prioritize pricing-related test cases, identify gaps in business requirements, and document expected system behavior. - Help maintain documentation for pricing- and order-related system configurations, known dependencies, and release-readiness criteria. Under UAT & Testing: - Participate as a Pricing and Order Operations subject-matter expert in UAT project-managed by Technical Program Management (TPM) and executed under RevOps coordination, ensuring relevant business scenarios and expected outcomes are represented. - Execute assigned Pricing and Order Operations test cases and collaborate with the GTM subject-matter experts identified by RevOps. - Partner with RevOps and relevant subject-matter experts to develop and maintain Pricing and Order Operations test cases, including scenarios for quoting, approvals, signature packets, bookings, marketplace offers, billing, and order management. - Document test results and defects with clear traceability from business requirement to test outcome, and provide domain-specific readiness input through the established UAT sign-off process. - Maintain the Pricing and Order Operations portion of the regression test suite for recurring QTC changes. Under Order Operations: - Operate under defined business requirements for order operations rules within the QTC flow, validating execution across signature packet generation and e-signature routing, booking rules, marketplace offer configuration—including AWS, Azure, GCP, and Snowflake—and the booking-to-order management handoff. - Partner with IT’s business systems team and the Proposal-to-Order Lead to keep order operations rules aligned with upstream pricing and quoting logic and downstream billing and revenue systems. - Ensure signature packets and marketplace offers accurately reflect the underlying order and pricing terms before execution. - Identify and troubleshoot order operations issues across bookings, signature packets, and marketplace offers, escalating systemic problems to the appropriate system owner. Now Skills: list: - 2–3 years of experience in pricing operations, order operations, business systems analysis, or quality assurance within an agile environment, ideally involving quote-to-cash processes. - Working knowledge of Salesforce CPQ and order management or billing systems, with the ability to read and understand configuration logic without necessarily building it directly. - Strong attention to detail and comfort performing structured, repeatable testing work. - Comfort using conversational AI tools—such as Claude, ChatGPT, or internal chatbots—to support daily and project work, combined with sound judgment about when human review or