Nomic.Ai

Software Engineer, Revenue Systems

🇺🇸 New York, Vereinigte Staaten, New York City, Vereinigte Staaten Vor Ort IT Senior Veröffentlicht Jun 2, 2026
Arbeitsort Vor Ort
Seniorität Senior
Kategorie IT
IT-Kategorie Backend Engineer
Sprache English
Veröffentlicht 2. Juni 2026
Zuletzt geprüft 2. Juni 2026

Wo diese Rolle verfügbar ist

Standardmäßig eingeklappt, damit die Stellenbeschreibung gut lesbar bleibt.

2 Standorte
Vereinigte Staaten
  • New York, Vereinigte Staaten
  • New York City, Vereinigte Staaten
JobGrid-Kontext

Rollenübersicht von JobGrid

Software Engineer, Revenue Systems at Nomic.Ai in New York, United States, with an on-site setup. JobGrid classifies it as an IT, Back End Engineer role at senior level; no employment type or salary is provided in the payload. The record was posted on 2026-06-02 and last checked on 2026-06-02, and candidates are sent to the original public application page with non-personal referral parameters.

  • Normalized role facts: title, company, New York location, on-site workplace, seniority, and IT / Back End Engineer classification.
  • Source freshness is captured from the posted and last-checked timestamps in the payload.
  • The employer content is kept separate; JobGrid uses structured facts from the original posting rather than repeating employer copy.
  • Application routing goes to the original public application page, with non-personal referral parameters appended.

Senior Engineer, Revenue Systems

Location: NYC Reports to: CTO


About Nomic

Nomic 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 Role

Revenue 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 Own

  • HubSpot integration — deal terms and contract data flowing reliably into the platform; CRM and platform staying in sync

  • Contract and entitlement modeling — representing what's billable, what's recognized, and how contract terms map to data

  • Tabs integration — usage and entitlements flowing out to invoicing automatically and correctly

  • Reconciliation — keeping multiple sources of truth consistent and surfacing discrepancies before they become problems

  • Integration standards — establishing the quality bar for how revenue-systems integrations get built and maintained going forward

What We're Looking For

  • Strong systems integration and data modeling skills — API/webhook integration, reconciliation, keeping sources of truth consistent

  • Revenue or accounting domain sense — you understand how contracts, usage, and entitlements map to money

  • Comfortable building greenfield against tools that aren't fully spec'd yet

  • Production experience in Python and/or TypeScript

  • A correctness-first mindset — edge cases in billing aren't acceptable

Even better if you have:

  • Experience with CRM integrations (HubSpot, Salesforce, or similar)

  • Background in billing, invoicing, or usage-based pricing systems

  • Familiarity with B2B SaaS contract models — seat licenses, usage tiers, entitlements

  • Experience scaling revenue operations without adding headcount per customer

How to Apply

Send a cover letter describing:

  • A system you've built to keep two or more data sources consistent

  • How you think about correctness in financial or billing contexts

  • Tools and languages you'd reach for on day one