Senior Integration Engineer

SourceFuse is engineering the client-facing platform layer for a major Australian financial services and insurance brokerage client. The platform consists of multiple client portals that today integrate with a legacy CRM (SugarCRM v7 via SOAP) and will progressively transition to a Salesforce-native CRM (Practifi).

You will own the design and build of a CRM integration service (anti-corruption layer) in Node.js/TypeScript: a stable internal API that the portals consume, with swappable adapters behind it — a legacy SugarCRM adapter in the short term, and a production-grade Salesforce adapter as

the client migrates. The portals must never need to change when the CRM does. That is the engineering bar for this role. This is a hands-on senior IC role with significant architectural ownership, working directly with client technical stakeholders in Australia and SourceFuse solution architects.

Experience Required: 6-9 Years

Preferred Location - Noida/Mohali

Key Responsibilities:

● Design and implement the CRM integration/adapter service in Node.js + TypeScript, exposing a versioned, contract-tested internal API to multiple Symfony-based portal applications.

● Build the Salesforce adapter: REST API, Composite/Composite Graph requests, Bulk API 2.0 for high-volume sync, and event-driven patterns using Platform Events and Change Data Capture.

● Implement and operate Salesforce authentication correctly: OAuth 2.0 (JWT bearer flow for server-to-server, refresh-token flows where appropriate), Connected App configuration, least-privilege integration users.

● Engineer explicitly for Salesforce governor limits and API allocations: request batching, caching strategy, backoff/retry with idempotency, queue-based decoupling (SQS or similar).

● Wrap and stabilise the existing SugarCRM v7 integration (legacy SOAP / v4_1; evaluate migration to Sugar REST v10) behind the same internal API as a transitional adapter.

● Map and reconcile data models across SugarCRM, Practifi (Salesforce-native), and portal-side PostgreSQL — including identity resolution and sync conflict handling.

● Define and enforce the integration contract: OpenAPI specs, consumer-driven contract tests, schema versioning, deprecation policy.

● Deploy and run the service on AWS: containerised (ECS/EKS), API Gateway, SQS/EventBridge, Secrets Manager, CloudWatch; CI/CD via GitHub Actions or similar.

● Build observability in from day one: structured logging, tracing across portal → adapter → CRM calls, sync-lag and error-rate dashboards, alerting.

● Handle sensitive data responsibly: the platform touches health-insurance-related client data subject to the Australian Privacy Act / APPs; data residency (ap-southeast-2), encryption in transit/at rest, and PII minimisation are requirements, not nice-to-haves.

● Work directly with the client's IT Applications team and the incumbent vendor during knowledge transfer; document everything you reverse-engineer.

Must-Have Qualifications:

● Expert-level, recent, hands-on experience integrating with Salesforce from external systems (not primarily Apex/LWC development on Salesforce): REST, Bulk API 2.0, Composite APIs, Platform Events / CDC, and the OAuth 2.0 flows that secure them.

● Demonstrated understanding of Salesforce governor limits, API request allocations, and the architectural patterns used to live within them at scale.

● Strong production Node.js + TypeScript skills: a typed, tested, modular service codebase is your default, not an aspiration.

● Familiarity with NestJS, Fastify, or Express + a DI pattern.

● Solid SQL skills with PostgreSQL and/or MySQL; comfort designing sync/staging schemas.

● Experience designing integration or middleware layers between systems you didn't build — including wrapping legacy SOAP/XML APIs.

● AWS production experience: containers (Docker; ECS or EKS), queues (SQS), API Gateway, IAM, Secrets Manager.

● Testing discipline: unit, integration against Salesforce sandboxes/scratch orgs, and contract testing (e.g., Pact) for API consumers.

● Clear written English and the ability to communicate directly with client-side architects and managers; comfortable presenting technical decisions and trade-offs.

● Ability to maintain meaningful working-hours overlap with AEST (roughly IST morning through early afternoon).

Strongly Preferred:

● Exposure to Practifi or other Salesforce-platform ISV products (Financial Services Cloud, nCino, Vlocity/Industries) — i.e., you understand that an ISV's managed-package data model is not vanilla Salesforce.

● Prior CRM migration experience (any legacy CRM → Salesforce), especially running old and new CRMs in parallel behind an abstraction.

● SugarCRM API experience (SOAP v4_1 or REST v10).

● Salesforce certifications: Integration Architect, Platform Developer I/II (valued as signal, not as a substitute for the hands-on bar above).

● Experience in insurance, health insurance, broking, or wealth/financial-advice domains; awareness of Australian privacy and financial-services compliance context.

● Event-driven architecture experience (EventBridge, Kafka) and familiarity with iPaaS tools (MuleSoft, Boomi) sufficient to articulate why we are building this layer instead of buying one.

● PHP/Symfony reading fluency — enough to trace how the portals consume CRM data today.