Salesforce developer Commerce Cloud Tech Lead
Job Description
Role: Salesforce developer
\n
Required Technical Skill Set: B2B Commerce Cloud Tech Lead, Commerce Cloud, Service Cloud, Apex, LWC, Copado/Gearset
\n
Experience Range: 12+
\n
Location: Seattle, WA (onsite)
\n
\n
Must-Have
\n
Desired Competencies (Technical/Behavioral Competency)
\n
• Salesforce Platform Expertise
\n
• Deep understanding of Salesforce B2B Commerce Cloud, Service Cloud and custom applications.
\n
• Must have solid understanding of Salesforce Experience Cloud, Lightening Web Components and Aura Components.
\n
• Must have good experience in APEX programming and Salesforce declarative tools like Flows, Process Builder and Validation Rules.
\n
• Must have solid understanding of Salesforce profiles, permissions sets/groups, sharing settings, org wide defaults etc.
\n
• Must be comfortable in using VS Code for development, Copado for DevOps, Data import/export tools.
\n
• Deep understanding of Salesforce security controls, standards and best practices.
\n
• Other Developer skills
\n
• Should be able to efficiently develop, debug and deploy software
\n
• Should be well versed in designing and implementing secure and reusable patterns and components. o Creating technical designs, helping with debugging & deployments.
\n
• Should be knowledgeable enough to help with estimation and troubleshooting
\n
• Should be a good communicator when it comes to cross functional engagements
\n
• Should be open to learning and adopting new technologies Focus
\n
\n
Good-to-Have
\n
• Documentation & Specification
\n
• Creating detailed technical design diagrams and documents.
\n
• Data & Integration Awareness
\n
• Understanding of Salesforce data model and relationships.
\n
• Should have experience and understanding of integration patterns (APIs, middleware, ETL tools) using REST, SOAP, SFTP protocols.
\n
• Flexible enough to fulfill needs of offshore and onshore working model.
\n
• Use of collaboration tools (Slack, Zoom, Teams) effectively.
\n
• Patience and clarity in communication to avoid misunderstandings.
\n
\n
Responsibility of / Expectations from the Role management, management capabilities, permissions, and account access.
\n
• Design, develop, and maintain secure APIs for partner integrations, card purchasing, order submission, and order status management.
\n
compliance and secure access.
\n
• management, and backend enterprise systems.
\n
•integration and functional validation.
\n
order management capabilities.
\n
• Ensure application quality through unit testing, code reviews, defect resolution, performance optimization, and production support.
\n
to deliver scalable, secure, and high-performing solutions.
