Integration Engineer

You build and maintain the integrations behind Kibo Connect Hub — the connections between the KIBO platform and the third-party applications our clients run alongside it: ERP, WMS, PIM, tax, payments, shipping, CRM, marketing, and more.

The distinction that matters in this role is reuse. You are not building an integration for one client. You are building one integration that many clients turn on and configure differently, and it has to hold up across all of them — different field mappings, different volumes, different edge cases, all on the same codebase. Adding the next client should be configuration, not a fork.

Some of what you build connects KIBO directly to a vendor's API. Some of it connects KIBO to universal API providers that already maintain large libraries of pre-built connectors, letting one integration reach many downstream applications. You will work in both models and help judge which one fits a given partner.

Product Management owns the partner strategy — which vendors we integrate with and what each integration covers. You are the engineering team that makes it real, and the technical voice that tells Product early when a vendor's API cannot support the scope as written.

KIBO is a composable digital commerce platform for B2C, D2C, and B2B organizations who want to simplify the complexity in their businesses and deliver modern customer experiences. KIBO is the only modular, modern commerce platform that supports experiences spanning B2B and B2C Commerce, Order Management, and Subscriptions. Companies like Ace Hardware, Zwilling, Jelly Belly, Nivel, and Honey Birdette trust KIBO to bring simplicity and sophistication to commerce operations and deliver experiences that drive value.

KIBO's cutting-edge solution is MACH Alliance Certified and has been recognized by Forrester, Gartner, IDC, Internet Retailer, and TrustRadius. KIBO has been named a leader in The Forrester Wave™: Order Management Systems, Q1 2025 and in the IDC MarketScape report "Worldwide Enterprise Headless Digital Commerce Applications 2024 Vendor Assessment."

By joining KIBO, you will be part of a team of Kibonauts all over the world in a remote-friendly environment. Whether your job is to build, sell, or support KIBO's commerce solutions, we tackle challenges together with the approach of trust, growth mindset, and customer obsession.

Build new integrations in Kibo Connect Hub against scope defined by Product Management, in Node.js and TypeScript

Design each integration for multi-tenant reuse — configurable field mappings, per-client credentials and settings, and sensible defaults — so onboarding the next client does not mean writing new code

Maintain the existing library of pre-built integrations, including the following: vendor API deprecations, breaking changes, credential and auth-flow changes, and schema drift that arrives without notice

Own the universal API provider layer — the third-party iPaaS and unified-API services we build through — including how we abstract them, where we depend on them, and what happens when they change or degrade

Work directly with partner vendors' technical teams on API behavior, sandbox access, certification requirements, and the defects you find in their APIs

Build integrations that survive real-world failure: retries with backoff, idempotent writes, dead-letter handling, replay after an outage, and rate-limit behavior that does not take down the downstream system or ours

Version integrations and manage backward compatibility so a change made for one client does not break the clients already live on it

Instrument what you build — logging, metrics, and alerting good enough to tell a partner outage from a client misconfiguration from our own bug, before a client tells us

Carry on-call for integration failures, triage them, and work them to resolution alongside our incident response process

Write and maintain the integration documentation clients and systems integrators actually implement against: what the integration does and does not cover, configuration steps, field mappings, prerequisites, error semantics, and limits

Feed technical reality back to Product Management — feasibility, effort, API constraints, and where a vendor's API forces a change in scope

Review peers' integration code with an eye on reuse, failure handling, and whether the next client can be onboarded without a developer

8+ years as a developer building integrations between software applications

Demonstrated experience building reusable, multi-tenant integrations used by many customers — not only one-off integrations scoped to a single client. Be ready to talk about how you handled configuration, versioning, and per-client variation on shared code

Strong Node.js and TypeScript

Deep, practical command of REST and JSON APIs: authentication patterns (OAuth 2.0, API keys, JWT, mTLS), pagination, rate limiting, webhooks, and idempotency

Experience with asynchronous, event-driven integration patterns — queues, pub/sub, retries, and eventual consistency between systems that disagree

A real instinct for data mapping and transformation between systems whose models do not line up, including the reconciliation problems that follow

Track record debugging production integration failures across a boundary you do not control, using logs and traces

Experience integrating with at least one enterprise system category — ERP, WMS, OMS, PIM, tax, payments, shipping, or CRM

Cloud experience (AWS, GCP, or Azure) and comfort with containerized deployment (Kubernetes/Docker), CI/CD, and automated testing

Clear technical writing — your documentation will be read by client developers and SI partners

Hands-on experience with a universal API or iPaaS provider (for example Merge, Nango, Paragon, Workato, Boomi, MuleSoft, or similar), including where the abstraction helps and where it gets in the way

Commerce, retail, or supply-chain domain knowledge — orders, inventory, fulfillment, returns, catalog, or pricing

Experience with legacy integration formats still common in retail: SFTP-based file exchange, flat files, SOAP, or EDI

GraphQL or streaming (Kafka, Kinesis, Pub/Sub) experience

Built or maintained a partner or app marketplace, or a public connector library

Use of enterprise-approved AI/GenAI tooling to accelerate integration scaffolding, test generation, or API documentation analysis, with judgment about data sensitivity and validating output