Pricing & Order Operations Analyst
About the role
. Then responsibilities: "What You’ll Do" includes bullet points; we can put under Responsibilities. Requirements: maybe "Skills We’re Looking For" includes experience etc. Qualifications maybe not separate; but we can treat Skills as separate. Benefits: "Perks And Benefits". Pay: not specified; we should NOT include Pay unless stated. Schedule: "This is a full-time remote position." That's schedule info (full-time remote). So we can include Schedule section with that sentence. We must not include boilerplate like EEO etc. Remove navigation etc. Also remove duplicated lines. Keep all substantive info. We need to use for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. Not include Job ID.
We need to preserve all substantive info: About Us? The posting includes "About Us" describing Fivetran and dbt Labs. Should we include that? The instruction: "use
for section headings (e.g. 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)." Likely they expect only those headings. However we could include an "About the company" section? Not in list; maybe we should not create extra headings. The About Us content could be placed under About the role? But that seems odd. Perhaps we can include an "About the role" section that includes the description of the role and also the company mission? The "About The Role" heading exists in the posting. So we map that to About the role. The "About Us" preceding that could be considered company overview; maybe we can incorporate into About the role as prose. 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 other headings, but they gave examples. Safer to stick to those headings only. So we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. Possibly also Qualifications if we have content; but we may not have separate qualifications beyond skills. Could combine Requirements and Qualifications? But we need to follow instruction: include a section ONLY when posting has real, specific content for it. We have content for Skills (list). For Requirements we have "1–3 years of experience..." etc. That's requirements. Qualifications maybe not distinct; we could omit Qualifications if no specific content beyond skills. Benefits we have. Schedule we have. Pay not present, omit.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule.
Now we need to extract content.
About the role: Should include the paragraph(s) under "About The Role". Let's capture:
"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 should keep that as prose in
. Possibly break into multiple paragraphs but okay.
Responsibilities: Under "What You’ll Do" with subheadings: Pricing Operations & QTC Support, UAT & Testing, Order Operations. We'll combine into a list of duties. Could keep subheadings as
maybe but instruction: use
- for any list of duties/requirements/benefits. So we can create a
with each duty as - . Might be long but okay.
Let's extract bullet points:
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.
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.
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.
We'll put each as
- .
Requirements: Under "Skills We’re Looking For" includes experience etc. Also maybe "Bonus Skills". We'll treat requirements as the bullet list of required skills. Let's extract:
- 1–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 decision-making is necessary.
- Clear written communication skills, with the ability to document test cases, defects, and sign-off criteria for technical and business audiences.
- A proactive and organized approach, with the ability to work across IT, Pricing and Order Operations, and Sales and Deal Desk without heavy oversight.
Bonus skills: Exposure to Revenue Recognition or Professional Services systems and processes. Could be included as optional but still content; we could add as another
- maybe marked as bonus. But we can include as part of Requirements or Skills. Since we have separate Skills section, maybe we put required experience under Requirements, and Skills under Skills. However the list includes both experience and skills. Could split: Requirements = experience and maybe working knowledge; Skills = attention to detail, AI tools, communication, proactive approach. But the instruction says use sections as needed. We could have Requirements (experience) and Skills (soft skills). Let's do that.
Thus Requirements section: list of experience and knowledge.
Skills section: list of soft skills and maybe bonus.
But we also have "Skills We’re Looking For" heading includes both experience and soft skills. To avoid duplication, we could put all under Skills and omit Requirements. However we need to follow instruction: include a section only when posting has real specific content. It does have specific content for skills/experience. Could just have Skills section covering all. But they also have separate Requirements and Qualifications examples; we can decide to include Requirements (experience) and Skills (soft skills). Let's do that.
Thus:
Requirements:
- 1–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.
Skills:
- 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 decision-making is necessary.
- Clear written communication skills, with the ability to document test cases, defects, and sign-off criteria for technical and business audiences.
- A proactive and organized approach, with the ability to work across IT, Pricing and Order Operations, and Sales and Deal Desk without heavy oversight.
- Bonus: Exposure to Revenue Recognition or Professional Services systems and processes.
Benefits: Under "Perks And Benefits". List:
- 100% employer-paid medical insurance
- Generous paid time-off policy (PTO), plus paid sick time, inclusive parental leave policy, holidays (including a year end Global Week of Rest), and volunteer days off
- RSU stock grants*
- Professional development and training opportunities
- Company virtual happy hours, free food, and fun team-building activities
- Monthly cell phone stipend
- Access to an innovative mental health support platform that offers personalized care and resources in areas such as: therapy, coaching, and self-guided mindfulness exercises for all covered employees and their covered dependents.
- *May vary by country and worker type - please reach out to your recruiter for more information Click here to learn more about Fivetran's Benefits by Region.
We need to keep the note about RSU stock grants* and the footnote. Keep as is.
Schedule: "This is a full-time remote position." Already mentioned in About the role but we can still include schedule section with that sentence.
Now produce HTML fragment.
We must not include markdown fences. Just raw HTML.
Let's craft:
About the role
... (the paragraph)
Responsibilities
- ... each duty
...
Requirements
- ... experience
- ... working knowledge
Skills
- ... attention to detail
- ... comfort using conversational AI tools...
- ... clear written communication skills...
for prose. We must not repeat job title as heading. Not include Job ID. We need to preserve all substantive info: About Us? The posting includes "About Us" describing Fivetran and dbt Labs. Should we include that? The instruction: "use
for section headings (e.g. 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)." Likely they expect only those headings. However we could include an "About the company" section? Not in list; maybe we should not create extra headings. The About Us content could be placed under About the role? But that seems odd. Perhaps we can include an "About the role" section that includes the description of the role and also the company mission? The "About The Role" heading exists in the posting. So we map that to About the role. The "About Us" preceding that could be considered company overview; maybe we can incorporate into About the role as prose. 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 other headings, but they gave examples. Safer to stick to those headings only. So we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. Possibly also Qualifications if we have content; but we may not have separate qualifications beyond skills. Could combine Requirements and Qualifications? But we need to follow instruction: include a section ONLY when posting has real, specific content for it. We have content for Skills (list). For Requirements we have "1–3 years of experience..." etc. That's requirements. Qualifications maybe not distinct; we could omit Qualifications if no specific content beyond skills. Benefits we have. Schedule we have. Pay not present, omit. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule. Now we need to extract content. About the role: Should include the paragraph(s) under "About The Role". Let's capture: "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 should keep that as prose in
. Possibly break into multiple paragraphs but okay. Responsibilities: Under "What You’ll Do" with subheadings: Pricing Operations & QTC Support, UAT & Testing, Order Operations. We'll combine into a list of duties. Could keep subheadings as
maybe but instruction: use
- for any list of duties/requirements/benefits. So we can create a
- with each duty as
- . Might be long but okay. Let's extract bullet points: 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. 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. 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. We'll put each as
- . Requirements: Under "Skills We’re Looking For" includes experience etc. Also maybe "Bonus Skills". We'll treat requirements as the bullet list of required skills. Let's extract: - 1–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 decision-making is necessary. - Clear written communication skills, with the ability to document test cases, defects, and sign-off criteria for technical and business audiences. - A proactive and organized approach, with the ability to work across IT, Pricing and Order Operations, and Sales and Deal Desk without heavy oversight. Bonus skills: Exposure to Revenue Recognition or Professional Services systems and processes. Could be included as optional but still content; we could add as another
- maybe marked as bonus. But we can include as part of Requirements or Skills. Since we have separate Skills section, maybe we put required experience under Requirements, and Skills under Skills. However the list includes both experience and skills. Could split: Requirements = experience and maybe working knowledge; Skills = attention to detail, AI tools, communication, proactive approach. But the instruction says use sections as needed. We could have Requirements (experience) and Skills (soft skills). Let's do that.
Thus Requirements section: list of experience and knowledge.
Skills section: list of soft skills and maybe bonus.
But we also have "Skills We’re Looking For" heading includes both experience and soft skills. To avoid duplication, we could put all under Skills and omit Requirements. However we need to follow instruction: include a section only when posting has real specific content. It does have specific content for skills/experience. Could just have Skills section covering all. But they also have separate Requirements and Qualifications examples; we can decide to include Requirements (experience) and Skills (soft skills). Let's do that.
Thus:
Requirements:
- 1–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.
Skills:
- 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 decision-making is necessary.
- Clear written communication skills, with the ability to document test cases, defects, and sign-off criteria for technical and business audiences.
- A proactive and organized approach, with the ability to work across IT, Pricing and Order Operations, and Sales and Deal Desk without heavy oversight.
- Bonus: Exposure to Revenue Recognition or Professional Services systems and processes.
Benefits: Under "Perks And Benefits". List:
- 100% employer-paid medical insurance
- Generous paid time-off policy (PTO), plus paid sick time, inclusive parental leave policy, holidays (including a year end Global Week of Rest), and volunteer days off
- RSU stock grants*
- Professional development and training opportunities
- Company virtual happy hours, free food, and fun team-building activities
- Monthly cell phone stipend
- Access to an innovative mental health support platform that offers personalized care and resources in areas such as: therapy, coaching, and self-guided mindfulness exercises for all covered employees and their covered dependents.
- *May vary by country and worker type - please reach out to your recruiter for more information Click here to learn more about Fivetran's Benefits by Region.
We need to keep the note about RSU stock grants* and the footnote. Keep as is.
Schedule: "This is a full-time remote position." Already mentioned in About the role but we can still include schedule section with that sentence.
Now produce HTML fragment.
We must not include markdown fences. Just raw HTML.
Let's craft:
About the role
... (the paragraph)
Responsibilities
- ... each duty ...
Requirements
- ... experience
- ... working knowledge
Skills
- ... attention to detail
- ... comfort using conversational AI tools...
- ... clear written communication skills...