Senior Engineer, Revenue SystemsLocation: NYC Reports to: CTOAbout NomicNomic builds AI agents and developer tools that power the built world. We help enterprise teams in architecture, engineering, and construction extract structured knowledge from decades of drawings, specs, and project files. Our platform combines embedding models, document parsing, and autonomous agents that reason over real-world data and take action in live environments.The RoleRevenue systems are the connective tissue between what we sell and what we ship.
We're hiring a Senior Engineer to own that surface—the integrations, data models, and pipelines that keep contracts, usage, and invoicing consistent and correct as we scale.Strong software engineering experience is the requirement. Revenue systems domain experience matters more than payments-infrastructure-from-scratch experience. The job is correctness: making sure the right things get billed, that HubSpot, our platform, and Tabs agree with each other, and that the whole pipeline runs without manual intervention.This is a senior IC role with broad ownership and real architectural influence.What You'll OwnHubSpot integration — deal terms and contract data flowing reliably into the platform; CRM and platform staying in syncContract and entitlement modeling — representing what's billable, what's recognized, and how contract terms map to dataTabs integration — usage and entitlements flowing out to invoicing automatically and correctlyReconciliation — keeping multiple sources of truth consistent and surfacing discrepancies before they become problemsIntegration standards — establishing the quality bar for how revenue-systems integrations get built and maintained going forwardWhat We're Looking ForStrong systems integration and data modeling skills — API/webhook integration, reconciliation, keeping sources of truth consistentRevenue or accounting domain sense — you understand how contracts, usage, and entitlements map to moneyComfortable building greenfield against tools that aren't fully spec'd yetProduction experience in Python and/or TypeScriptA correctness-first mindset — edge cases in billing aren't acceptableEven Better If You HaveExperience with CRM integrations (HubSpot, Salesforce, or similar)Background in billing, invoicing, or usage-based pricing systemsFamiliarity with B2B SaaS contract models — seat licenses, usage tiers, entitlementsExperience scaling revenue operations without adding headcount per customerHow to ApplySend a cover letter describing:A system you've built to keep two or more data sources consistentHow you think about correctness in financial or billing contextsTools and languages you'd reach for on day one