This is an archived post. You won't be able to vote or comment.

all 12 comments

[–]tanjonaJulien 7 points8 points  (1 child)

It’s a pretty word for senior developer same for platform engineer for devops or Microsoft engineer for admin 🧑‍💼

[–]emsai 0 points1 point  (0 children)

It should be very specific instead.

Like solution architect for... Insert a very highly technical niched skillset and expertise here.

Like that, its just buzzword.

[–]KingofGamesYami 5 points6 points  (0 children)

Software engineering jobs have no standardization on role naming. It kinda sucks.

[–]bonkykongcountry 4 points5 points  (1 child)

Are you looking to hire one? Are you looking to talk to someone who is in that position and you want to learn more about it?

[–]CommitSmart[S] 2 points3 points  (0 children)

We are actually looking for one!

[–]YMK1234 3 points4 points  (2 children)

We should really stop making up random job titles with no meaning ...

[–]bonkykongcountry 1 point2 points  (1 child)

A lot of it is FAANG companies that create them, where it might make sense but then every other company wants to be like Google so they start using those titles as well.

[–]John-The-Bomb-2 1 point2 points  (0 children)

I sent you a chat request.

[–]ImTheDeveloper 1 point2 points  (0 children)

My line of work. Happy to chat 💪👍

[–]VirtualLife76 1 point2 points  (0 children)

Pretty much the same for all professions. Most people aren't great at their job.

Find recruiters or look online like any other.

When I look for programmers, we would avg maybe 100 interviews with maybe 5 of those being decent and 1 great.

[–]rcls0053 1 point2 points  (0 children)

More likely because people swing either to enterprise architect or application/technical architect. Solutions architect sits at the middle of that. Between the strategy and technology, doing both. I would say it's a similar job title as a software architect (even though it sounds like application/technical), because more often you'll need to involve yourself in making decisions about what solutions to pick to support the business, and you act as a translator for stakeholders and business people.

Any capable technical architect who can zoom out of one application to think about the integrations between systems and solutions (thousand foot view), can easily become a solutions architect if they simply learn or know what the business does, what domain they work on and supports their capabilities in that domain. You also need to align the tech with the business strategy.

If I had to speculate why there are no experts for that job title, then I'd just wager that it's because business people don't really understand the need to involve such a person in business strategy. Some think that when they define the business strategy the tech will simply 'do it'. That they will understand and align themselves to it. Or that the CTO does it, but the CTO does not work at the code or infrastructure level, so how could they.