Salesforce Tech Lead/ Architect

Job Title: Salesforce Tech Lead/ Architect

Location: Remote

Looking for someone who has experience in migration & implementation from Oracle to Revenue cloud. Need immediate joiners.

Job Summary:

Minimum Qualifications

• 10+ years of IT experience, including 8+ years as an Architect across Salesforce Cloud, Azure Cloud and other Integration platforms
• Led multiple project implementations for each of:
• Strong hands-on experience in Revenue Cloud (CPQ + Billing) complex pricing, subscriptions, usage billing
• Strong hands-on experience with Salesforce (Service Cloud, Experience Cloud, Data Cloud, Apex, Flows, LWC) and enterprise CRM implementations
• Dell Boomi/ MuleSoft / API Architect with deep expertise in API-led connectivity, RAML design,
• Experience with Dell Boomi / MuleSoft architecture (processes, API-led, clustering, Molecule deployment)
• Experience with Microsoft Azure and other clouds with hands-on in services like Azure Logic Apps, Azure Service Bus, Azure SQL, plus exposure to AWS / PCF / OpenShift / CloudHub runtime environments
• Strong background in DevOps & CI/CD (Jenkins, Git, Maven), security (OAuth2.0, TLS, JWT, API gateways), logging & monitoring (Splunk/Grafana/DataDog/CloudWatch) etc.
• Ability to own end-to-end architecture, estimation, and technical governance for complex, multi-system integration landscapes
• Experience leading cross-functional teams, collaborating with client architects, and presenting solutions to senior stakeholders
• Excellent communication skills

Responsibilities

• Working closely with Delivery team, mentoring and helping them implement Salesforce Revenue Cloud features
• Lead solution blueprinting, governance, and architecture reviews, defect triage and solutioning
• Define target architecture (microservices/event-driven), reference patterns, and guardrails across Azure, Power Platform, and Salesforce.
• Design & deliver integrations: Salesforce enterprise systems using Boomi (primary), Azure Integration Services (APIM, Functions, Service Bus, Event Grid).
• Stand up secure Azure foundations: landing zones, network topology, identity (Entra ID/Managed Identity), Key Vault, private endpoints.
• Power Platform governance: environment strategy, DLP, Dataverse schema, ALM (managed solutions, pipelines), COE adoption.
• API strategy: contract-first, versioning, throttling, observability; publish via APIM.
• Non-functionals by design: security, cost, reliability, performance, scalability.
• Lead 4 10 engineers; review designs, unblock delivery, and communicate with stakeholders.