Skip to main content

Integration Architect in Fort Lauderdale

Posted yesterday

energy jobline zrFort Lauderdale (FL)

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Job Description& - ( ) AOPartners has been retained by a confidential client to find a senior, hands-on Integration Architect to accelerate its Salesforce-to-Microsoft Fabric customer master platform. It is not a "Fabric developer" or "Data Engineer" role. We want an integration architect who has already solved this exact class of problem: real-time Salesforce eventing into Fabric, with customer master sync across multiple downstream applications. You'll lead the architecture and write the code. Review and validate the end-to-end Salesforce → Fabric → downstream architecture Assess code quality, technical debt, scalability risks, and supportability Establish event contract standards and schema governance Stand up deployment and release management processes Eliminate single points of failure and harden resiliency Accelerate downstream consumer integrations across multiple enterprise applications Implement automated and regression testing for customer master events & Deep hands-on Fabric experience: Eventstreams, Notebooks, Lakehouse, Warehouse, Real-Time Analytics Enterprise-scale Pub/Sub and event-driven architecture design and delivery Azure Container Apps, Event Hubs, and Service Bus integrated with Fabric Event routing, replay, dead-letter patterns, and idempotent processing Performance tuning for Fabric workloads and event pipelines Observability, logging, monitoring, and production support readiness Expert in Platform Events, Pub/Sub API, and gRPC integrations Real-time integration experience, not batch ETL OAuth, event subscriptions, replay IDs, and resiliency patterns Bidirectional Salesforce-to-enterprise integration design True software engineering background, not low-code only Java, Python, Spark, and modern API development Automated testing frameworks for event-driven systems Code review discipline, design patterns, coding standards, and CI/CD Track record refactoring prototypes into production-quality solutions Customer master / MDM synchronization across multiple applications CDC, event sourcing, data contracts, and schema management Canonical customer models and downstream distribution patterns Data quality frameworks and validation rules Customer onboarding, update, and account sync workflows
Type: Contract / 1099
Duration: 1 to 3 months Start: ASAP #MicrosoftFabric #Salesforce #EventDrivenArchitecture #Azure #IntegrationArchitecture #Hiring

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this