top of page
2.png

Senior Integration Engineer

Remote | Full Time

United States

Divinity Software Group, LLC

Closed- Check Back Later

Role Description:

Divinity Software is hiring a Senior Integration Engineer to own and build client integrations across the collections ecosystem.

 

This is a high-ownership role for a senior engineer who thrives in real-world integration work — distributed systems, inconsistent vendor APIs, legacy databases, and compliance-aware environments.

 

Our platform is multi-tenant and cloud-based, but every client integration ultimately connects through an on-premise gateway. Your primary responsibility will be building and maintaining our “Last-Hop Library” — client-specific integration components implemented as a set of C# interfaces and plugin-style libraries that dynamically bootstrap each client within our on-prem API. That on-prem API bridges our platform to the client ecosystem (systems of record, dialers, payment tools, etc.).

​

This is not a “ticket-taker” role. We’re looking for someone who can operate independently, communicate clearly, and own integration success end-to-end.

What You Will Do:

  • Own client integrations end-to-end: discovery → architecture → build → deployment → support

  • Implement and maintain client “Last-Hop” libraries in C#/.NET

  • interface-driven integrations

  • plugin-style components

  • tenant-specific bootstrapping inside our on-prem multi-tenant API

  • Build secure, resilient integration logic using:

    • REST APIs, webhooks, and messaging patterns

    • authentication flows (OAuth2, JWT, secrets management)

    • data mapping and transformation pipelines

    • Troubleshoot and resolve distributed integration issues across multiple services

  • Validate fixes through staged rollout:

    • dev → internal test → client test environment → production

  • Write and maintain integration documentation:

    • mapping specs

    • runbooks

    • troubleshooting guides

    • operational handoff notes

  • Improve the integration framework over time (reusable patterns, better reliability, better observability)

Requirements:

Must Have:

  • Strong C#/.NET Core experience is required

  • (This role is primarily backend C# integration engineering)

  • 5+ years backend engineering experience

  • Proven experience owning production integrations end-to-end

  • Collections industry experience required

  • You understand terminology and workflows (placements, portfolios, disputes, dialers, payment flows, compliance awareness)

  • Strong distributed debugging ability:

    • You can trace failures across services and message flows

    • You can reason about state transitions and execution paths without full client-side access

    • You can isolate issues using logs, telemetry, correlation IDs, and inference

  • Strong documentation habits and clear async communication (remote-first execution)

  • ​Comfortable debugging integrations that can’t always be reproduced locally (client-controlled environments, limited access, production-like issues)

​

Strongly Preferred:

  • Azure experience (Functions, Service Bus, App Services, Key Vault, Cosmos DB / SQL)

  • Experience with integration reliability patterns:

    • retries + backoff

    • idempotency

    • deduplication

    • durable workflows

  • Experience integrating with:

    • collections platforms / servicing tools

    • dialers/contact center systems

    • ACH/payment systems

    • bureaus/skip tracing/vendors

  • Familiarity with compliance-aligned engineering practices (PCI, SOC2, audit logs, access controls)

What Makes This Role Great:

  • High trust + high autonomy — you’ll be treated like an owner

  • Real-world engineering problems with real stakes

  • Remote-first culture built around strong async execution

  • Small team, high standards, meaningful impact

  • Your work directly affects client outcomes and platform reliability

This Role Is Not a Fit If:

  • ​You need full debugger access and perfect reproduction to solve issues

  • You prefer tightly scoped work with constant direction

  • You don’t want to be accountable for integration outcomes

  • You avoid client-facing technical conversations

Closed- Check Back Later
bottom of page