Quentin Vinesse

2 months

After finishing my onboarding, I started building some demos and join pre-sales calls with AEs to help have some French prospects sign up for the Answers Beta, while working on some UK AFTs at the same time. Lately I've been working on getting the Yext French Answers experience ready for International day.

Leading my first Answers demo for a real client (Fitness Park), because I had to build it pretty last minute and gather some data on their website myself, but we ended up really impressing them, they signed up to the beta, and we had a great kickoff call last week.

Becoming an administrator has motivated me to start getting serious about learning HTML and CSS, which I had been planning on doing for a while but finally was able to do thanks to the onboarding and the fact I use these languages on a daily basis when building Answers experience for clients. It has also allowed me to revisit accounts I have implemented on Listings when I was an implementation manager, but this time working on Answers with them and meeting new people from different departments (IT, Devs, etc..). It is great to see different aspects of these companies.

A common question I get is if we actually have to write code at all, and we do! For every client and demo I've worked on so far, there is some customization work that needed to be done, be it adding CTAs on Answers cards, creating a header and footer in HTML and CSS, customizing the look and feel of CTAs, there is always coding involved, so being familiar with HTML and CSS is very important.

So far, working on Answers projects has been a blast, but I'd say the toughest challenge I've faced is having some developers on the client side in calls who ask some very technical questions about the code and integration. Thankfully, this gets better with experience, and our technical documentation is my best friend during these calls and to write follow-up emails!