
Salesforce Technical Architect
- Toronto, ON
- Permanent
- Temps-plein
- 8-10 years of Strong knowledge of custom Salesforce development including Apex, Aura, Process Builder, Flow, and LWC, Visualforce, basic administration, reporting & general design concepts
- Should have worked in 2 - 3 full lifecycle Salesforce implementation project as Technical architect
- Mandatory to have Salesforce Service cloud expertise, Sales cloud &SFDC experience cloud experience
- Expert in Aura framework and Lighting framework, particularly for developing custom lightning components on our SFDC Community pages
- Expertise in DevOps best practices, CI/CD and deployment for an IT organization of enterprise scale, either with Salesforce specific tools like Copado or Git, Bamboo etc.
- Experience building webservices using SOAP, REST, XML, JSON
- API integration skills working with middleware platforms such as Mulesoft
- Develop and maintain custom solutions on force.com platform using Apex and Visual force
- Develop and support new apps using lightning framework for internal and external users
- Support on-going production Global SFDC instances for business continuity
- Maintain proper documentation for work flow processes, list of values, migration plans, and standard operating procedures in accordance with business requirements.
- Assess the impact of proposed changes and recommend alternative solution choices, determining trade-offs and impact analysis
- Support the Customer's integration program. Work with integration leads on processes moving data between Salesforce and other third-party solutions such as marketing automation or ERP.
- Communicate effectively with IT leaders and/or business users on the status of project
SAP as service providerWe use the following session cookies, which are all required to enable the website to function:
- "route" is used for session stickiness
- "careerSiteCompanyId" is used to send the request to the correct data center
- "JSESSIONID" is placed on the visitor's device during the session so the server can identify the visitor
- "Load balancer cookie" (actual cookie name may vary) prevents a visitor from bouncing from one instance to another