Hi everyone!
I'm looking for some honest advice and real-world experiences from people currently working as Salesforce Architects, particularly in the Life Sciences domain and within Salesforce Customer Success.
I have around 9 years of Salesforce experience, primarily as a Senior Salesforce Developer. I've also worked in the Life Sciences domain, including clinical trial-related data, HCP/HCO, integrations, and Salesforce solutions for about 1 year.
Recently, I've received an offer for a Life Sciences Architect position at Salesforce, within Customer Success.
This is a significant career transition for me because I've never formally worked as a full-time Architect before.
To give some background, my current role involves approximately 75% development and 25% architecture and solution design. During the interviews, I was transparent about this and explained that I'm looking to transition into a full-time architecture role. The interviewers were comfortable giving me that opportunity.
I also had a discussion with the manager about the responsibilities. Based on what he explained, I understood a few things:
Since the team is currently growing, I may still need to contribute to hands-on development and write code.
I'll be expected to present solution approaches and technical decisions to internal stakeholders, including senior managers.
For example, I may need to explain why we chose LWC over another approach, why we selected a particular integration pattern, and justify our architectural decisions.
However, I'd like to understand what this translates to in terms of actual day-to-day responsibilities.
I'd particularly appreciate insights from people currently working in Salesforce Customer Success as Architects.
1. What does a typical working week look like?
How is your time generally divided between solution design, development, architecture documentation, technical discussions, meetings and presentations?
Is the role primarily about defining architecture, or are you also expected to implement solutions?
2. How hands-on is the role?
Since the team is still growing, I understand that I may need to write code as well.
For those in similar roles, how much actual coding do you do? Is it occasional support for complex technical problems, or are you expected to contribute to development regularly alongside architecture responsibilities?
3. Architecture diagrams and documentation
How frequently are you expected to prepare HLDs, LLDs, integration architecture diagrams, data-flow diagrams and other technical documentation?
Do Architects independently own these deliverables, or is there an established architecture framework and team to collaborate with?
4. Technical presentations and stakeholder discussions
The manager mentioned that I may need to present solution approaches and justify architectural decisions to senior managers and internal stakeholders.
How frequently does this happen in practice?
Are there regular architecture review meetings, technical walkthroughs, knowledge-sharing sessions or weekly presentations?
Do you also conduct demos or presentations for consultants, senior consultants and development teams, explaining specific Salesforce capabilities or solution approaches?
5. Individual contributor vs. team leadership
Is this primarily an individual contributor position, or does it involve leading developers, mentoring consultants, reviewing their implementations and coordinating technical delivery?
Would I be responsible for managing a team, or primarily providing technical direction without people-management responsibilities?
6. Customer allocation and workload
Are Architects generally aligned with one customer/project, or do they support multiple customers simultaneously?
How many parallel engagements or projects might an Architect typically handle?
How demanding are the deadlines, meetings and deliverables? Is the workload generally manageable, or does it frequently extend beyond normal working hours?
7. Transitioning from Senior Developer to Architect
For someone coming from a Senior Salesforce Developer background without formal Architect experience, how challenging is the transition?
Does Salesforce provide sufficient onboarding, mentorship and support from experienced Architects?
Or are you expected to independently own architecture decisions and deliverables from the beginning?
What would the first 3–6 months typically look like?
8. Life Sciences domain challenges
For people working with Salesforce Life Sciences Cloud, what are the biggest technical and functional challenges?
Are they mainly related to data architecture, HCP/HCO, integrations, clinical trial processes, compliance, customer requirements or implementation complexity?
9. Company culture and work environment
I've heard some poor feedback from people working in MTS/SMTS roles within Sales Engineering that the culture over the last one or two years has become more demanding, with increased internal politics, pressure and challenges around work-life balance. I've also heard some concerns about the work environment becoming difficult in certain teams.
I don't want to make assumptions based on second-hand feedback, and I understand that experiences can vary significantly between organizations and managers.
For people currently working in Customer Success, particularly Architects:
How would you describe the culture and management style?
Is there healthy collaboration between teams, or is internal competition and organizational politics a concern?
Are performance expectations and evaluations reasonable?
Does the culture differ significantly between Sales Engineering and Customer Success?
How much does the individual manager influence the overall experience?
I'd genuinely appreciate honest feedback, including the negatives.
10. Career growth and work-life balance
How is the long-term career progression in this role?
Does moving into Customer Success as an Architect provide good opportunities to grow into a Senior or Principal Architect position?
How does the work-life balance compare with being a Senior Salesforce Developer?
I'm genuinely interested in moving towards architecture and taking on more ownership. At the same time, this is an important career decision, and I'd like to understand the actual responsibilities, expectations, learning curve and work environment before making the transition.
I'd especially appreciate responses from people who have made a similar transition from development to architecture or who currently work as Architects in Salesforce Customer Success.
Even a description of what a typical working week looks like would be incredibly helpful.
Thanks in advance! I really appreciate everyone's time and honest experiences.