National Coding Week: Hear from our Analysts
As part of National Coding Week (14 – 18 September), we've interviewed some of our analysts about their interaction with coding in their everyday jobs and if they have any advice for those looking to learn coding themselves.
Having started with Vanquis in our Contact Centre, Josh, Senior Analyst in Insight Analytics shares his journey into coding, his experiences and some handy tips...
Tell us a little bit about your role at Vanquis.
I currently work within Insight Analytics. Most notably owning the production of the Customer Outcomes Dashboard each month. Almost all of the work I complete is centred around the Customer; including things such as: spend, fees, external credit score. To provide a specific example; I have recently looked into the impact the “Eat out to help out” scheme had on spending across the portfolio.
How do you use coding in your role at Vanquis?
I use coding to translate data sources into stories. Starting with a raw table(s), coding certain conditions and requisites before wrapping up into particular views to support analysis.
What led you into a job in coding?
I was/am particularly interested in strategy, which is effectively everything involved with making a business decision. I recognised that a great deal of this comes from analytical capabilities, therefore it seemed like a critical skill for me to learn. I thought coding [analytics] would be a fantastic foundation in order to build my career.
What’s the most rewarding part of your job?
Being rewarded with the offering of new opportunities to learn/progress; as a direct result of the hard work being recognised by senior stakeholders.
What was the hardest part about learning?
Every analyst codes differently; whether it’s a simple difference in formatting through to a deliberate difference in functions. One of the most difficult aspects to begin with was taking scripts from experienced analysts and trying to decipher; this is sometimes a requirement because legacy processes are typically built by analysts no longer with the business, so if something was to fall over – a new [to the code] analyst would be required to try fix. Often, it was quicker to reformat and sometimes re-write than it was to fix – particularly if there weren’t supporting comments.
Are there any tools or resources you would recommend?
Google is perhaps my most regular go to; you can search almost anything you would need when it comes to syntax etc. Another key for me; asking colleagues around me. This has taught me a tonne of new things e.g. syntax/functions/thought processes – whilst allowing me to build key relationships.
Top tips?
Be intentional. Really consider which area of analytics you want to get into. I personally think the enjoyment of coding isn’t related to coding itself; its related to the underlying topic. If the underlying topic interests you; coding is much more enjoyable and rewarding.
