This is my first post of a series describing my personal journey to obtaining my Salesforce Certified Technical Advisor (CTA) qualification. It is intended to pay forward all the help I received from the architect community on my Journey to CTA. In it I share many details that I wished at the time someone else would have posted.
This series is written particularly for people in companies that do not have a CTA program or significant mentoring from another CTA. This is “what I would have liked someone else to have written about ahead of me” with a bunch of practical details. I don’t know that what I’ve put together is the best answer, but it’s what I figured out along the way.
Since this is the start of a series, and perhaps the start of your studying, here’s my checklist for a smooth start on your test taking day.
In the next post, I’ll cover my test taking experience in San Francisco.
I had more to share about my entire #JourneyToCTA than I realized. It is a long and demanding process. It is my hope that the information I share in this series helps you in focusing your studies and confidently passing Salesforce’s Certified Technical Advisor Certification. It is a long and rewarding journey.
Part 1 – Welcome to Robert Wing’s #JourneyToCTA
Part 2 – Test Day
Part 3 – Test Taking Action Plan
Part 4 – Scenarios I Passed On for #JourneyToCTA Exam
Part 5 – Highlighting for Success
Part 6 – Salesforce CTA Solution Presentation
Part 7 – Discovering my Greatest Weakness
Part 8 – Certified Technical Advisor Exam Q&A
Part 9 – Preparation Strategies
Part 10 – Was it Worth It?
About Robert Wing, CTO, aMind Solutions
I’m a manager and architect focused on early-phase software product and project delivery. I focus on building the right things, building them correctly, and delivering them reliably.
As a partner in a ~100-person consulting and software business I do a bit of everything – marketing, negotiation & selling, estimation, planning, contracting, solution design, technical design, project management & governance, etc. – with a focus on being “the product guy” and “the details guy” amongst the partners.