Do (SaaS) Solutions Engineers Really Need to Code? A Practical Take

When it comes to Solutions Engineering, the role can vary significantly depending on the type of product you're selling. Some SEs work with highly technical products like databases, cybersecurity solutions, or developer platforms, where coding and deep technical knowledge are essential. Others work with more user-facing SaaS products like HR software, CRM systems, or collaboration tools.

This article focuses on the non-technical SEs, those who sell SaaS products where customer-facing skills, business acumen, and product knowledge take center stage. So, the big question is: Should non-technical SEs learn to code?

Coding in Non-Technical SE Roles: A "Nice to Have"

In non-technical SaaS roles, your customers are usually business users: HR managers, sales leaders, or operations professionals. These stakeholders care about outcomes, not the underlying technology. Your role is to translate product features into value for their business, a task rooted in empathy, storytelling, and problem-solving.

In such cases, coding is rarely a dealbreaker. What matters more is how well you can align the product with the customer's challenges, articulate its benefits, and deliver tailored solutions. That said, coding can be a bonus that helps you stand out in the crowd.

Where Coding Can Help

When strategically applied, coding can give you an edge in non-technical SE roles. For instance:

• Customization: Customers often request tailored solutions or integrations. Knowing how to tweak scripts or set up workflows shows agility and builds trust.
• Efficiency: Automating demo setups or repetitive tasks can save hours, letting you focus on high-impact activities like deep-dive discovery sessions or competitive positioning.
• Cross-Team Communication: Understanding code helps you collaborate more effectively with developers or technical consultants, ensuring smoother handovers and fewer bottlenecks.

Picture yourself in a customer meeting where a prospect asks, "How does your product integrate with our existing tools?" Instead of deferring the question, you could quickly sketch out the integration possibilities or show a lightweight prototype. Coding, in this context, becomes a confidence booster for both you and the client.

Where It Can Go Wrong

However, leaning too heavily into coding has its risks. As SEs, our primary job is to deliver value through conversations, not code. Over-focusing on technical aspects can create several problems:

• Disconnect you from business users: Most non-technical audiences care about ROI, efficiency, and usability, not API calls or coding logic. Focusing on the latter might lose their attention.
• Dilute core responsibilities: Spending too much time coding can detract from other critical tasks, like refining your pitch, understanding competitive differentiators, or supporting the sales cycle strategically.
• Set unrealistic expectations: Diving deep into coding risks overpromising technical deliverables that fall outside your role or the product's scope.

Balancing Act: Code as a Tool, Not the Focus

Striking the right balance is where great SEs differentiate themselves. Coding, when treated as a tool rather than a focus, can amplify your effectiveness without overshadowing your primary role.

I've seen SEs use simple scripts or automation to customize demo data, simulate a customer's environment, or build small utilities for sales teams. These contributions don't just impress customers; they also enhance internal collaboration, speeding up the sales cycle.

How AI is Changing the Game

The rise of AI is making coding less of a barrier and more of an enabler for SEs. With AI tools like Claude or GitHub Copilot, even SEs with limited or no coding experience can achieve technical outcomes that once required a developer.

AI can help in numerous ways:

• Generate example scripts or APIs for customer use cases
• Troubleshoot demo configurations on the fly
• Personalize content for proposals or presentations, reducing manual effort

In many ways, AI acts as a safety net for SEs, allowing them to deliver technical solutions without needing to master coding. It democratizes technical expertise, making it easier for non-technical SEs to add value in technical conversations.

Beyond the SE Role

What's fascinating is how these skills extend beyond traditional SE responsibilities. Coding and automation can help you contribute in broader ways:

• You can streamline internal processes by automating repetitive tasks for your team or creating tools to simplify workflows.
• Enable sales teams by building simple tools or dashboards that give account executives faster access to critical data.
• Finally, these skills support professional growth, preparing you for roles like product management, where understanding both the technical and business sides is crucial.

In today's competitive SaaS world, SEs who can balance customer empathy with technical acumen become invaluable not just to their customers, but to their teams and organizations.

Wrapping It Up

For non-technical SaaS SEs, coding isn't a must-have, but it's undeniably a value-add when applied strategically. It's not about replacing your primary responsibilities; it's about augmenting them to deliver greater impact.

With AI lowering the barriers to technical expertise, SEs today have more tools than ever to navigate technical challenges without losing sight of the customer. The goal is balance: using coding and AI to solve problems, enhance team efficiency, and simplify customer journeys, all while keeping the focus on outcomes.

In the end, coding for SEs isn't about becoming a developer. It's about becoming a more versatile, impactful advocate for your customers and your company.