Open role · Engineering

Software Engineer, Monetization

Work mode: Remote (EST preferred) Engagement type: Full-time Contract Req ID: GDBI-5O7Q9L3N

Role summary

Build the systems behind subscription plans, entitlements, usage metering, billing, invoicing, payments and revenue workflows for NoèmeX products and enterprise customers.

What you’ll do

  • Design billing and pricing architecture that can support subscriptions, add-ons, enterprise licensing and usage-based models.
  • Build usage metering for AI, data processing, storage and other billable product consumption.
  • Develop subscription, entitlement, invoicing, payment and credit/refund workflows with strong correctness guarantees.
  • Integrate monetization services with CRM, ERP and finance systems supporting quote-to-cash processes.
  • Improve observability, reconciliation, audit trails and controls around financial transactions.
  • Partner with Product, Finance, Sales and Customer Success to turn commercial models into reliable software.

What you should bring

  • Senior-level backend engineering experience in transaction-heavy or correctness-sensitive systems.
  • Strong system design, relational data modeling and API design skills.
  • Experience with distributed systems concepts such as idempotency, consistency and failure recovery.
  • Production experience with languages such as Python, Java, Node.js or Go and relational databases.
  • Ability to work with financial, sales and product stakeholders on ambiguous requirements.
  • Strong attention to correctness, auditability and operational reliability.

Useful additional experience

  • Billing or subscription platforms such as Stripe, Chargebee or Zuora
  • ASC 606 / IFRS 15 familiarity
  • Quote-to-cash and CRM/ERP integrations
  • Multi-currency or international payments

How we work

NoèmeX teams stay close to the business problem and the production system. You may work across client delivery, platform development or internal capabilities depending on the role. We value clear specifications, maintainable architecture, disciplined execution and direct communication.

Hiring process

The exact assessment varies by role. Shortlisted candidates should expect an initial conversation followed by a role-relevant technical, practical or structured panel assessment before a final decision.

Submit your application.

Provide the information required for this role. Applications are reviewed using the recruitment process described in our recruiting privacy policy.

Your home address is required for this application and is handled under our recruiting privacy policy. Do not include passport numbers, SIN/SSN, financial account details or other sensitive government identifiers.

Used to send your verification link and updates for this application.
Used only if we need to clarify availability or interview scheduling.
Helps us understand work authorization constraints for client environments.
Add a second country of citizenship if you hold dual or multiple citizenship. Leave this blank if it does not apply.
Helps align timezone, tax/vendor setup, and client access requirements.
Select your address from the list to fill the fields below automatically, or enter them manually - this box does not need to work for your application to go through.
Please enter your rate in your local currency, based on your country of residence.
Consider Europe broadly here (for example the EU, the UK, or Switzerland). Work authorization is granted by individual countries, not the EU as a whole, so we'll ask which country if that matters for your answer.
An employer-specific (closed) work permit only authorizes you to work for the employer named on it.
Most US work visas are tied to a specific sponsoring employer - let us know which one applies.
Used for fast background context (roles, dates, industries). No automated posting.
Used to review work samples where relevant (code, dashboards, writeups).
This is required so we can score applications consistently. Please paste the text directly rather than emailing your resume separately - do not include passport numbers, SIN/SSN, financial account details or other sensitive government identifiers.
Optional supporting link. If provided, it must be accessible without logging in (e.g., "anyone with the link can view").