System Design

💬 In plain words: The title "Salesforce Architect" means completely different things depending on who is interviewing you. Consulting firms (SIs) care about how well you present to clients and whiteboard architecture trade-offs. Product companies (ISVs) care about deep code quality and AppExchange package thinking. In-house enterprise teams care about your operational maturity—how you will fix their messy legacy org. You must prepare for the format, not just the technical topics. 📌 Example: Take the exact same technical topic, like Apex Triggers. A Product Company will hand you a block of code and ask you to find the bugs (e.g., SOQL in a loop, no bulkification). An SI consulting firm will ask you to draw a system architecture on a whiteboard to explain to a CIO why you chose Apex over Flow. An In-House team will ask you, "Our org has 50 conflicting triggers and deployment is broken. What is your 90-day plan to fix it?" Same knowledge base,...

💬 In plain words: Every word you add to an AI prompt acts as additional weight for the model to balance. Longer instructions increase the chances that the model gets distracted or ignores core directions. Salesforce explicitly confirms this principle: keeping reasoning instructions concise produces significantly more accurate results. 📌 Example: A Meridian subagent originally used eleven sentences of detailed prompt instructions and consistently misrouted requests. By shortening the instructions to four clear sentences and moving two strict constraints into code logic, the routing accuracy jumped without changing a single downstream action. Concept When an AI agent misbehaves, developer instinct is often to add more instructions. In practice, this usually makes performance worse. Every line in your system prompt increases the context size that the model must evaluate during reasoning. Overlapping or wordy instruct...

In plain words: Salesforce Well-Architected is the official set of architectural guidelines provided by Salesforce that defines what "good" architecture looks like across three foundational pillars: Trusted , Easy , and Adaptable . It helps architects and developers design secure, scalable, and maintainable systems. Building on Salesforce requires balancing speed with long-term stability. The official Salesforce Well-Architected framework provides architects, developers, and platform owners with prescriptive guidance and decision trees to build solutions that deliver immediate business value without accumulating technical debt. The 3 Core Pillars of Salesforce Well-Architected The official framework structures all architecture recommendations into three primary pillars, each supported by two sub-principles: 360 Framework Overview: 1. Trusted: Protects stakeholder confidence through uncompromising Security and Reliability . ...