5 things I have learnt as a Customer Engineer
Published: 2022-09-08 12:37:50

---
title: 5 things I have learnt as a Customer Engineer
published: true
date: 2022-09-08 09:42:09 UTC
tags: 
canonical_url: https://write.as/kelvintaywl/5-things-i-have-learnt-as-a-customer-engineer?pk_campaign=rss-feed
---

## Background

It has been an eventful year so far being a part of CircleCI's Support Engineering team. This also marks my first year in [Customer Engineering](https://en.wikipedia.org/wiki/Customer_engineer).

This has been a different challenge for me, as I transitioned from a past life of a software engineer.

I have learned a lot. I hope this list is useful for folks switching to Customer Engineering!

## 1. Empathy is important

Empathy is an important element in communication. This remains true even when two engineers work through a problem.

Customers write in a support ticket because they need help solving an issue. They likely spent a lot of time trying to solve it, and _may be frustrated_ at this point. _On that note, a good error message will help users better than a technical support answer can._

In addition, English may not be the main or strongest language of the customer. I find that short and simple instructions can go a long way.

Always remember to factor these points, when you reply.

## 2. Detect XY Problems early

It helps to see the bigger picture of a customer's ask. At times, their original question can be [a XY problem](https://xyproblem.info).

I have observed that such questions generally exhibits the following _smells_:

- the customer is trying to do something that veers from the common use-case or best practices
- the customer is unable to articulate well what their true intentions are, even when quizzed further

In these situations, never hesitate to **confirm what they are trying to solve exactly**. This makes sure that you understand their problem and motivation.

This brings about my next point below.

## 3. Clarify, clarify and clarify

Solving a problem requires understanding the problem first.

Not everyone is great at writing about their problem at hand. There will likely be details missing, and these could be important.

Remember that asking further questions is also a valid response. It is even better when you can explain how their answers will help in the next step.

For example,

> “Would you be able to do 123, and share the output here? This will help us confirm or rule out ABC.”

At times, these questions can help customers arrive at their own answer or solution.

## 4. Anticipate the next question

Solving an immediate problem for the customer feels great! Anticipating potential challenges, and sharing them is even better.

I find this to be a useful trick when dealing with new users in particular.

New users are likely still trying to figure out how to use your product. Beyond the immediate question, they may bump into another hurdle soon.

If you can anticipate this early, share your knowledge while you close out the ticket. This proactiveness will help with [ticket deflection](https://whatfix.com/blog/ticket-deflection/) too.

## 5. Share knowledge

Overtime, you may end up being the “subject matter expert” for certain topics around the product.

Instead of being the bottleneck, make efforts to distill this knowledge to the rest of the team.

This can come in the form of:

- pair ticketing (like pair programming!)
- internal _or_ public knowledge base (even better)
- Ask Me Anything (AMA) sessions

This can only help the team, as there becomes a better balance of knowledge amongst members.

You can apply for time off in peace, knowing that your teammates got this!

Oh, and one last piece of advice. Slack should never be your team's knowledge base; Invest in documentation! :book:

I hope you have found this a useful and good read.