StaffSoftwareEngineer,MonetizationPlatform

10+ years of experience as a software engineer, meaningful time owning business-critical backend systems in production, Deep experience architecting billing, payments, pricing, or quote-to-cash systems for a B2B SaaS company at meaningful scale, experience designing APIs and event-driven systems that ingest, validate, aggregate, and reconcile high-volume operational data, understanding of modern billing models, including usage-based pricing, subscriptions, prepaid credits, commitments, overages, hybrid packaging, and enterprise-specific commercial terms, Experience working directly with Accounting, Finance, RevOps, and GTM systems where data quality, auditability, and timing matter, experience integrating with systems like Salesforce, CPQ, NetSuite, payment platforms, and downstream finance/reporting tooling, JavaScript/TypeScript and object-oriented programming, Building and consuming RESTful web services, Relational databases, data modeling, and transactional workflows, Distributed systems and asynchronous processing, Writing unit, integration, and end-to-end tests, Logging, telemetry, and production debugging, Git and modern CI/CD practices, At least one major cloud platform and modern infrastructure tooling, A product and systems mindset, Architected or modernized a billing system that had to support real usage metering, invoice correctness, and flexible commercial models rather than a single static subscription plan, Built systems where raw product activity was transformed into durable billing inputs and surfaced in customer-facing or internal financial workflows, Worked through pricing and packaging changes without repeatedly hardcoding logic into application code, Supported models like prepaid credits, subscriptions with overage, enterprise commitments, or hybrid contracts for different customer segments, Partnered directly with Finance, Accounting, and RevOps to close gaps between what the product did, what the customer bought, and what the company invoiced, Led engineers through ambiguous, cross-functional initiatives where the right answer required balancing correctness, flexibility, speed, and operational simplicity, Communicated complex architectural decisions clearly to both technical and non-technical stakeholders, Balanced individual contributor depth with mentoring and unblocking other engineers