Depends who you ask, as there are different types of &quot;Architects&quot;, under &quot;Solution Architect&quot;, &quot;Business Architect&quot;, &quot;Technical Architect&quot;,...<p>For me, I only care about the technical part of it, meaning:<p>- Translating requirements into technical specifications<p>- Designing the application modules and their relationships<p>- Selecting the languages, libraries and frameworks allowed in the project<p>- Full stack technical documentation<p>- Designing and implementation of the continuous deployment infrastructure<p>- Having an overall picture how all modules come together<p>- Taking part in the development team as senior coder<p>Those were just a few examples. Of course, the roles one takes are very dependent on team size and type of customer.<p>However not all architects are made alike. Meaning while I consider critical that one has a foot in both worlds, architecture and coding, in many enterprise companies that isn&#x27;t the case.<p>Moreover usually descriptions like &quot;Solution Architect&quot; and &quot;Business Architect&quot; tend to be alias to roles like &quot;Product Owner&quot; or &quot;Project Manager&quot;.