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.
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.
More Salesforce Developer portfolios
Ready to build your portfolio?
Follow the Salesforce Developer roadmap — skills, projects, and timeline to get hired.