Eps 30: Technical ≠ Effective with Alice Egan
Alice Egan, a French linguistics major turned sales engineer, discusses her journey from non-technical background to pre-sales success at Zendesk. She emphasizes that technical fluency doesn't require coding ability, but rather understanding technology through storytelling and business context.
Summary
Alice Egan shares her unconventional path into sales engineering, starting as a French and linguistics major who moved to San Francisco and landed an associate SC role at Zendesk despite having no technical background. She describes spending her first months secretly googling technical terms like APIs between customer calls. Through structured self-learning and creating internal documentation, she built technical fluency and eventually started her own company, SaaS Savvy, to help other non-technical SCs develop similar skills.
The conversation explores the challenge of impostor syndrome in pre-sales and how Alice overcame it by embracing her differences rather than hiding them. She advocates for learning technology through historical context and storytelling rather than coding, arguing that most SCs need to understand how to talk about technology rather than build it. Alice emphasizes that technical doesn't have to mean traditional computer science backgrounds, and suggests the industry needs new categories like 'tech sales technical' professionals.
The discussion covers practical strategies for non-technical SCs, including how to research technology concepts, when to admit knowledge gaps, and how to position oneself beyond the limiting 'technical resource' title. Alice recommends learning the 20% of concepts that provide 80% of understanding, using resources like Wired magazine and technology history books rather than developer documentation. The episode concludes with a challenge for SCs to develop better self-introductions that focus on being product and ecosystem experts rather than just technical resources.
About this episode
Episode 30: You Don’t Need to Be the Most Technical Person in the Room In this episode, we’re joined by Alice Egan to challenge one of the biggest myths in sales engineering. The best Sales Engineers aren’t always the most technical people on the call. They’re the ones who can turn complex technical concepts into simple, compelling stories that buyers actually understand. In SaaS, this matters more than ever. Just like buying a car, most buyers don’t need to see the engine. They want to know how it works, how it fits their business, and why it solves their problem. In this episode, we discuss: Why being too technical can slow deals down How to translate complexity into clear, buyer-friendly stories When technical depth helps and when it hurts A practical way to position yourself at the very beginning of a sales call How top Sales Engineers read the room and adjust in real time If you’re a Sales Engineer, Solutions Engineer, or work in presales and feel pressure to always be the most technical voice, this episode will change how you think about your role. Tune in for real-world insights and practical nuggets you can use immediately.
Key Insights
- Alice argues that the pivot from on-premises solutions to SaaS enabled hiring charismatic storytellers for SC roles, but companies still need to teach them fundamental technology concepts
- Alice claims she overcame impostor syndrome by creating structured documentation of technical terms and concepts, which became the foundation for internal courses that boosted her visibility
- Alice contends that SCs should learn to talk about code and understand how it works rather than learning to code themselves, as their job is not coding
- Alice explains that APIs don't move or do anything - they're like castle walls with doors that protect software data and functionality while providing authenticated access
- Alice recommends using ChatGPT by asking what life was like before a technology, what it is, and what value it provides, rather than just looking up definitions
- Alice argues the term 'technical' in sales engineering is meaningless and varies dramatically between different types of software companies, from business apps to developer tools
- Alice defines her ideal SC as a 'tech sales technical' professional who talks about technology from business and cultural perspectives rather than diving into technical implementation details
- Alice describes her role as a software product and ecosystem expert who helps businesses understand how solutions integrate with enterprise backends and other software systems
Topics
Transcript
[0:01] Hello everybody and welcome to episode 30, episode 30 of Diary of a Sales Engineer. I'm Ryan Krueger and today I'm joined with Samir Saher and we got an exciting guest for you. I want you all to meet Alice Egan. She did not come up through engineering, computer science or anything remotely technical. She was a French and linguistics major who fell into pre-sales at Zenesk and spent the first few months secretly googling what's an API between customer calls. Out of pure survival, she taught herself [0:32] how to talk tech, learning the language of cloud, software, and APIs and quickly rose to support two of Zenesk's most technically demanding territories, the Bay Area in San Francisco…
Full transcript available for MurmurCast members
Sign Up to AccessMore from Diary of a Sales Engineer
RIP Traditional Presales
Ryan Krueger and Samir Saher discuss how the sales engineering role is fundamentally transforming due to AI, consumption-based pricing models, and market consolidation, requiring SEs to evolve from pre-sales-only positions into "account engineers" or "forward deploy solution engineers" who manage customers across the entire lifecycle while developing technical skills like coding and maintaining deep domain expertise.
How Sales Engineers Handle Difficult Prospects Without Losing the Deal
Ryan Krueger and Samir Sahai Gosser discuss strategies for handling 'prickly' prospects and internal colleagues in sales engineering. They categorize difficult people into distinct buckets and offer tactical advice for disarming skeptics, managing difficult calls, and building cross-functional relationships. The episode also covers best practices for following up on unknown questions and documenting commitments around unbuilt product features.
From Sales Engineer to CEO | Jeff Wang, CEO of Windsurf
Jeff Wang discusses his transition from sales engineer to CEO of Windsurf, emphasizing how SE skills like versatility and problem-solving translate well to leadership roles. He advocates for SEs to actively identify and solve organizational problems beyond their technical duties to gain broader influence.
If Your SE Never Says No, You Don't Have a Partner
Sales engineers discuss the importance of saying 'no' to account executives as strategic partners rather than order-takers. They emphasize that pushback protects deals, prevents wasted time on bad opportunities, and requires building trust through partnership rather than just being a technical resource.
Eps 32: GTMshift with James Kaikis
James Kaikis, co-founder of Pre-Sales Collective, discusses his entrepreneurial journey after leaving PSC, including his current ventures GTM Shift, AI Revenue Studio, and Solution Exec. He shares insights on the evolution of sales engineering roles and predicts significant changes in go-to-market motions driven by AI.