Jitendra Zaa Portfolio
Salesforce technical architect and CRM/Service CTO whose site anchors on a published book, "Apex Design Patterns" (2016), and a Udemy course, "Mastering Salesforce DX," rather than a project gallery.
Location
Not listed — probably too busy shipping to update the bio.
Skills
What makes it work
A breakdown of the choices that make this portfolio stand out.
A published book as the core credibility artifact
Leading with "Apex Design Patterns" rather than a screenshot gallery is a stronger depth signal for a language-specific role than any single project could be.
The same topic developed across three formats
Book, Udemy course, and blog all cover Apex/DX — repetition across formats signals sustained depth rather than one lucky post.
Senior title stated up front
Leading with "CTO" before the technical content calibrates the reader's expectations toward architecture-level thinking, not just code samples.
What Salesforce Developers can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
If you've written any long-form material (book, course, extended guide), lead with it — it demonstrates sustained expertise a single project can't.
Cover one topic across multiple formats (blog + book + course) rather than scattering across unrelated topics.
State your current title or seniority plainly if it's substantive — it calibrates a reader's expectations before they read further.
Case studies
A book, an open-source Apex library and a CTA mock-exam group. The thread through all three is teaching other Salesforce engineers to design, not just to code.
Apex Design Patterns
A Packt book, co-written with Anshul Verma, on applying object-oriented design patterns to Apex. It opens with OOP basics (inheritance, polymorphism, abstract classes) and then works through creational, structural, behavioral and concurrency patterns, plus anti-patterns, tied to real project problems.
Apex runs under hard governor limits, so pattern choice decides whether code scales. Writing the reference book on it shows architecture-level command of the language.
Covers creational, structural, behavioral and concurrency patterns in Apex
Separate treatment of Apex anti-patterns and governor-limit best practices
Written for three levels: new Apex developers, intermediate, and advanced
CTA Gang of Four (CTAGoF)
A group of four architects who prepared for the Salesforce Certified Technical Architect exam together. All four passed, and they now run mock review boards for CTA candidates. The site takes mock requests (candidates must already hold Application and System Architect) and keeps a list of publicly available CTA mock scenarios.
Judging mock CTA boards means critiquing whole-system designs under exam conditions, which is the same skill an architecture review board uses.
Free mock-board scheduling for architect-level candidates
Curated list of public CTA practice scenarios, with sources credited
Clear disclaimer that it is not affiliated with Salesforce
Projects
A small rule engine written in Apex. You register the operators you allow (&&, ||, ==, <, >= and so on), pass a map of binding values for merge fields such as Case.IsEscalated, and Rule.eval() returns true or false for an expression string.
Writing an expression tokeniser and evaluator inside Apex's CPU limits is real language-level engineering, and the documented trade-offs show sound judgment.
Rules evaluated from plain strings at runtime, with no redeploy needed
Operator registry built with factory and singleton patterns
README lists known limitations and performance costs up front
More Salesforce Developer portfolios
Ready to build your portfolio?
Follow the Salesforce Developer roadmap — skills, projects, and timeline to get hired.