After two decades in tech (Microsoft, startups, data platforms, the works), I realized I was spending more time explaining my job than actually doing it.
Especially as a Solutions Architect / Sales Engineer — one of the most misunderstood roles in the game.
So I started a weekly newsletter called Architect This.
It’s part therapy, part insight, part "why does no one know what this job actually is?"
I write about:
- What SAs and SEs really do (hint: it's not just demos and diagrams)
- How we bridge chaos, customers, and roadmaps
- The daily emotional rollercoaster of pre-sales, onboarding, and fixing things we didn’t break
If you've ever:
- Fixed a broken dashboard while explaining it to a customer
- Been told "just do a quick demo" with no prep
- Acted as the translator between sales promises and engineering reality
…then yeah. This one's for you.
Would love feedback, stories, war flashbacks, etc.
1 comment
[ 3.1 ms ] story [ 10.3 ms ] threadAfter two decades in tech (Microsoft, startups, data platforms, the works), I realized I was spending more time explaining my job than actually doing it.
Especially as a Solutions Architect / Sales Engineer — one of the most misunderstood roles in the game.
So I started a weekly newsletter called Architect This. It’s part therapy, part insight, part "why does no one know what this job actually is?"
I write about: - What SAs and SEs really do (hint: it's not just demos and diagrams) - How we bridge chaos, customers, and roadmaps - The daily emotional rollercoaster of pre-sales, onboarding, and fixing things we didn’t break
If you've ever: - Fixed a broken dashboard while explaining it to a customer - Been told "just do a quick demo" with no prep - Acted as the translator between sales promises and engineering reality
…then yeah. This one's for you.
Would love feedback, stories, war flashbacks, etc.