“During the first month, I ramped up on our codebase, learnt to work with my teammates, took online training to learn about the technologies we were using, and started to take small refactoring tasks.”
What was your university and programme?
My initial degree was in Management from Kedge Business School in France. I worked for a few years after graduating in a HR data analytics role, which gave me experience in tools such as MySQL. I became more interested in IT and decided to do the MSc Computer Science (Conversion) at UCD.
What do you like about your current job? (What do you do each day?)
My team works on Cloud Orchestration, which involves moving the Workday application from private to public clouds. I like the variety of tasks I can get involved in on a daily basis. We are also working with trendy technologies (Kubernetes & Docker) which are very useful to know about. I also enjoy the “full-stack” aspect of the role, which allows me to learn a lot about system administration & networking and really broaden my skills.
What skills/technologies have you learnt since you came to Workday?
I’ve learnt a huge amount since joining Workday. My team works on containerising applications, and we are using Kubernetes as our orchestration manager. I hadn’t heard of Kubernetes before joining Workday, I read about it the for the first time after I saw it mentioned on the job description of the role I was applying for. We also use Docker, which I had heard about before joining Workday, but had never used. Programming wise, we are using Ruby, Groovy, Golang and Bash scripts.
What's been your favourite event at Workday since you started?
The summer party. It was amazingly well organized and I could not believe how well Workday catered for its staff. It was a carnival theme, with a funfair and bands and lots of great food.
Tell us about your interview process - do you remember the kinds of questions you were asked? Was it difficult?
I first had a chat with a recruiter, where we discussed the role, the teams, and the expectations (both Workday’s expectations and mine). Then I had a tech phone screening with the person leading my department. The questions covered were quite broad. There was a lot of questions around data structures and polymorphisms, as well as a few full-stack questions. After that interview, I had a programming test to take at home, and then a final face to face interview. The face to face interview lasted about 2 hours. I met with the head of my department for about 30 minutes. We talked about the technologies they were using in the term (Kubernetes, Docker, AWS…) and whether I had experience with them (I didn’t – but at that stage I had learnt a bit about them so I was able to talk about them during the interview). Then for 1 hour, I met with 2 members of the team I would join. There was a coding challenges, and some questions about infrastructure designs and more data structure questions.
Where do you want to be in 5 years?
I would see myself as an engineer, and my hope for a 5 years period is that I would be working with a different set of technologies, or that I expanded the range of technologies I work with.
How was your first month in the job?
During the first month, I ramped up on our codebase, learnt to work with my teammates, took online training to learn about the technologies we were using, and started to take small refactoring tasks.
What advice would you give to graduates looking for a job at Workday?
Learn your data structures and prepare for basic coding challenges. There’s a website – pramp – where you can get mock programming tests with other online peers. This is valuable to learn how to take a coding test and how to properly explain your thought process when solving a coding puzzle.