Software Architect Mentorship
|
What do Salesforce Program Architects do?Harpal works for Salesforce in an Advisory services role. Salesforce Program Architects are some of the industry’s most experienced Salesforce technology specialists. They can plan a client's Salesforce solution roll-out, oversee complex deployments, improve end-user adoption, and a lot more. Their goal is to see clients get maximum busıness value from Salesforce.
|
The VisionWe lead with business value, focusing on pragmatism, and delivering via minimum viable products. Learn the philosophy, the approach, and methodology that Salesforce uses for Enterprise Architecture.
|
Need mentoring help?Suggested Reading
Define your goal, moon-shot dream role?
|
Key Dimensions of our work |
Which dimension would you like to work on?
Which ones is your strongest? Relevant Job Descriptions |
Orals Coaching: Up your soft skills, EQ

Moments of reflection
- What are our obligations to our clients, product teams
- How can we over-communicate, manage the patterns?
- Plan executive summaries emails, communicate at a macro level
- Collect and provide data and facts: carry more weight that ‘gut’ feelings
- Dress for success
- Think through ice-breaker topics to smooth out communication with executives
- Don’t be afraid to ask for help, or say ‘I don’t know, but I will find out …’
- Be prescriptive when sharing your point of view
- Be ready to move past theory into practical application
- Be a Public speaking God:
- Give a short talk on a subject every few days 1:1, or in a group setting
- Record yourself present, watch it multiple times
- Lean in on the Salesforce architecture community
- Define your goto team, stick with them, meet them often
- Be available to help them in their projects and likewise expect help from them.
- Pay it forward :-): Become a mentor to a newer team mate, think like one
Salesforce Integration patterns

When you implement Salesforce, you frequently need to integrate it with other applications. Although each integration scenario is unique, there are common requirements and issues that developers must resolve.
This document describes strategies (in the form of patterns) for these common integration scenarios. Each pattern describes the design and approach for a particular scenario rather than a specific implementation. In this document you’ll find:
This document describes strategies (in the form of patterns) for these common integration scenarios. Each pattern describes the design and approach for a particular scenario rather than a specific implementation. In this document you’ll find:
- A number of patterns that address key “archetype” integration scenarios
- A selection matrix to help you determine which pattern best fits your scenario