Solution Architect Q&A Tell me about a time when your proposed solution was not well received by your client, users, or team? With your answer, it would be important to demonstrate an ability to adapt, not taking negative feedback personal, and perhaps relying on the team around you to get to an acceptable solution. Provide an example of a solution you are really proud of. Let the creative juices flow with your answer - this is an opportunity to show off! How do you evaluate when to use an out-of-the-box solution vs. a custom solution? The answer to this question often depends on what value a buyer puts on marginal enhancements. If someone has a lot of spending cash and really cares about something specific, custom might be suitable. But in several use cases, you can get 95% of the way to the desired state without customization, so it might not pay off to do so especially given that Salesforce iterates on its own features, not custom features. What measures do you take to ensure your designs are scalable? This is pretty open-ended depending on what you have worked on in the past, but the idea is that you should describe the measures you have taken for your solutions to work with 1 user or 1000, or 1 record or 1 million. What measures do you take to ensure your designs are easily maintained? Similar to above, this will depend on specific work you have done, but will involve things like referencing Custom Settings or Metadata for business logic instead of requiring updates directly to Flows or Apex. The goal is to show that something an architect designed and built does not require an architect or developer to perform regular maintenance.