Salesforce Developer to Architect
Amit Chaudhary

Amit Chaudhary

Amit Chaudhary is Salesforce Application & System Architect and working on Salesforce Platform since 2010. He is Salesforce MVP since 2017 and have 17 Salesforce Certificates. He is a active blogger and founder of Apex Hours.

Salesforce Developer to Architect

In this post, we will look at the top considerations that are crucial to being a successful architect on the Salesforce platform. Even more, We will share approaches on what to focus on if you are a developer on the journey to becoming an architect. Being a good Architect means lifelong learning, practicing and goal setting.

We did the session with Emely Patra on Navigating your career from Developer to Architect. Please check recording here. In this post I am going to include some key point form same session and some others community sessions.

Difference between Salesforce Architect and Developer

Its very important to understand what Salesforce Developer do and what is Salesforce Architect?


  • Develop the product and focuses on solving a specific problem
  • One who write the code like Apex, VF, Aura and LWC
  • Designed the code structure like trigger framework.
  • Consider for governor limits when designing solutions.
  • Responsible for CI/CD


  • Plans, designs and reviews the construction of enterprise software, primarily cloud focused, and Salesforce related.
  • Hold the vision and foreses the system before it is build
  • Think about bigger picture, Think Strategically and Communicate Effectively.
  • Responsible for data modeling, System landscape, Integration Architecture, Security design, Large Data Volume, System performance and etc.

Architect Responsibilities

Based on name alone, it’s all about the technology, right? Not exactly, the role and success depends on so much more. Check our Meta Architect session. with Carl Brundage.

  • Create architecture implementation and design plans
  • Identify strengths, weaknesses and tradeoffs in design decisions
  • Communicate design overviews to executive/business and technical audiences
  • Guarantee application design supports the business requirements
  • Collaborate with others on approaches needed to support strategy
  • Ensure timely delivery of fully functional software for users

CTA Mindset

The knowledge you gain on each domain has to be applied in a business context , to solve for a business problem and achieve some business value. This is what a CTA mindset is about, bringing it all together and applying the right lenses to see the models. Here are simple ways to think like an Architect.

Think Strategically

  1. Think N numbers of steps in advance, think about how the situation could evolve, how levers could change
  2. Know the limitations and other workarounds
  3. Do the Risks assessment and mitigations honestly

Communicate Effectively

  1. A good architect not only knows the solution well but can explain it to different audiences as well. 
  2. You know knowledge is no good if your stakeholders do not understand how it helps them
  3. Be it developers or business leaders, communicating in context and in a language your audience understands is key to being a top class architect

See the big picture

  1. The Architect always has an eye on the BIG PICTURE. He forced on Plans, designs and reviews the construction of enterprise software, primarily cloud focused, and Salesforce related
  2. Keeping at an eye on the end results and keeping the program on it’s right course to achieve the right Business Results is key to success.

Check out full session here

Some Myths for Salesforce Architect

Lets talk about some myths we always have for Salesforce Architect.

  • To become a Salesforce Architect I first work as Salesforce Developer.
  • Salesforce Architect must be able to write Apex and LWC.
  • Salesforce Architect Know everything.
  • Certification are the golden Standard.

What Next ?

1) Create your own goal.

Self assessment is very important. You should know What do you enjoy doing? What’s your natural Strength and What do you want to continue doing and what do you want to drop in your future role? Being a good Architect means lifelong learning, practicing and goal setting.

2) Presentation Skills

Take every opportunity for practice and overcome your fears. Speak at user group and run workshop with a customer and learn 5 Skills Great Salesforce Consultants Have In Common.

3) Find a mentor

A mentor is really useful specially when preparing for the CTA board review. Someone who can give you honest feedback and help you structure your thoughts is a key success ingredient in your success.

4) Practice makes you perfect

Now that you know the 3 simple ingredients that make a good architect and you feel ready for your review boards how do you get there? Let me tell you something, it is not easy. Bringing together your breadth of domain knowledge into context specific architecture take practice. So all I can say is Practice, Practice Practice.

5) Feedback is a gift

Finally “feedback is a gift” accept it graciously . It’s a quality that can only help you be better every-time. Experience is the wonderful knowledge that enables you to recognize a mistake when you do it again.

6) Habit of thinking strategically

One of the awesome things about going through the whole grill of becoming a CTA is you naturally get into the habit of thinking strategically, thinking of the big picture, organizing your thought into business context etc.

7) What’s beyond CTA

The learning does not stop there, growth mindset is extremely important before and even after the review boards.

Further learning

  1. Sharing Architecture in Salesforce.
  2. Salesforce integration Patterns & Best Practices
  3. Building Scalable Solutions on Salesforce
  4. How Salesforce Query Optimizer works for LDV
  5. Pre-Sales Life Cycle in Salesforce

Please share some tips if you have for our audience.

Share this article


  • One thing I’d add to your list of differences between a Developer and Architect is the latter needs to think in terms of “Patterns”. There are many patterns we seek to leverage as architects. This applies to all aspects of a project. It applies to integrations, record sharing, ERD relationships, coding, frameworks, services (e.g. Enterprise SOA patterns applied to Salesforce) and many other things as well. Some, will often refer to these patterns as “best practices”, but there are “anti-patterns” architects learn to look for as well which are important to consider as applications and orgs scale.

    While it’s true that not all architects need to know how to write code, having the ability to understand code and interfaces is extremely helpful when it comes to these patterns. Without them, understanding the need for service oriented architecture, various layers of abstractions, and certain types of services will be much more difficult to understand and implement. I also feel it’s nearly essential for an architect to understand why certain frameworks are more desirable to implement than others; especially when the decision of which one to implement ultimately affects the outcome of their project.

    • Thanks Cal Smith. We totally agree with you. Really nice point you added.

  • Thanks for the rich info shared!
    Would you guys have a place/link/community where we could find mentors to have even a 30min monthly call?
    Tkx in advance for your support.

Leave a reply

Keep in Touch

Subscribe for Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 3,230 other subscribers


Our Supporter


Apex Hours

Apex Hours is one stop platform to learn Salesforce skills and technology

Join our Newsletter and get tips and tricks how to explore the salesforce for free!