Initially hired to help support the development team as a consultant, I was given the chance to take on sole responsibility to rebuild the company's flagship product from the ground up. This has been an amazing opportunity that I'm very grateful to have been trusted with, and its been a massive challenge including- building a dev team from scratch (we are now 4 strong!)- taking on all architectural decisions- being across all infrastructure changes to support the new product- designing it in a way that it is a seamless upgrade as far as the clients see - less than 30 minute outage, with no password or auth changes- it supports offline- it is fully mobile first- full Azure devops pipeline for continuous weekly builds, with a test framework to ensure qualityIt is written in Blazor WASM, C#, and with a SQL backend and has been a real joy to build. Clients are live on it, and the feedback has been overwhelmingly positive.Backed by a great team, and a fantastic company culture to push and innovate, I feel I have truly stretched and tested myself.

Working as a senior developer after moving back to FIS. Developing new features for new clients in C# and SQL.

An all encompassing role in a smaller company (approx 20 employees), I was responsible for supporting a 15+ year legacy system while simultaneously architecting a new ground up rewrite to take the company forward. I was the direct manager of 5 staff and enjoyed my time here bouncing between firefighting and interacting with customers directly to big whiteboard future planning and predicting what customers would want tomorrow.

I currently lead the Response Team. This is a team I was asked to set up in February 2017, and is responsible for all incoming client cases - fixing live bugs in live systems, and triaging all client inquiries. In the last year the Response Team has become a vital part of the business, and it has since grown to 30 team members across 2 countries (NZ and India). In April 2018 I became a Technical Lead along with Lead of the Response Team. It is the most senior development position for a Software Developer. The additional duties that brought were - high level architectural reviews- functional reviews of new system features - management responsibilities.I have also travelled overseas as a trouble shooter for UAT and installation issues. Due to the nature of the team I lead, I have been asked to travel with only a days notice.As the Response Team has grown, I have encouraged it to be self sufficient without me by:- Empowered my team to be able to resolve high pressure situations on their own, only escalating to me in the most critical of situations- Putting new work flows in place to ensure that when I'm not around the cases still get prioritised and worked on in a timely fashion- Giving the team ownership of problems

In April 2017 I was asked to form a new team within the business called the Response Team. It is responsible for all incoming client cases - fixing live bugs in live systems, and triaging all client inquiries. It initially was formed with 2 developers, but over the year grew to 8 and was split across 2 countries (New Zealand and India).Since inception, this team has performed better than anybody imagined. We have had to deal with multiple Priority 1 cases (entire system down) and had to meet strict and challenging SLAs.My role grew dramatically as a result, and my new responsibilities were:- Responsible for meeting strict SLAs (4 hour turn around of priority 1 cases, regardless of day or time)- Responsible for prioritising cases, and ensuring less important ones still kept moving so nothing would stay still- Liasing with the L2 team to ensure that clients were happy- Being the escalation point for evolving issues- Mentoring and 1-2-1 meetings with my team members- Interviewing candidates in 2 countries to fill roles in the growing team- Continue to develop code as well, to fix critical issues- Implemented a SQL code review process so that SQL run on client systems was rigorously tested and reviewed

As a Senior Software Engineer, I gained more responsibilities in my job.Aside from the routine day to day duties of a Software Engineer, I would also have to- Give technical presentations to up skill the wider team- Discuss designs and specs at a higher level with the design team- Review design decisions- Mentor and support newer developers- Take responsibility for ensuring deadlines were met within the team

In the role of Software Developer I had the following roles and responsibilities- Implementing specifications as requested by the Design Team- Continuous code improvement, maintaining older code as I developed features- Code reviews - every commit was checked, so I would review the work of others, along with having my own work reviewed- Finding and fixing bugs- I coded in C#, and supported both MS SQL And Oracle databases

At RCS, I created software used by radio stations all over the world to manage their advertising and revenue. The software encompassed booking advert spots to playing them over the air to billing the customer. The product is both a detailed desktop application as well as a fully featured web site, and is driven by SQL Server.The majority of my time was spent adding features and functionality to the system. This was mainly back end work on the central API coding in C#. My largest solo project was writing a data import tool, to allow legacy systems to migrate into the latest software.Other jobs I've worked on over the years:- I spent some time doing a DevOps role, writing an automated build system, including overnight builds, using MSBuild with Ant and NodeJS integration. - I wrote the installer using Inno Setup

Whilst at Massey, I was in sole charge of several websites of varying sizes. The most important of which were the main websites for the College of Sciences and well as a large internal Intranet, used for measuring academic staff workloads and funding for papers.I spent the majority of my time updating and rewriting legacy code as well as developing some new features. One of my biggest projects was developing a large college-wide staff profile system, that was just being successfully rolled out when I left.Lastly, I also worked alongside the other Colleges' web staff to help shape Massey's future web direction, a lot of which was taken on board and used.