Senior Software Engineer, Konnect Admin/Billing

Kong Inc.

Get hot jobs first on Telegram

New positions appear faster in our channel

Location: Canada, United States
Job Type: full-time
Work Format: 🌍 Remote
Salary: $150K – $175K • Offers Equity • Offers Bonus
Posted: September 11, 2026

Job Description

Kong has different base pay ranges for different work locations within the United States and Canada, which allows us to pay employees competitively and consistently in different geographic markets. Compensation varies depending on a wide array of factors, including but not limited to specific candidate location, role, skill set and level of experience. Certain roles are eligible for additional rewards including sales incentives depending on the terms of the applicable plan and role. Benefits may vary depending on location. US based employees are typically offered access to healthcare benefits, a 401(k) plan, short and long term disability benefits, basic life and AD&D insurance, among others.

OverviewApplication

Are you ready to unlock intelligence?

If you don’t think you meet all of the criteria below but are still interested in the job, please apply. Nobody checks every box - we’re looking for candidates that are particularly strong in a few areas, and have some interest and capabilities in others.

About the Role:

The Senior Software Engineer will be a core member of the Billing Platform Team, designing and implementing the microservices and integrations that power Kong's commercial infrastructure. You'll build scalable, reliable TypeScript services that handle the full customer billing lifecycle, from trial signup through enterprise subscription provisioning and consumption metering. This role requires deep experience with distributed systems, event-driven architectures, and third-party financial platform integrations, combined with strong ownership instincts and the ability to operate in a domain where correctness is not optional.

What You'll Do:

Design, develop, and maintain TypeScript microservices that power billing lifecycle management across self-serve and enterprise plan models.
Build and evolve integrations with payment processing, usage metering, and CRM platforms to support contract and entitlement synchronization.
Implement reliable event-driven workflows using Kafka or similar platforms to process contract events, provision entitlements, and trigger billing state transitions.
Design and maintain the entitlement enforcement layer that gates product access based on plan type and contract state across Kong's multi-tenant platform.
Own the provisioning pipeline that maps closed sales opportunities to live org configurations, reducing manual intervention and human error.
Collaborate with product managers, RevOps, and finance stakeholders to translate billing requirements into reliable, auditable system behavior.
Build and improve internal tooling for billing operations, including admin interfaces used by customer support and finance teams.
Write clean, maintainable, well-tested code with comprehensive unit, integration, and end-to-end tests across a high-stakes financial domain.
Participate in code reviews, design discussions, and architecture planning with a focus on correctness, idempotency, and operational resilience.
Participate in on-call rotation and own incident response for billing platform services.
Mentor junior engineers and contribute to a culture of engineering rigor and operational accountability.

What You'll Bring:

5+ years of professional software engineering experience building backend services and distributed systems.
Strong proficiency in TypeScript and Node.js with experience building production microservices using frameworks such as NestJS.
Deep experience with relational databases (PostgreSQL or similar) including schema design, query optimization, and data modeling for financial or transactional domains.
Experience designing and building event-driven architectures using Kafka, SQS, or similar messaging platforms.
Proven experience integrating with third-party financial or billing platforms such as Stripe, Zuora, Chargebee, or usage metering systems.
Strong understanding of distributed systems concepts including consistency, idempotency, eventual consistency, and failure recovery in financial workflows.
Experience building microservices that consume and produce CRM events as part of automated provisioning or fulfillment workflows.
Solid understanding of multi-tenant SaaS architecture and the complexity of enforcing per-org entitlements at scale.
Experience with Kubernetes and container orchestration for deploying and operating production services.
Strong computer science fundamentals including data structures, algorithms, and system design.
Experience with CI/CD pipelines and tools such as GitHub Actions or Jenkins.
Demonstrated skills using code repositories and collaboration tools (GitHub, JIRA, Confluence, or similar).
Experience working with globally distributed teams.
Excellent problem-solving skills and ability to debug complex data consistency issues across distributed systems.

Bonus Points:

Experience with usage-based billing models, metering pipelines, or consumption rating systems (Metronome, Lago, Amberflo, or similar).
Familiarity with Snowflake or similar data warehousing platforms used for contract aggregation and billing logic.
Experience building internal billing admin tooling for operational and support use cases.
Knowledge of financial reconciliation patterns, audit trail requirements, and building systems for regulated or revenue-critical environments.
Experience with prorated billing, invoice lifecycle management, or credit and refund processing workflows.
Familiarity with AWS Marketplace or other cloud marketplace billing integrations.
Understanding of CPQ (Configure Price Quote) systems and how contract data flows from CRM to provisioning.
Experience with Druid, ClickHouse, or other OLAP systems used for real-time usage analytics.
Knowledge of Infrastructure as Code tools such as Terraform or Pulumi.
Experience with observability and monitoring tools (Datadog, Prometheus, Grafana, or OpenTelemetry).
Familiarity with service mesh technologies (Istio, Linkerd) and mTLS.
Fullstack capable with experience building internal tooling UIs.
A passion for building systems where the correctness of data has direct commercial consequence.

