Thinking about switching my career to Solutions Architect as I'm interested in talking with users.
Although, I'm still relatively new in my career (~2 YOE) and worried whether it's too early to make a move.
Any tips/thoughts on switching careers from SWE to Technical Solutions? Will it be harder to switch back to SWE in the future?
Can you clarify what your definition of "Solutions Architect" is? I did some Googling, and it seems like a blend between product manager, TPM (technical project manager), and SWE (with not too much of this one). However, I feel like this term will vary across different companies, and some companies will call it a different title (e.g. At Meta, this role reminds me of "Solutions Engineer").
...as I'm interested in talking with users.
You can still do this as a SWE in many ways:
In general, yes, I'd say that it is harder to go from Technical Solutions back to SWE. The bias you'll face is that someone in Technical Solutions is (ironically) not as technical as a Software Engineer.
This has ramifications in terms of both influence in an org and compensation.
At Meta, roles like Data Engineer and Solutions Engineer (e.g. people who helped advertisers integrate with the ads API) were given ~30-40% less equity compared to software engineers.
If you feel the company has a desperate need for Solutions Architect, and you feel like promotions are now possible, then it may be worth it. This makes sense at very senior levels, e.g. I imagine being a senior software engineer, switching over to Solutions Architect would be an interesting way to get to Staff.