We are looking for a highly analytical and technically proficient QA Engineer to take ownership of our Opportunity-to-Cash (O2C) and Enterprise Billing testing. In this role, you will act as a quality gatekeeper for the financial systems that drive our business.

You will join the BOBA Frameworks QA team — a small, high-ownership team embedded in the Finance engineering organization — where quality directly impacts revenue accuracy and customer trust.

You will not just be executing test cases; you will be mapping out complex data flows that span across Salesforce CPQ, our middleware, our Billing Platform, our payment gateways (Braintree), and our NetSuite ERP. If you are a critical thinker who understands the financial domino effect of a failed sync, loves unraveling usage-based billing logic, and thrives in cross-functional collaboration, we want you on our team.

What You Will Do (Key Responsibilities)

• End-to-End Pipeline Ownership:
• Execute comprehensive test strategies for our entire Opportunity-to-Cash lifecycle.
• Trace data payloads from the moment an order is created in Salesforce CPQ to the moment the final journal entry hits NetSuite.
• Complex Billing Lifecycle Validation:
• Take ownership of testing our Enterprise Billing Platform.
• Rigorously validate invoice generation, taxation (Avalara), proration, discounts, credits, tiered and usage-based pricing models, credit memo issuances, and dunning (collections) workflows.
• Test Plan & Coverage Ownership:
• Own and maintain structured test plans in Xray for all buying programs (PAYG, Savings Plan, Volume Plan).
• Ensure traceability from requirements to execution across every billing lifecycle stage.
• Payment Gateway & Ledger Allocation Testing:
• Take ownership of end-to-end payment flows through Braintree.
• Validate successful authorizations, settlements, and complex edge cases like partial refunds on multi-invoice payments.
• Ensure funds are accurately handled (e.g., proper allocation vs. unallocated amounts) and invoice statuses remain correct across systems.
• Usage & Consumption Testing:
• Deep-dive into our usage-based billing models.
• Simulate high-volume usage data, validate tier drawdown logic, and ensure overages are calculated with absolute precision.
• Cross-System Integration Testing:
• Perform robust integration testing across our financial tech stack.
• Validate API payloads, investigate failed background syncs, and ensure data integrity between Salesforce, Billing Platform, NetSuite, and Braintree.
• Defect Triage & Root Cause Analysis:
• Investigate system logs and identify exactly where a data sync broke down.
• Provide developers with clear, actionable reproduction steps beyond just reporting bugs.
• Cross-Functional Collaboration:
• Act as the bridge between Engineering, Product, and Finance.Partner with business stakeholders to understand complex revenue rules and translate them into foolproof test scenarios.

What Success Looks Like (Your First Year)

• Day 30 — Architecture & Ownership: You've mapped the full Quote-to-Cash pipeline end-to-end: Salesforce CPQ → Boomi/PASS provisioning → Billing Platform → NetSuite → Avalara & Braintree. You've taken full ownership of the Xray test repository and can explain which test cases cover which buying program, workstream, and billing lifecycle stage without being asked.
• Day 60 — Independent Execution: You independently execute QA for a complete enterprise billing lifecycle — from contract activation through invoice approval, tax calculation, and payment processing — and close it without escalation. You've begun triaging Billing Platform → NetSuite sync failures and Boomi provisioning errors on your own, and you understand the difference between a defect and expected system behavior.
• Day 90 — Primary Sign-Off: You are the QA gate for all cross-system financial deployments. Engineering ships nothing that touches CPQ, Billing Platform, or NetSuite without your sign-off. You've established a defect triage process in Jira and Xray that gives Engineering and Finance a shared, real-time view of quality — eliminating the back-and-forth that slows down deployments.
• Year 1 — Measurable Impact: Critical post-deployment data sync errors between CPQ and NetSuite have dropped measurably. Every active buying program — PAYG, Savings Plan, and Volume Plan — has standardized, Xray-tracked test coverage for usage-based billing, commitment invoicing, contract lifecycle boundaries, and edge cases. The team ships faster because QA is a multiplier, not a bottleneck.

What You Bring to the Table (Required Experience)

• O2C Domain Expertise: 4+ years of QA experience with a heavy focus on Quote-to-Cash / Order-to-Cash business processes. You understand the "why" behind financial transactions, not just the "how."
• Salesforce CPQ: Hands-on experience configuring and testing quotes, product bundles, amendments, and contract renewals within Salesforce CPQ.
• Enterprise Billing Platforms: Proven experience testing complex billing systems such as BillingPlatform, Zuora, or similar financial engines.
• Payment Processing & Gateways: Hands-on experience testing enterprise payment gateways (Braintree heavily preferred; Stripe or Adyen acceptable). You possess a deep functional understanding of payment lifecycles (Auth, Capture, Settle, Refund) and how gateway actions impact Accounts Receivable (AR) balances.
• Integration Middleware: Familiarity with provisioning and event-driven middleware (Boomi or equivalent). You can read a payload log and identify where in the chain a sync broke.
• Test Management & Agile Tools: Proficient in Jira for defect tracking and Agile workflows, with strong hands-on experience using Xray as a test management tool. You know how to navigate structured test plans, manage test executions, and maintain strict traceability between bugs, test cases, and product requirements.
• Usage-Based Models: Familiarity with testing consumption-based pricing, tiered pricing, drawdown models, and metered billing logic.
• Integration & API Verification: Experience validating data transfers between systems (using tools like Postman or validating middleware logs). You know how to prove a system sent the right data even if the UI hasn't updated yet.
• Taxation & Compliance Tools: Familiarity with enterprise taxation calculation software like Avalara.

Who You Are (Soft Skills)

• A System-Level Thinker: You understand that missing a prerequisite step — like failing to approve a usage invoice before uploading the next month's consumption — breaks the entire downstream flow.
• Self-Driven Investigator: When a test fails, you don't just throw it back to Dev. You dig into the documentation and logs to help figure out exactly what went wrong.
• Exceptional Communicator: You can clearly explain a complex API sync failure to an engineer, and then turn around and explain the business impact of that failure to a Finance Manager.
• Detail-Obsessive Under Ambiguity: Financial test data is rarely clean. You know how to set up a controlled test environment, isolate variables, and still reach a confident pass/fail verdict even when upstream systems are noisy.