#LI-MP1

About Kong:

Kong Inc., the AI Connectivity Company, is building the connectivity layer of AI. Trusted by the Fortune 500® and AI-native startups alike, Kong’s unified API and AI platform enables organizations to secure, manage, accelerate, govern, and monetize the flow of intelligence across APIs and AI traffic — on any model, any cloud. For more information, visit .

🎯 Who is this job for?

This role is suitable for a Senior Software Engineer with 5+ years of experience building production backend services, distributed systems, and TypeScript/Node.js microservices.

The candidate should be skilled in PostgreSQL, event-driven architectures with Kafka or similar tools, Kubernetes, CI/CD, multi-tenant SaaS, system design, and integrations with billing, payment, CRM, or usage-metering platforms.

They should be familiar with designing reliable billing and entitlement workflows, provisioning pipelines, financial data models, idempotency and consistency handling, internal admin tools, testing, incident response, and mentoring junior engineers.

💬 Potential Interview Questions

How would you design an idempotent billing workflow that processes subscription or contract events from Kafka?

Use a stable event or business key, persist processing status and deduplication records in PostgreSQL, and commit state changes transactionally where possible. A retry should safely return the existing result rather than create duplicate subscriptions, entitlements, or invoices.

How would you model subscription, contract, and entitlement data in PostgreSQL?

I would separate immutable contract and billing events from the current subscription and entitlement projections. Tables would include tenant and organization identifiers, effective dates, plan versions, lifecycle states, audit metadata, and unique constraints that prevent conflicting active records.

How would you handle eventual consistency between a CRM, payment provider, and Kong’s internal provisioning services?

I would treat each system as an independent source of truth for its domain and synchronize them through durable events and reconciliation jobs. State transitions would be explicit, observable, and retryable, with compensating actions or manual review for unrecoverable failures.

How would you design entitlement enforcement for a multi-tenant SaaS platform?

Entitlements should be resolved using the organization, plan, contract state, feature, limits, and effective timestamp, with tenant isolation enforced at every data and API boundary. Frequently accessed decisions can be cached, but cache invalidation must be driven by entitlement events and fail safely when data is unavailable.

How would you integrate a provider such as Stripe, Zuora, or Chargebee into a TypeScript service?

I would isolate the provider behind an adapter with typed domain interfaces, validate webhook signatures, persist incoming events before processing, and make all outbound operations idempotent. Provider-specific identifiers, status mappings, rate limits, retries, and reconciliation workflows should be handled explicitly.

How would you implement usage-based billing and ensure metering accuracy?

Usage events should have unique identifiers, timestamps, tenant context, and sufficient metadata for replay and audit. I would use durable ingestion, deduplication, late-event handling, clear aggregation windows, and reconciliation between raw usage, rated usage, and invoices.

What patterns would you use to make Kafka-based billing workflows reliable?

Use partition keys that preserve ordering for a customer or organization, consumer groups for scalability, and committed offsets only after durable processing. Dead-letter topics, retry backoff, schema compatibility, correlation IDs, and replayable consumers are essential for operational recovery.

How would you build a provisioning pipeline from a closed CRM opportunity to a live organization configuration?

The pipeline would validate the contract, map products and terms to internal plans, create or update the organization idempotently, and publish provisioning and entitlement events. Each stage should expose status and failure reasons so operations teams can retry safely or intervene manually.

How would you test a billing microservice built with TypeScript, Node.js, and NestJS?

I would combine unit tests for domain rules, integration tests against PostgreSQL and messaging infrastructure, contract tests for external providers, and end-to-end tests for complete lifecycle scenarios. Tests should cover retries, duplicate events, out-of-order delivery, partial failures, proration, refunds, and authorization boundaries.

How would you diagnose and operate a production incident involving incorrect entitlements or billing state?

I would trace the affected organization through correlated events, service logs, database history, provider records, and metrics to identify the first inconsistent transition. After containing the issue, I would use an idempotent repair or reconciliation process, preserve an audit trail, communicate impact clearly, and add monitoring or tests to prevent recurrence.

📋 Job Summary

Kong is an AI connectivity company building the platform that helps organizations secure, manage, and monetize API and AI traffic. As a Senior Software Engineer on the Konnect Admin/Billing team, you’ll design reliable TypeScript and Node.js microservices, event-driven Kafka workflows, payment and CRM integrations, entitlement systems, and internal billing tools using PostgreSQL, Kubernetes, and CI/CD. This is a fully remote, full-time role available in Toronto or Washington, offering CA$145K–CA$165K in Canada or $150K–$175K in the US, plus equity and bonus opportunities. Apply to shape revenue-critical distributed systems, collaborate with global teams, and make a direct impact on Kong’s commercial infrastructure.