Interview Evaluation

Evaluation of Interview Task

Pre-Interview Task

I recently had an interview for a position at Mazzor Studios as a programmer, and as part of the interview process, I was required to complete a pre-interview task to show off my programming skills. The task involved me fixing bugs in an existing unity project that they provided, and adding new features to the project as requested. Each change I committed to the project I was tasked in documenting them so that they can have a better understanding of my changes.

Interview Task

Overall, I felt the interview and task went reasonably well. I was told that I was able to effectively demonstrate the skills needed for the position and show off my knowledge with the gaming industry and unity.

I was informed during the interview that my pre-interview task was conducted to a good standard and I was able to achieve everything that they were looking for. Specifically, they highlighted that the fixes I implemented showed a good understanding of Unity and C#. I added a default switch case to the colour changer, which was well received.

However, they also provided some constructive criticism in my feedback, which I will definitely keep in mind for future interviews and pre-interview tasks. The main area for improvement was the documentation. I was told that it was deemed "ok," I was told that adding screenshots with annotations, would significantly improve the documentation of my work. Additionally, the feedback suggested that adding comments to my code changes would be beneficial to other programmers.

Looking at the feedback I was provided, I agree with the things which were stated. When looking back at the code documentation, I should have commented the code which I had added for better readability, however since the code I changed was so minimal I didn’t think it would have mattered at the time. I understand that clear and documentation is crucial for working with teams of people, or when others need to understand and maintain the code that you have written. However, The suggestion of using screenshots with annotations is helpful, as it will allow me to show off my changes visually.

In conclusion, I believe that my interview went reasonably well. Though I had a few things that I could improve on I believe my execution was overall good.

Comments

Post a Comment

Popular posts from this blog

Devlog 1: Climbing System - Initial Implementation

Devlog 1: Climbing System - Initial Implementation Objective: The purpose of this week was to implement the basic ledge grabbing and horizontal movement functionality based on the YouTube tutorial. Project Name: Mini Project New Features: Ledge Grabbing: Implemented functionality enabling the player to detect if they are underneath a ledge while jumping. This allows the player to grab onto a ledge This Involved setting up collision to detect the position of the ledge and changing the player state. Ledge Grab Animations: I Integrated animation assets for the player character's ledge grabbing pose and idle hang, These animations where from Mixamo. I created animation blueprints to handle the different animations states the player character could be in. I added code into my climbing system code to trigger these animation. Side to side movement I enabled the player movement along the ledge while hanging. This involved creating more collision detection to make sure that there were still...
Read more

Devlog 2: Climbing System - Mantle Implementation

Devlog 2: Climbing System - Mantle Implementation Project:  Mini Project - Climbing System Implementation Objective: Implement the mantle system, enabling the player to climb onto ledges from the hanging state and from the ground. New Features: Mantle System  Following the tutorial I was shown how to integrate the mantle system from the Advanced Locomotion System. Which allows the player to climb up onto ledges. I modified the mantle system code to use my modified animations and to work with the climbing system I have been working on. This took me around 4 hours to complete. I Implemented logic to detect mantle-able surfaces so that the climbing system knows what is climbable and what isn't. I moved code for the mantle system from ALS System into my project Progress: During this week I have been slowly implementing the mantle system into my project, following the tutorial. This system will be used for allowing the character to be able to climb up the ledges they are hanging ...
Read more

Devlog 3: Climbing System - Bug Fixes

 Devlog 3: Climbing System - Bug Fixes Project: Mini Project - Climbing System Objective: Fix bugs with the animation playback and player input with the climbing system Progress: This week I focused on bug fixing and improving the climbing system code, this included fixing issues with animation and player inputs. Fixed muliple bugs Animtions were not playing correcly, would make the player snap around when the mantle animtation played Player input was being disabled after the player completed a ledge climb, stopping the player from moving around. Another issue was that after a ledge climb, the player was unable to climb another ledge, because of code not reseting vars correctly. Fixing these issues required me to review the code I had already written, focusing on the state management and animation blueprints. Main Issues Animations were not cut correctly to provide a smooth animation transition while holding on a ledge Player input was not being reenabled after the player completed...
Read more