Required Skills: Salesforce, Enterprise architect, Salesforce Certified Application Architecture, System Architect, Data modeling, Apex, LWC, Flow, REST SOAP, Mulesoft, Boomi, Data Loader, Informatica, Jitterbit
Job Description
Own end-to-end Salesforce architecture (Sales Cloud, Service Cloud + related clouds) while leading M&A-driven org consolidation — harmonizing multiple orgs, data models, and business processes across merging entities.
Core scope
Architecture standards, design patterns, and governance; lead technical design reviews for scalability, security, performance
Data models, integration architecture (APIs, middleware, ETL), sharing/security model
Platform roadmap, technical debt, release evaluation; mentor devs and admins
M&A / consolidation scope
Assess Salesforce orgs across merging entities — objects, data models, customizations, integrations, license usage
Design and execute consolidation strategy (org merge, org-to-org migration, or hybrid multi-org)
Data migration and de-duplication across account/customer/opportunity data; resolve process, taxonomy, and business logic conflicts
Work with M&A/PMO on timelines, cutover, and rollback plans; manage data integrity, compliance, and business continuity risk
Document as-is/to-be architecture and drive stakeholder alignment across both organizations
Must-haves:
10+ years Salesforce, including 4+ years Enterprise architect-level
Salesforce Certified Application Architect and/or System Architect
Led at least one large-scale org merger, consolidation, or migration
Data modeling, Apex, LWC, Flow, integrations (REST/SOAP, MuleSoft/Boomi)
Salesforce security/sharing model and multi-org architecture
ETL/data migration tools (Data Loader, Informatica, Jitterbit, etc.)
Strong stakeholder management across two organizations' leadership and technical teams
Based in US ET or CT
Preferred:
Consulting/professional services background; change management during M&A system transitions; industry-relevant Salesforce implementations
Soft skills:
Comfortable with M&A ambiguity, explains technical trade-offs to non-technical executives, diplomatic across competing teams