From DevOps engineer to solutions engineer: Bridging the gap between technology and business

After spending over seven years as an application developer and then a DevOps engineer, I recently transitioned into the role of Solutions Engineer at HashiCorp (some companies have different titles for this role such as Sales Engineer or Systems Engineer, etc). This shift was more than a change in job title; it was a significant transformation that leveraged my hands-on technical experience to solve broader business challenges. In this blog post, I'd like to share how my journey unfolded, the importance of mentorship, and how my practitioner background became an invaluable asset in my new role.

»The DevOps years: Driving organizational change

My early career was deeply rooted in the technical trenches of a legacy IT organization going through a modernization effort, but it was also a period where I became an agent of organizational change. When I joined the California Department of Transportation, there was a broken Configuration Management Database (CMDB). ServiceNow was newly acquired, and processes for automation and integration were broken. By the time I left, we had transformed these critical areas, leading to significant positive changes within the organization.

»Key achievements:

• Became a change agent: I championed and led the district implementation of ServiceNow CMDB. This centralized system streamlined asset management and improved efficiency. I also collaborated with cross-functional teams to redesign the change control process. This reduced system downtime and improved compliance with regulatory standards.
• Standardizing practices: I authored best practices for web applications and SQL databases, ensuring consistency and security across applications.
• Automating workflows: I established a DevOps team culture to automate workflows, improving deployment frequency.

These experiences were critical in understanding how IT organizations use technology to deliver value to their customers. I wasn't just implementing technical solutions, I was aligning technology with business objectives to drive tangible results and taking ownership of cultural change within the organization.

»The importance of mentorship and seizing opportunities

One of the pivotal factors in my career progression has been the mentorship I received along the way. I've been fortunate to work with leaders who recognized my potential and provided opportunities for growth. Transitions don't happen in isolation, they require leaders who are willing to take chances on people.

• Kevin Ross: As my manager when I was a system administrator, Kevin allowed me to grow by involving me in business-level initiatives on the networking and infrastructure side. His trust and willingness to delegate important tasks gave me the confidence and experience needed to tackle complex challenges.
• John Ramirez: As an automation and integration lead, John empowered me to foster an environment where DevOps practices could thrive. His support was instrumental in creating a culture of innovation and continuous improvement within our team.
• Joe Colandro: At HashiCorp, Joe took a chance on me by facilitating my transition into the Solutions Engineer role. His belief in my abilities made this significant career shift possible. Without leaders like Joe who are willing to invest in people, such transitions might remain out of reach.

These mentors didn't just provide opportunities; they cultivated an environment that promoted growth for those willing to put in the effort and ask for the chance to prove themselves.

»Recognizing the value of industry experience

As I contemplated the next step in my career, I realized that my deep technical background and experience in driving organizational change gave me a unique perspective. Transitioning to a solutions engineer role felt like a natural progression. My industry experience made it easier to understand my customers' challenges because I'd faced similar issues myself.

One of the most interesting things I learned was that business and technical challenges are remarkably similar across different industries. Whether in transportation, government, or the private sector, organizations grapple with issues like scalability, security, operational efficiency, and cultural change.

»Transitioning to solutions engineering: Bridging two worlds

Joining HashiCorp was a perfect fit. I was already on the path of using their technology in my previous roles, and their focus on infrastructure automation and cloud solutions aligned perfectly with my expertise.

In my role as a Senior Solutions Engineer, I found that:

• Understanding customer needs is key: Solutions engineering isn't just about being a technical expert. It's about understanding what the customer needs and delivering value through technology.
• Industry experience matters: My background made it easier to relate to customers' challenges and propose practical solutions.
• Cross-industry challenges are similar: The problems faced by organizations often transcend industry boundaries, making my broad experience valuable.

»Overcoming challenges: Adjusting to the sales culture

Transitioning into a sales-oriented culture was one of the significant challenges I faced. The metrics of success shifted from technical milestones to sales targets and customer acquisition/consumption.

To adapt, I:

• Developed soft skills: Enhanced my communication and presentation abilities to better articulate technical concepts to non-technical stakeholders.
• Embraced the sales process: Learned MEDDPIC to align with the sales culture.
• Balanced tech and business: Strived to maintain my technical edge while also understanding the business implications of the solutions I proposed.

»The rewards of bridging the gap

The move has been incredibly rewarding:

• Greater impact: Leveraging my practitioner background allows me to offer practical, real-world solutions that resonate with customers.
• Professional growth: I've grown not just as a technologist but as a strategic thinker who can bridge the gap between technology and business needs.
• Fulfillment: Helping organizations solve complex problems brings a sense of accomplishment that goes beyond technical achievements.

»Conclusion

Transitioning from a practitioner to a solutions engineer has been a transformative experience that underscored the value of mentorship and seizing opportunities. Being part of organizations that promote growth, provided you're willing to put in the effort and ask for opportunities, makes all the difference. Leaders who are willing to take chances on people play a crucial role in facilitating such transitions.

For those considering a similar path, remember that your hands-on experience is a powerful tool in bridging technical and business worlds. Seek out mentors, embrace opportunities, and don't hesitate to step out of your comfort zone. While adjusting to a sales culture can be challenging, the opportunity to make a broader impact is well worth the effort.

»What's next?

I look forward to continuing to help organizations navigate their technological challenges by leveraging both my technical expertise and understanding of business needs. If you're considering a similar transition or have experiences to share, I'd love to hear from you!

Acknowledgments: A heartfelt thank you to Kevin Ross, John Ramirez, and Joe Colandro for their mentorship and for taking a chance on me. Your guidance and support have been invaluable in my career journey.