I wanted to write my personal experience on this topic since last few years. This is the journey most of the technical architect has to go through. I would like to mention that not all technical architects need to go through Developer to Technical Architect journey.
I personally know lot of Salesforce technical architect who does not know how to write an APEX class and in other words they never worked as developer. Some of them are recognized as distinguished Salesforce Technical Architect. You may have heard that you need to spend long years as developer to become Salesforce Technical Architect, but I do not agree with this. I am sure you would also find one or more excellent Technical Architect who cannot write or debug a complex APEX Code.
I started my career as developer and after spending several years as developer I transitioned to an architect. This article is for people like me who are from development background and would like to transition to a Salesforce Technical Architect.
Journey to Salesforce Technical Architect
If you are a Salesforce Developer and would like to transition to Salesforce Technical Architect, then you need to start the preparations. Similar to any other career path, you have to go through different phases of transition.
I would explain this journey in three phases that you would have heard several times in different context CRAWL (Acquire) => WALK (Apply) => RUN (Master)
CRAWL (Acquire)
This is the phase where we need to acquire the necessary skills and knowledge to work as a Salesforce Technical Architect. I would recommend going through the Salesforce Technical Architect Trailhead and try to acquire all the certifications needed to become System Architect & Application Architect
Keep your target to go through and understand the content and not just passing certification exams using online questions and dumps. Certification may help you find a role for you but without proper knowledge you may fail.
Here also I would like to mention that I have seen several successful technical architects who are not certified. Preparation for certification is going to set-up foundation and you would learn all different concepts that you would be applying when you get opportunity to work as Salesforce Technical Architect. Certification may help other to know that you have gone through the concepts, and you have the foundation but that is not mandatory.
WALK (Apply)
Once you get your foundation done, you can start applying your learning in your day-to-day work. You do not need to be assigned as a Technical Architect role to apply your learning. Some of the initiatives you can take are listed below: –
- Talk to your project manager and technical architect and show your interest and share all the learnings and certifications you have ac
- Start peer review of other team members development activities and start looking from architect perspective like modular design, performance, scalability, security etc…
- Learn from the design of your technical architect. Also explore existing design to see how the other architects designed. Not all designs are great but you can evaluate the design with your learnings
- Actively explore opportunities to work as Technical Architect in small size or support kind of engagements. When you start your journey, you need runway to take-off. You can also work as supporting architect on complex projects where you already have a seasoned technical architect.
- Do not hesitate to seek help wherever needed. Discuss your design with other architects (friends, mentor) to ensure you are on right path
- Some companies assign a mentor during this journey so see if you can get a mentor
Well, if you are not getting any opportunities or help for transition then discuss with your coach and start exploring opportunities outside of organization. This should be last step as taking-off your journey on new runway may not be as pleasant as you expect.
RUN (Master)
This is the phase where you need to ensure you keep on updating your skills with new technologies. Start looking beyond Salesforce. You do not need to master everything, but awareness of different technologies is very important.
Additionally, having knowledge of product, technology and tool related to specific industries would be very beneficial. Last few years Salesforce is focusing on different industries like Healthcare, Education, Manufacturing etc.. and understanding Salesforce product capabilities for these industries would help you move to next level (Journey from Technical Architect to Enterprise Architect)
Transition Challenge
I would list down few challenges that most of the developers face during this journey.
- Start thinking as architect and stop writing APEX in your mind when you are conducting technical workshops. I have seen this very frequently with new architects and they start thinking like developer when they discuss the requirements. You need to have design discussions and not development discussions. Discuss the feasibility, performance, scalability, reusability, security etc..
- You may be excellent developer but now you are transitioning to architect so try to stop writing code and focus on providing solution, review solutions etc..
- You do not need good communication skills as developer, but you need to communicate well (both verbally and in writing). You will be interacting with business and IT team, conducting technical workshops so good communication would be important
- You need to master skills of creating documentations that includes flow diagrams, network diagrams, process diagram etc..
Summary
Journey from Developer to Architect may not be short and it may take years. A technical architect plays critical role in success or failure of a project. Salesforce provides all necessary guidance to become a successful Technical Architect. You have to make sure you do not lose focus and keep learning.