The use of the word “solution” in business is ubiquitous. A generic definition of a “solution” is that it is an answer to a problem. When applied to a business context, the definition is more precise; however, many companies’ “solutions” really only the fit the generic definition. In a later post, I will provide a more satisfying definition of the word “solution” as it it applies to customer-facing engineering.
A Solutions Architect’s responsibilities are similar to that of a Solutions Engineer, but the Solutions Architect position is usually considered more senior. A Solutions Architect will often focus more on the pre-sales side than the post-sales side. For example, a Solutions Architect may be more involved in giving proof-of-concept demos and doing a requirements analysis (to determine the feasibility of delivering what the customer wants). A Solutions Architect may need to be well-versed in reading programming code, but may never write code.