Salesforce Technical Architect

Job Description

Technical Architect — Salesforce Financial Services Cloud, Multi-Cloud & Enterprise Architecture

\n

Location: [REMOTE]

\n

Workplace type: [Hybrid]

\n

Employment type: Full-time Seniority: Senior Management level

\n

Job function: Information Technology · Engineering · Consulting

\n

Industries: IT Services and IT Consulting · Financial Services

\n

Travel: [30–40%]

\n

Openings: Multiple — immediate start

The Role\n

You own the blueprint. Not one cloud — the whole estate. You'll design multi-cloud Salesforce solutions for financial institutions where FSC is the core, but Sales, Service, Experience, Marketing, Revenue, Data Cloud, and Agentforce all have to coexist coherently; where the integration landscape includes legacy core systems; and where the data architecture has to satisfy a regulator, not just a product owner.

\n

This is the most senior technical seat on a program. You are accountable for whether the thing we designed actually works at scale, stays secure, and can be maintained after we leave.

What You'll Do\n

Solution & multi-cloud architecture

\n

\n
• Own end-to-end architecture for complex, multi-cloud Salesforce programs anchored on Financial Services Cloud.
\n
• Design the cross-cloud solution blueprint — FSC + Sales Cloud + Service Cloud + Experience Cloud + Marketing Cloud / Marketing Cloud Growth + Revenue Cloud + Data Cloud + Agentforce/Einstein — with clean boundaries, shared data models, and a defensible system of record for every entity.
\n
• Produce architecture artifacts that hold up under review: solution architecture documents, logical and physical data models, integration architecture, sequence and context diagrams, ADRs (architecture decision records), and NFR specifications.
\n
• Own build-vs-buy-vs-configure and single-org-vs-multi-org decisions, with the trade-offs written down.
\n
• Define org strategy, environment/sandbox strategy, release architecture, and the governance model that keeps it from drifting.
\n

\n

Data architecture

\n

\n
• Design the enterprise data architecture: canonical models, master data management, golden record and survivorship rules, deduplication and matching strategy, and party/customer 360 design across FSC's Individual and Household constructs.
\n
• Architect for large data volumes — indexing, selective query design, skinny tables, archival and purge, and sharing recalculation at scale.
\n
• Define data governance, lineage, retention, residency, classification, and data quality frameworks.
\n
• Architect Data Cloud implementations: ingestion, identity resolution, calculated insights, data model mapping, and activation back into FSC.
\n
• Own data migration architecture for high-volume, high-sensitivity financial data — including reconciliation and audit trail.
\n

\n

Integration architecture

\n

\n
• Design the integration landscape end to end: API-led and event-driven patterns, canonical services, orchestration vs. choreography, synchronous vs. asynchronous decisions, idempotency, error handling, replay, and observability.
\n
• Architect across MuleSoft, Boomi, Informatica, Kafka, API gateways, Platform Events, Change Data Capture, Salesforce Connect/External Objects, Streaming and Bulk APIs.
\n
• Integrate Salesforce with core banking, insurance, lending/mortgage, custodial, portfolio and order management, market data, KYC/AML, document management, e-signature, payments, and data warehouse/lakehouse platforms.
\n
• Define hyperscaler-adjacent architecture where relevant — AWS/Azure/GCP services supporting the Salesforce estate.
\n

\n

Enterprise architecture & governance

\n

\n
• Partner with client enterprise architects and CIO/CTO organizations to align Salesforce architecture to the enterprise reference architecture and technology roadmap.
\n
• Build multi-year platform roadmaps, capability models, and target-state architectures with a credible migration path.
\n
• Lead architecture review boards; navigate security architecture review, InfoSec, risk, and compliance sign-off.
\n
• Design for regulatory reality — GLBA, SOX, FINRA/SEC, SOC 2, PCI DSS, GDPR/CCPA — including Shield Platform Encryption, Field Audit Trail, Event Monitoring, BYOK, and compliant data sharing.
\n
• Own non-functional architecture: performance, scalability, availability, DR/BCP, and observability.
\n

\n

Practice & commercial leadership

\n

\n
• Serve as the senior technical authority in pre-sales — solution design, technical POVs, estimation, RFP/RFI response, and executive demos.
\n
• Serve on the Cloud Peritus Center of Excellence; review architecture and design across programs, not just your own.
\n
• Mentor Technical Leads and Senior Developers; build the architecture bench.
\n
• Drive thought leadership — accelerators, reference architectures, IP, whitepapers, and conference/community presence.
\n

What You Bring (Required)\n

\n
• Minimum 15+ years of technology experience, including 12+ years on the Salesforce platform and 5+ years in a dedicated architecture role .
\n
• Deep Financial Services Cloud expertise — you have architected FSC solutions for real financial institutions and can defend the data model choices you made.
\n
• Proven multi-cloud Salesforce solution design across at least three clouds in a single enterprise program.
\n
• Deep enterprise integration architecture experience — patterns, middleware, event-driven design, and legacy/core system integration at enterprise scale.
\n
• Strong data architecture credentials — enterprise data modeling, MDM, data governance, large data volume design, and migration architecture.
\n
• Enterprise architecture experience — reference architectures, roadmaps, architecture governance, and TOGAF-style rigor (formal certification optional).
\n
• Hands-on credibility: you can still read Apex and LWC, review a design in detail, and prototype when it matters.
\n
• Consulting/SI background with direct exposure to C-level and enterprise architecture stakeholders.
\n
• Exceptional communication — you can hold a whiteboard with a CTO and a sprint room with engineers on the same day.
\n

Nice to Have\n

\n
• Salesforce Certified Technical Architect (CTA) — or actively on the CTA path (Application Architect + System Architect / "Architect" domain certifications).
\n
• Domain certifications: Integration Architect , Data Architect , Identity & Access Management Architect , Development Lifecycle & Deployment Architect , Sharing & Visibility Architect , B2C Solution Architect , Financial Services Cloud Accredited Professional .
\n
• MuleSoft Certified Integration Architect; AWS/Azure/GCP architect certifications; TOGAF.
\n
• Salesforce Industries / OmniStudio architecture depth.
\n
• Data Cloud, Agentforce, and AI/ML architecture experience in regulated financial services.
\n
• Experience with nCino, ICE Mortgage/Encompass, FIS, Fiserv, Jack Henry, Temenos, BlackRock Aladdin, Charles River, or comparable FS platforms.
\n

First 90 Days — What Good Looks Like\n

\n
• Day 30: You've assessed the current architecture of your program (or client estate) and delivered a written risk and opportunity POV.
\n
• Day 60: A target-state architecture and integration blueprint exist, are socialized, and are signed off by the client's architecture review board.
\n
• Day 90: Delivery teams are building against your blueprint without needing you in every conversation, and you're contributing to the CoE and to at least one active pursuit.
\n

\n