this depends on the type of organization you are in and what type of architect. At a small startup i was an engineer who coded a lot but also did what would be

this depends on the type of organization you are in and what type of architect. At a small startup i was an engineer who coded a lot but also did what would be considered architecture, devops, db administration, project management and client relationships. when i joined a fortune 100 as a solution architect, i mostly made power point and worked to translate unclear business objectives into architectures, work breakdowns, estimation and multi-year planning. it was expected i could code, understand db choices and trade offs but truly never had to do anything hands on technical.