Ask HN: What does a solution architect do? | Hacker News Reader

Ask HN: What does a solution architect do?

4 pointsTbobbyZ5 comments

I think I’m one. I used to be a developer, but now I spend most time in meetings, creating tickets, and pushing tickets over the finish line. I’ve noticed I’ve had to drastically improve my writing skills. I function as a support agent + developer + consultant.

This role feels like I’m wearing too many hats. I don’t mind. The team is only 4 people. No one has the knowledge I have so I feel special on the team.

Any book recommendations for what I’ve described would be helpful! Thanks.

View on HN

There's no hard and fast rule, especially when you're working with a small team. When I think of a solution architect, they select the right technology/technologies for the job - usually in an enterprise setting where the tech landscape is vast. This is typically a role one moves into after being a developer - which is helpful because they were hands on with the technology (or at least other technologies) and have the ability to get into the technical details.

Typically, the person that spends time creating tickets, and making sure they are moving along, generally has a title like scrum master, tech lead, product owner, product manager or the like. Each of the aforementioned roles has different additional responsibilities and responsibilities can vary by company, for the same title.

The title consultant typically doesn't refer to a skillset or job function. It's mostly used to describe a person that doesn't work for the company, but can be hired (oftentimes short term) to do anything.

A solution architect spends a lot of time in meetings and handles communication with the business side. They gather requirements, sell solutions through presentations. They usually utilizing preexisting off the shelf products and configure them to fit a solution. They often hire external developers for work.

They don't deal with tickets, jira or standups.

I'm not sure you would fit the classic solution developer title. It sounds like you have become a product owner or system owner for a legacy product that has little development but needs to remain stable because many internal employees rely on the system.

Curious what your product is.. is it a crm?

Good guess! Yes. Salesforce.

You’re in a good place if you enjoy this kind of work. As far as book recommendations go, it probably depends on where you see yourself going. Would it be more technical work, sales, product, business, management, entrepreneurship, or something else? Like you said, in your role you get exposed to a lot. In my own experience it was a transition to product.

You can certainly continue in your existing role, of course. It doesn’t have to be a transition. But it’s a generalist type of job, and it feels like one discipline ultimately wins out in the end.

Would this role be good to transition to engineering management in the future? I find the role much less technical than I thought. It's a lot of coordination with stakeholders to ensure we are building something they want. Letting go of my technical mindset has been the greatest challenge for me since I worry I will not be hireable.

Reply on news.ycombinator.com