Growing Your Career in Technical Support: 4 Tips for Getting Hired at Elastic from Support Director Heidi Sager
Heidi Sager loves math, but she also loves working with people.
She always has, which is why she enjoyed her part-time job working at the IT department of the University of Colorado while she was studying electrical engineering. (She'd started in computer science, but explains that it "wasn't for her" and switched her major.) She helped students and professors with word processors, basic programming, and software checkout, and took a full-time job after graduation as a UNIX system administrator.
"I'm definitely not the kind of person who could be heads down coding all day or, you know, in a lab all day long," says Heidi, who is currently a Support Director at Elastic. "I really like personal interaction and helping people solve their problems."
The technical challenges and interpersonal opportunities of tech support were perfect for Heidi, who became a support manager relatively early in her career after a battlefield promotion. "Someone thought it was something I might be good at, and it turned out they were right!" she says.
At Elastic, Heidi explains that her number-one responsibility is making sure that their team of support engineers has everything they need to be able to support Elastic's customers. "We clear roadblocks and things for them so that they can do what they're best at," she says. Second to that is her responsibility to evolve the business of support at Elastic. "We're developing tools and changing processes and procedures to make sure that we're as efficient and scalable as possible," Heidi explains.
Heidi is also responsible for hiring support engineers for her team. She's hosting a PowerToFly event on January 27 at noon EST to connect with other women in tech and talk more about open roles on her team (if you'd like to be considered for an invite, you can email us at firstname.lastname@example.org!). Ahead of the event, we sat down with Heidi to learn more about what support at Elastic looks like, what she's hiring for, and what she loves to see (and not see!) in candidates.
Support at Elastic is a team sport
Her team works with internal teams like sales, while also interfacing directly with external customers, and it's Elastic's human-first approach that Heidi appreciates when it comes to customer interaction. "I've been at places where the customer's always right, regardless. And I've been at other places where it's 'we do the right thing' regardless of what that means," she says. "At Elastic, we're very much on the 'do the right thing' side, which is awesome."
That means that the support team often works together to solve issues. "There's going to be times when you make mistakes; everybody's human. As long as you did it with the right intent, that's all that matters. Somebody's got your back and they'll help you navigate, whatever that means," explains Heidi.
Heidi loves to bring new engineers on the team. It's when she really gets to see teamwork in action. "They always start off a bit nervous," she says, "asking a lot of questions and feeling like they are being a drain on the team. But then comes a point when somebody really senior asks a question and the new person is the one to answer it. It's the best! Not everyone can know everything. And we're very open to asking for help."
The team approach is supported by a culture of feedback. Heidi's engineers have regular 1:1s with their managers and every week, her team publishes all of the customer satisfaction surveys they've received for the company. "It goes out to the entire organization. All the details, good or bad, and what we're doing about it. It's great. Sometimes we mess up and we own that. We apologize and try to do better. Sometimes there's a product gap or a product defect or something that needs to be addressed. Sometimes the customer is just not aligned with what we can deliver," she says.
Along with regular check-ins and feedback on how they're doing in their day-to-day responsibilities, Heidi also hosts quarterly conversations focused on her team's broader career and personal goals. She's developed many career paths within and outside of her team and helps each engineer find the path that's right for them. Those paths include becoming support developers who work on the internal tools her team uses, like an automated case assignment feature; managers on her team and others; consultants and trainers for customers; marketers; solutions architects who travel with the sales team to demo products; or developers and engineers on other teams.
For Heidi, the support team is the best long-term place to be. "It's new all the time. We have new products, and new services that are coming to us. Every customer uses our software a little bit differently, too. It keeps it interesting and not repetitive day after day," says Heidi. "I think most of the folks that enjoy support are problem solvers. They just love how it feels when you can solve that problem and move on to the next and do it all over again."
What Elastic is looking for: 3 paths, 5 key skills, and 4 dos and don'ts to keep in mind
There are a few archetypes of people that Heidi sees finding great success in support:
- Developers who want more human interaction. Should we just call this the Heidi path?
- Customer support professionals. "Some people with a support background decide they really want to focus on the technical side; maybe they've gone back to school for some technical certificate or degree, but they still want to use their soft skills and customer support skills," explains Heidi.
- Managers who want to be "responsible for [their] own destiny." Heidi explains that she's had people who explored technical management but realized that they wanted to stay more of an individual contributor, and really ended up enjoying the support engineer role.
And regardless of what track they're on or where exactly they come from, there are a few things Heidi looks for in applicants:
- Potential over specifics. Don't have deep knowledge of the Elastic Stack? That's fine. You can learn. Though Heidi does suggest looking into the free download of Elastic's software and digging in a bit before your interview. "We love when we folks that come in can ask questions or explain what was challenging; it shows great initiative."
- A base of technical know-how. You don't need to be a developer, but you do need to have been in a technical environment before. "If you have an understanding of how distributed systems work, that's great," says Heidi.
- Strong communication skills. Written is more important than verbal, since the team communicates through tickets, but both matter. "You need the ability to communicate to various levels of customers—very technical to not technical at all—and convey a message, ask the right questions, and be able to interpret the answers."
- Conflict management skills. While sometimes Heidi's team works with customers who are planning ahead and need some help, oftentimes they're called in for crises when something's not working. "There can be heated situations, so the ability to diffuse that and talk through it is key," says Heidi.
- Follow-through. "If you say you're going to do something, like get back to [a customer] in a couple of hours, you need to get back to them in a couple of hours," Heidi says.
Heidi also has a few dos and don'ts for applicants to keep in mind:
- Do: Review Elastic's Source Code. "It's the guiding principles for how we do the things that we do; it's what's most important to us," explains Heidi.
- Don't: Skip doing your homework. "My number one frustration is someone who is there for a job, but not for the specific job. When someone really doesn't know what Elastic is about or what our software does, even at a high level, I don't love that," says Heidi.
- Do: Be yourself. "I love when somebody is really, truly being themselves, when you can see that they're showing you what they're all about and not trying to fit a certain mold. We really don't want a hundred of the exact same person," says Heidi.
- Don't: Disqualify yourself. "Don't assume that we're looking for someone who has been running the Elastic Stack for five years and knows everything there is to know about it. There's a lot more in support then than just that technical side and we're open and excited to bring in junior people all the way up to senior people," says Heidi.
How Hopin’s CCO Knew a Startup Environment Was Right For Her—and Two Questions to See If It’s Right for You
If there's a thread that connects all the different facets of Rosie Roca's life, it's the power of bringing people together.
From how she was raised, to how she got her first job, to the decision to leave enterprise software to take on her current role as the Chief Customer Officer at fast-growing events technology platform Hopin, a focus on community has helped to guide Rosie's decisions.
After a brief hiatus, we're picking our series of diversity, equity, and inclusion (DEI) terms back up!
This month we're looking at different ways of addressing people with disabilities.
In honor of Black History Month, we've been reading some of the great books written by four of the talented Black speakers that joined us at our recent Diversity Reboot Summit—because Black History Month isn't just about looking to the past, it's about elevating the Black voices that are helping to build a better present and future.
Have you read any of the books below? Let us know what you think!