You love troubleshooting technical issues and you are eager to help your team members grow, by coaching and sharing your knowledge with them. As our Senior Support Analyst, you are internally and externally the go-to person for any complex technical challenge when implementing or using one of our products. You love working in a place where not everything is predetermined, but you work together with other colleagues to help ZIVVER grow step-by-step
A day at HQ
(We are living during a pandemic, so there’s no such thing as a day at HQ. We fully support a work-from-home situation (read as monitors, headphones, webcam, docks, and whatever else you might need). In normal times though...)
Two of your team members are working on troubleshooting a new issue at a new customer. They already had multiple TeamViewer sessions with the customer to try to understand when and why the problem occurs. One of your team members also tried to reproduce it on our own test environment but with no luck. Now the customer is complaining that are relative simple problem takes days to diagnose! So just before lunchtime your team members ask you for help. You listen to the background of the problem, the different theories they’ve tried and advise them to call the customer and ask for a test account.
Time for lunch, and time to discuss the very important matter of your social life with your colleagues. The lunch room is abuzz with excitement about an upcoming company ski trip. With renewed energy, you return to your desk.
One of your colleagues called the customer during lunch. The test account is already available! Now it's time for you to do your magic. You open the environment of the customer on one screen, on the other screen you put up one of our own test environment. For the next hour you try different approaches. When looking for events in Kibana you suddenly notice an unexpected event. It's not an error, but it looks like new functionality is already turned on for this customer. It takes some time for you to set up this functionality for one of our test environments. But when this is done you can easily reproduce the problem. You immediately file in a bug report for this. One of the developers has look at it, but doesn't understand what's happening here. So you explain to him that this is the effect of the new functionality and how you set it up in your environment. You both decide to inform the Product Owner as the support for this new functionality in this client requires a User Story put on the backlog.
You are just in time for the weekly meeting and you share this new knowledge within the team.