SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
VAST Data is seeking a Customer Success Tools & Automation Engineer to design, develop, and deploy automated workflows that optimize customer success operations. This role bridges engineering and customer operations, focusing on process improvement, efficiency gains, and enhanced customer satisfaction through thoughtful automation.
You will own the full lifecycle of automation initiatives: identifying optimization opportunities within customer success processes, designing solutions using modern tools and frameworks, and implementing them across the organization. You'll analyze customer data to uncover trends and patterns that inform automation strategy, then translate those insights into technical solutions.
Key responsibilities include developing automated workflows using Python, Bash, and Django; configuring automation platforms like Ansible and Puppet; integrating with Salesforce CRM systems; and leveraging Grafana for data visualization and SQL for analytics. You'll provide technical expertise to the customer success team, ensuring they can effectively use new tools and processes. Documentation and training are core parts of the role—you'll create runbooks, maintain process documentation, and conduct training sessions to drive adoption.
You'll collaborate closely with Customer Success, Product, and Engineering teams to understand customer needs and translate them into technical requirements. This is a hands-on engineering role with strong cross-functional exposure, ideal for someone who enjoys solving operational problems at scale.
Required: 3–5 years of automation engineering experience, ideally in customer success or customer service environments. Strong proficiency in Python and Bash; experience with Django, Ansible, and Puppet; familiarity with Salesforce; knowledge of Grafana and SQL. Excellent analytical and problem-solving skills, with the ability to communicate complex technical concepts clearly to non-technical stakeholders.
