An architect is a specialized kind of designer, historically concerned with the design of buildings and related structures. The title has been co-opted by the software industry because of the innate similarities between buildings and software products.

• A software or technical architect is probably the oldest of these titles, and was possibly distinct at one time, but is now mostly a misnomer, often conferred upon the programmer with the most battle scars.
• A data architect handles digital data structures, designing everything from network protocols to interchange formats (e.g. for files). They are specialized further as database architects, who design the schemata of relational databases.
• An information architect is distinct from a data architect, despite the similar terminology. Rather, the former is often narrowly regarded as the technological progression of a librarian. The role is similar in spirit, but deals with the curation of information but intended for human consumption, at various degrees of scope and organizational facets.
• There exist other domain-specific titles, such as security architect or scalability architect, usually visible in larger or more specialized projects.
• A solution or product architect is the designer in charge of the overall conceptual integrity of a software product. Just like a true architect or the director of a film, this role reconciles business goals with technical acumen by reinforcing the mutual goal of a superlative experience on the part of the product's end users.