Would you become a software architect? Why and why not?

I wouldn't or at least not in a full-time capacity. Because I need a bigger dose of implementing stuff than of defining stuff + don't want to carry the blame for a major infra fuckup

Yes. But only after I get to understand most of the innards of what I’m architecting.
It looks like mad fun.

Same as @webketje

No, it's too high level and seems like it can become repetitive. The architects I worked with joined projects during the initial phase, helped set it up, moved on to another project. Granted - if I got into it I'm sure I'd think it was fun and probably feel like the other work is too low level

I'm with @Nanos on this one. Can you define the role? It's vastly different between companies.
At my previous company I would. Current company I would not.
Also cars don't get smaller...

As a system architect I can confirm that you get to do much less actual coding. You still have the problem solving part, but at least for me its way more meetings with everyone else in the organization that have an opinion or want something from the developers and I see my role as sort of a gate keeper to save the rest of the developers from unnecessary meetings :)

But you do get to do more overall design of the solution at an earlier stage and depending on team you can often get to code on proof of concept or even first implementation of a feature if you need to test out different options.

I don't think I would, there's too little coding and too much PowerPoint

If you feel like your opinion and skills can benefit others then yes, it's great to have a word in the bigger picture and ensure there is progress and technical advancements.

If you don't like the responsibility, then avoid it.

Either way: make sure you bloody keep coding. An architect that doesn't actively write code reaches used by date pretty quickly.

@devdiddydog true, you need to keep up with what happens code wise or your not going to make good decisions.

@Voxera just curious: do you ever have any technical project managers or dev lead roles on the same team with you as an architect?

I'm trying to think what the distinction is between those 3 roles, as all of them seem to: have tons of meetings, do lots of planning before projects, and protect devs.

@jiraTicket I have some other architects that work more project based with solutions that span multiple systems with their own dev teams and system architects.

And of cause I talk with the architects on the systems we integrate with, but not really any tech lead on the teams (there are 3 teams I work with)

And since this is my first larger company I have no real experience with tech lead as such from before since I have mostly been the most experienced ;) I sat with a computer before many if them where born :P

@Nanos we have a solution there with bikes. The chain and GPS tracing (here in the Netherlands the electric bikes come with that)

So soon we will see lots of loops in the sidewalk like we already have for boat parking.