conderr99

What if you didn’t need to understand them and just took their explanation as enough - simply accept that people will come to different conclusions than you, and that that is okay?

I have 12 years of experience working as a backend engineer full time for medium-to-large sized software companies, and breaking into consulting has always seemed really difficult to me.

I mostly excel at system architecture and writing technical documents to describe the trade offs of those systems. I really don’t enjoy full stack/web programming or marketing - is it possible to consult in strictly this capacity? e.g. as a principal or higher level engineer?