Prasad Guuduru

Why What

To enable a future-ready, fine-grained authorization foundation beyond static RBAC and JWT-only models, supporting enterprise-scale access control and continuous compliance needs.

• Designed the Authorization (AuthZ) strategy for transitioning core platform services from legacy access control to policy-based and attribute-based models (PBAC/ABAC).
• Built and validated a proof of concept demonstrating migration from coarse-grained authorization to fine-grained, policy-driven enforcement aligned with SOC 2 and ISO 27001 expectations.
• Prototyped a session-token–based authorization model as an alternative to JWT-only enforcement, enabling dynamic policy evaluation, runtime access changes, and reduced token complexity.
• Collaborated with security, platform, and product stakeholders to define initial policy boundaries, enforcement points, and extensibility considerations for future enterprise adoption.

What Why How

Provided Trailblazer Identity for Salesforce websites, enabling a unified identity layer across customer-facing experiences.

To create a Trailblazer Identity Account and wire profile data across systems, converting prospects into customers and enabling personalized, authenticated user experiences across Salesforce properties.

What Why How

Unified content across Salesforce websites and exposed it as a reusable, centralized content service.

To provide internal websites with aggregated, consistent content that can be reused across the Salesforce ecosystem, enabling the Marketing organization to ingest content from multiple sources, normalize it under a unified schema, and ensure terminology consistency across all websites.

This allowed changes (e.g., product renames or messaging updates) to cascade immediately across all sites, eliminating duplication and content drift.

What: Exposing Taxonomy Content as a service

• Why: For achieving same naming conventions across all the different internal websites
• How: 1. Taxonomist author content via Taxonomy Management Tool. Based on product requirements we have onboarded an API for consuming that data, sending back cached content back to consumers.
• 2. Lead a team of engineers, interacted with product and taxonomists in collecting API requirements and communicated with Taxonomy Management Vendor for achieving the integration.

What: Onboarded developer pipelines, tooling and 2) contributed to personalization scripts.

• Why: For deploying code to wordpress and 2) for achieving personalization across website.
• How: 1. Partnered with Frontend team, Security and Wordpress team on achieving deployments from salesforce code repo to wordpress servers.
• 2. Was part of personalization team in contributing to Personalization beacon library for integrating evergage.

What: Provisioned Digital Applications infrastructure in rackspace and orchestrating deployment pipelines.

• Why: For managing marketing platform on third party cloud provider.
• How: 1. Contributed to Infra as Code (Chef) Scripts for spinning up multiple application servers and webservers onto stack.
• 2. Implemented pipeline for deploying artifacts.
• 3. Java Based Application for intercepting the leads and delegating requests to MRIS Application for further lead processing.

What: Created AEM Web Components and Migrated and regenerated 18k+ forms from one CMS to another CMS while achieving author-ability.

• Why: Out of Marketing Organization decision we want to migrate all the digital content to better CMS from a legacy CMS. However, there were 18k forms still were running on legacy CMS hosted on R&D Application servers, We had to migrate all those off R&D Servers and achieve author-ability.
• How: 1. Lead team of junior engineers and consultants, Partnered with Marketing organization and identified the flavors of forms that needs to be migrated .
• 2. Developed equivalent form fields web components in AEM
• 3. Came up with a script to generate those component.
• 4. Scraped all the website forms and repopulated those via ETAL application.

What: Onboarding functionality for Fast Sign-up with in salesforce website where customers right after submitting the form we want to spin a salesforce product org and land them onto product with out email verification.

• Why: Prior to this implementation, all the prospects who wants to try out a free trial org needs to go back to email and click on a product link async to try out salesforce product. For, faster conversion we want to onboard a Faster Signup Forms.
• How: 1. I single handedly, interacted with Marketing Product, R&D Product and R&D Architect, collected the requirements and onboarded a POC in 3 months.
• 2. Interacted with UX at that time, and R&D teams on expanded the module to all flavours of forms. (example, submitting developer form needs to spin up developer org.)

What: Implemented Translation Module with in CMS

• Why: At that, we have onboarded a new localization translation agency ( SDL ) and we had to export content and ingest translated content to CMS
• How: 1. Partnered with Lead Engineer, vendor, product and security team and gathered requirements.
• 2. Implemented a translation module with Open CMS for securely exporting and ingesting the data and providing a interface option for authors for sending translations.
• 3. Created a workflow engine for orchestrating the exports, approval, ingestions.

What: Contributing to frontend and backend system with in CMS

• Why: For allowing web experience managers to author content
• How: 1. We have extended Open Source CMS and created modules around it based on marketing organizations asks.
• 2. Implemented modules like Redirect management module, Replication module, Translation Module with in CMS.

• Bootstrapped Netflix similar product call'd TV Everywhere for Tivo Inc.
• Owning BackEnd Api's.
• Driving Offshore team for delivering multiple modules w.r.t TV Everywhere project.

• Contributing to Service Oriented Applications.
• Partnering with onsite teams in delivering quality code.

• Developing web based tools for marketing and sales teams.
• Contributing to Frontend/Backend and Database modules.