Praxt Talent

Senior Integrations Engineer

Greater Cleveland, OH — hybrid, 2–3 days on-site

The short version

We are an established B2B software company. We grew by building and by integrating products we purchased, so we now run a suite of products rather than one — and a growing roster of outside vendors wants to plug into them.

Somebody has to build the front door. That is this job.

The distinction that matters

There are two kinds of integration work here, and we are only hiring for one of them.

The first is building a specific integration for a specific business need — wiring product A to product B for a particular workflow. We already have a team that does that.

The second is building the platform everyone else integrates (including Vendors) through. You design and publish the APIs. You decide how an outside company reaches our core systems securely, quickly, and without any hand holding them. Once a vendor is connected, they run on their own and nobody on your team touches it again.

That second one is the job. If you have built the thing partners integrate into, rather than integrations between things, keep reading.

What you would own

-      The public API surface: designing it, publishing it, versioning it, and holding it to real standards for security, performance and documentation

-      Partner enablement — the connectors, tooling and documentation that let an outside company integrate with very low effort and no help from us

-      Integration patterns across the platform: API-based integration, event-driven messaging, data synchronization, workflow orchestration

-      Building in C# and .NET on Azure, with an embedded iPaaS (we run Prismatic) for connector development

-      CI/CD, automated testing and deployment automation for integration work

-      Monitoring and observability, so integration health is something you can see rather than something you guess at

-      The hard failures — the ones that cross system boundaries and nobody else can reproduce

Honestly, what this role is not

-      It is not a pure architecture seat. The first three to six months are heavy on architecture while you set the direction, and you will have other architects to lean on. After that it settles into a hands-on senior engineering role owning what you built.

-      It is not a low-code configuration job. We are not using someone else's connectors to integrate our software. We are building the connectors.

-      It is not a maintenance role. The person who built this platform has moved on, which means it is open for someone to shape.

What we are looking for

-      7+ years building software, with a real share of that on APIs and integrations

-      Strong, current C# and .NET with REST API development — this stays hands-on

-      Hands-on Azure: API Management, Service Bus, Event Grid, Functions. We are a Microsoft shop and we mean it

-      Experience building connectors or an integration platform — Prismatic, MuleSoft, Workato, a homegrown connector framework, or comparable

-      A track record designing APIs that people outside your own company consumed

-      Working knowledge of event-driven and API-first design across distributed systems

-      CI/CD and DevOps practice applied to integration work

-      Someone who communicates well across product, engineering and support, and can turn architectural direction into something built

What makes you stand out

-      You have built or run an integration marketplace, or a developer portal partners self-serve from

-      EDI or other standardized data exchange with outside partners

-      Payments experience — ACH, card rails, reconciliation

-      AWS or GCP alongside Azure

-      You have absorbed an acquired company's product into an existing platform

-      You have put AI into an engineering workflow and governed it properly, not just used it

Why this one is worth a look

-      The direction is already funded and decided. Tooling already chosen, a clear mandate. You are not fighting for budget or relitigating strategy.

-      Real ownership. You are not inheriting somebody's platform and keeping it warm. You are deciding how partners connect to a product tens of thousands of professionals already run on.

-      Stability with momentum. A forty-year-old, profitable market leader that is investing seriously in engineering right now.

-      A hiring manager who is clear. The VP of Architecture has a one-page picture of this role: where it sits, what success looks like at six and twelve months, which decisions are yours, and what the job is and is not. You will see it early, so you can tell quickly whether it is for you.

What it is like here

Independently verified, not marketing copy: 4.0 out of 5 on Glassdoor, 78 percent of employees would recommend us to a friend, work-life balance rated 4.2. We have won a regional top-workplace award twenty times.

Because we are together in the office two to three days a week, the extras are real: an on-site gym with free personal training and fitness classes, in-office massages and manicures, house cleaning and laundry service, monthly car washes, catered lunches every Wednesday, a game room, and tickets to Cleveland sporting events. Benefits include full medical, dental and vision, a 401(k) with company match, and tuition reimbursement.

If you have built the platform outside vendors integrate through, we should talk.