Sales Engineer Playbook · SDR → Sales Engineer
"I'm not technical enough for this."
Sort of true, and far less true than it feels. The SE job is explaining technology, not building it — and the specific gap underneath the fear is almost always narrower than "technical enough."
Why this happens
You're comparing yourself to the engineers you work alongside, who spent years building the thing. But that's not the job you're moving into. The SE job is understanding it deeply enough to explain, demo, and defend it — a different, learnable skill from building it.
Why the obvious fix doesn't work
The obvious fix — "go learn to code" — solves the wrong problem. It's slow, it's not what the interview actually tests, and most SEs don't write code day to day. The real gap is usually product and domain depth, not programming ability.
What actually changes it
Deliberate, narrow depth: know your product's architecture, its limits, and how it compares honestly to the competition. That's a few weeks of focused reading and asking, not a computer science degree.
Today's 10-minute version
Pick one part of your product you've never fully understood. Ask an engineer or SE to explain it in 15 minutes, and write down the answer in your own words.
The skills underneath this