Role Overview

Fortiv is a cloud-native B2B SaaS platform for Business Continuity Management (BCM). We help enterprise customers map their critical processes, manage risk, run exercises, and coordinate incident response. The platform's value depends heavily on the quality and freshness of customer data — org structures, IT asset inventories, business process dependencies, recovery plans.

This role exists at that boundary. The Integrations Engineer owns the technical layer through which customer data enters and stays current in Fortiv: bulk file ingestion, connector integrations with customer HR/ITSM/CMDB systems, and the full onboarding engineering workflow for new enterprise customers. The role is roughly 30% ongoing backend product work and 70% integration and data onboarding.

This is a senior individual contributor role. You will be the primary engineer responsible for customer data integrations end-to-end, working directly with customers' technical teams and operating in a compliance-governed environment (ISO 27001:2022, GDPR).

What You Will Work On

Customer Data Onboarding

Each new enterprise customer requires structured onboarding of their existing data into Fortiv. You will own the technical side of this:

File-based bulk import Customers deliver CSV/XLSX exports from their HR, ITSM, and CMDB systems to Fortiv. You will configure per-customer field mapping, transformation rules, and scheduling. Onboarding typically spans 4–8 weeks elapsed per data source, with 3–5 days of Fortiv engineering effort each.

Data quality validation : Joint review with the customer before go-live — completeness checks, edge case handling, test load iterations, and sign-off. You will often be the one leading the technical side of these conversations.

Custom ingestion configuration : Our ingestion pipeline supports a wide range of entity types (users, teams, resources, risk metadata, etc.) with configurable column mappings, field transformations, and relationship resolution. You will extend this configuration model as new customer requirements emerge.

Connector Development

A core part of why this role exists is to build and extend native integrations with the enterprise systems our customers already use — moving beyond file-based import toward live, maintained data pipelines. This is greenfield work with high product impact. You will:

Build and extend integrations with HRIS, CMDB, and ITSM platforms: Design and implement connectors to systems such as Workday, BambooHR, ServiceNow, Jira Service Management, and Device42. This means understanding their APIs, auth models, data models, and rate limiting behaviour, and mapping their concepts cleanly onto Fortiv's domain.

Own the connector framework : As connectors are built, you will also refine the patterns — how connectors are configured, scheduled, and monitored — that future connectors will follow.

Outbound pull and event-driven sync : Connectors may operate on a polling schedule or respond to webhooks from source systems. Both patterns will be in scope.

Webhook receivers : Extending our existing webhook infrastructure to handle inbound events from new source systems.

Technical Requirements

Must Have

Python — We use async Python (asyncio, async/await patterns). Comfortable with type annotations and Pydantic v2 for data modelling and validation. Our codebase runs Python 3.13.

async web frameworks — You will add API endpoints and background job handlers in our FastAPI service. Familiarity with dependency injection patterns, middleware, and OpenAPI schema design.

ORM experience — You need to be able to write async queries, understand relationship loading strategies, and work with migrations.

PostgreSQL — Solid working knowledge: query optimisation, multi-tenancy patterns, async notification mechanisms, concurrent job processing. Our production DB is Aurora PostgreSQL 16.

REST API integration — Experience integrating with third-party REST APIs, handling auth flows (OAuth2, API keys, bearer tokens), pagination, rate limiting, and error recovery.

File-based ETL — Experience building or maintaining CSV/XLSX ingestion pipelines: schema mapping, data validation, transformation logic, entity resolution across types.

Strong Advantage

Enterprise SaaS integrations — Experience integrating with HR systems (Workday, BambooHR, ADP), ITSM (ServiceNow, Jira Service Management), or CMDB tools (ServiceNow CMDB, Device42).

Compliance-governed environments — Prior work in an ISO 27001 or SOC 2 environment: audit log requirements, data classification, secrets management policies, pen test remediation workflows.

Nice to Have

Infrastructure-as-code (Terraform) — We use Terraform for all infrastructure. You won't own infra but being able to read and propose small changes is useful.

Docker — All services run in containers. Ability to build and debug Docker images for local development.

Redis — Our services use Redis for rate limiting and caching. Basic familiarity is enough.

Structured logging / observability — Ability to write well-structured log entries and work with distributed tracing context.

Non-Technical Requirements

Compliance Mindset

You will routinely make decisions that touch GDPR and ISO 27001 requirements: what data to request from customers, how to store credentials, when to add a new sub-processor, how long to retain import artefacts. You don't need to be a compliance expert, but you need to understand why these controls exist and be able to apply them without hand-holding on every decision.

Autonomy and Ownership

Onboarding workstreams run largely independently. You will often be managing multiple customers at different stages in parallel. The role requires strong project awareness — tracking what's agreed, what's in progress, and what's blocking — and proactive communication.

What We Are Not Looking For

• A generalist backend engineer who will mostly build product features. The ratio here is deliberately tilted toward integration and onboarding work.

• Someone who needs a fully defined scope. Customer integrations involve ambiguity: source systems have undocumented quirks, customers change their export formats mid-onboarding, and requirements surface during validation rounds. Comfort with this is essential.

• A consultant or solutions architect role. You will write and own the code.