Pricing & Order Operations Analyst
Fivetran · Austin, CO · 3 wk ago
RemoteRemoteManufacturing$104k–$125k/yrFull-time
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 must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invention. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions.
We need to parse the posting.
Key sections:
- About Us (but we need About the role? Actually "About The Role" heading present. We'll use
About the role
and put content from that section. - "About Us" maybe not needed as a section; but we could include as part of About the role? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. The posting includes "About The Role" which we map to About the role. - Then "What You'll Do" corresponds to Responsibilities. - Then "Skills We're Looking For" corresponds to Skills (maybe also Requirements/Qualifications). There's also "Bonus Skills". Could treat as Skills. - There's also "Technologies You'll Use" maybe part of Skills or Requirements? Could be under Skills or Requirements. We'll include under Skills maybe as bullet list. - There's also "Pay Range" => Pay section. - "Perks And Benefits" => Benefits section. - Schedule: The posting says "This is a full-time remote position." That's schedule info (full-time, remote). So we can include Schedule section with that. - Requirements/Qualifications: The posting includes "2–3 years of experience..." etc. That's qualifications/requirements. We'll put under Requirements (or Qualifications). Since both headings allowed, we need to decide. Probably combine experience and knowledge under Requirements. Qualifications maybe education? Not present. Could leave Qualifications empty -> not include. So we will include Requirements. - Also there is "About Us" content about mission etc. Could be part of About the role? But we already have About the role content. The "About Us" is more company overview; maybe we could include as part of About the role? But instruction: include a section ONLY when posting has real, specific content for it. The About the role section we have content from "About The Role". The "About Us" could be considered company overview, not required. Could omit. We must not include boilerplate like EEO, accommodations, etc. We must preserve all substantive information. So we need to include details from each relevant section. Let's extract content: About The Role: "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 preserve all that. We'll put inmaybe multiple paragraphs. Responsibilities (What You'll Do): We have two sub-sections: Pricing Operations & QTC Support, UAT & Testing, Order Operations. We need to capture bullet points? The text is prose with sentences. We'll keep as
maybe break into paragraphs for each bullet? Could use
- for list of duties. The instruction: Use
- for any list of duties/requirements/benefits. So we should convert the duties into list items.
Let's list duties:
From 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.
From 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.
From 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 these as
- items.
Requirements:
From "Skills We're Looking For" (the bullet list) plus maybe "Technologies You'll Use". Also "Bonus Skills". We'll treat as requirements.
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 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.
Technologies You'll Use:
- Salesforce CPQ
- Jira
- Suger and marketplace user interfaces, including AWS, Azure, GCP, and Snowflake
- Notion
- Metronome
- Hex
We could include these under Requirements or Skills. Since Skills heading already used for skills list, we could put technologies under Skills as well. But we already have Skills list; we could add another
- under Skills for technologies. Or we could create a separate section like "Technologies" but not in allowed headings. So we incorporate into Skills.
Thus Skills section will contain both skill requirements and technologies.
But we also have a separate Skills heading; we can put all skill-related content there.
Thus we will not have a separate Requirements section? But we need to include Requirements if we have content. The experience etc could be considered Requirements. We could put them under Requirements. Then Skills could be more about abilities like attention to detail, communication, etc. However the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Skills.
Thus we split:
Requirements: experience, working knowledge of Salesforce CPQ, etc. Also maybe technologies.
Skills: attention to detail, comfort with AI tools, written communication, proactive approach, bonus exposure.
But we also have "Bonus Skills". Could be under Skills.
Let's decide:
Requirements:
- 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.
- Familiarity with the technologies used: Salesforce CPQ, Jira, Suger and marketplace user interfaces (AWS, Azure, GCP, Snowflake), Notion, Metronome, Hex.
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.
That seems reasonable.
Now Benefits: list from "Perks And Benefits". We'll extract bullet points.
Perks And Benefits:
- 100% employer-paid medical insurance
- Generous paid time away from work, including paid vacation or flexible/unlimited vacation depending on role and country, plus paid sick time, inclusive parental leave, paid 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
We should keep the asterisk note maybe as part of the RSU stock grants item.
We'll output as
- .
Pay: we have Pay Range $104,036—$124,848 USD. We'll output as
Pay Range: $104,036—$124,848 USD
. Schedule: "This is a full-time remote position." We'll output asFull-time remote position.
. Now About the role: we need to output the content from About The Role as prose (). Could be multiple paragraphs. We'll keep as maybe two paragraphs: first paragraph describing role, second about reporting and prioritization, third about full-time remote. Let's craft: Paragraph 1: "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
- .
Pay: we have Pay Range $104,036—$124,848 USD. We'll output as
- items.
Requirements:
From "Skills We're Looking For" (the bullet list) plus maybe "Technologies You'll Use". Also "Bonus Skills". We'll treat as requirements.
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 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.
Technologies You'll Use:
- Salesforce CPQ
- Jira
- Suger and marketplace user interfaces, including AWS, Azure, GCP, and Snowflake
- Notion
- Metronome
- Hex
We could include these under Requirements or Skills. Since Skills heading already used for skills list, we could put technologies under Skills as well. But we already have Skills list; we could add another
- for any list of duties/requirements/benefits. So we should convert the duties into list items.
Let's list duties:
From 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.
From 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.
From 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 these as