Related Posts
VMware Opening support domain, DM for referral

Can anyone provide me a referral to Linkedin?
More Posts
Anyone down to play tennis in Frisco/Plano?
For anyone that is interested, the Celsius first bankruptcy hearing is going on now and will likely have repercussions and could set precedents across other similar cases. These are the key considerations, at least a few of which IMO are absolutely reprehensible.
It does sound at least like the judge and Kirkland (lawyers) are leaning towards ruling in favor of the folks with custody accounts.
https://cases.stretto.com/public/x191/11749/PLEADINGS/1174907182280000000001.pdf
Additional Posts in Salesforce Professionals
New to Fishbowl?
unlock all discussions on Fishbowl.


Technical Architect is a CTA or is pursuing that path. If you don’t know what that is then it’s not for you.
Solution Architect bridges the functional and technical roles and is the next step for a very experienced SFDC Senior BA/Admin.
Tech archs can code
You’ll be much deeper in code, devops, monitoring offshore teams, integration patterns, etc being a TA. SAs provide overarching solution design from a business perspective and usually need a TA to complete their designs
https://joinfishbowl.com/post_1ttuj
Solution Architect = Techno-functional solution expert
Technical Architect = Custom dev-oriented leader who can design an entire solution/suite, not just write code for an application
Enterprise Architect = Capable of "system of systems" design, build vs. buy, most technical in the area of integrations, data model, and security.
Salesforce's "Program Architect" internal advisory consulting role encompasses elements of all 3 (ratio depending on the engagement), but leans heavily on the last two ( more technical than an EA but more platform architecture-focused than a TA generally is), and is Salesforce-oriented (but not limited) rather than being truly platform-agnostic, and are engaged for the duration of a transformation effort but generally not beyond.
The CTA designation is poorly named IMO because it requires some dev but not like what a TA generally does; it doesn't even require you to pass PD II to be eligible. It really should be called "Certified Platform Architect" because that's what it is, someone who can build anything on Force.com (Applications Architect) + connect to any external tool, data source, or technology (Systems Architect) + distill those concepts for both highly technical and executive folks (tested by the boards). Will be interesting to see what the two new architect certs announced at Dreamforce entail.
As a solution architect, I design the end to end solution, map integrations, manage data migration approach/strategy, create a release strategy and build everything that can be built declaratively (including simple triggers but not complex ones). I do code reviews though and work closely with developers to ensure custom development accounts for exception and boundary cases and meets the outcomes expected by the client. I've not needed a TA in most of my projects, unless there's significant custom integrations and web development involved. For larger projects requiring a TA, we have often also needed an SA to be able to lead key conversations with stakeholders on design decisions. They are both unique complementary skillsets and should be staffed based on the scope of the project.
Technical architect: he/she manages solution design and build of Salesforce.
Solution Architect: Not specific to one system but manages overall solution that may span across multiple systems.
For example: if a project involves lead to order conversion. That span across Salesforce, CPQ, ERP systems including master data management systems and middle wares. Each tech architect worries about their own system (such as salesforce, sap etc) while solution architect worries about overall solution end to end.
The bigger the project the more difference you find between tech arch and solution arch