Job Satisfaction at FNZ

Currently doing self-led training to get up to date with the company's systems and codes. Challenging enough to stay interesting

My role is Technology solutions graduate. My current responsibilities include getting familiar with all products, business terms, and business logic and mastering the tech stack.

Fixing bugs, building user stories, writing dev tests, documentations.

Analyst Developer : making new builds of code for the project/ fixing bugs, etc.

Currently as part of the graduate program I am working in the developer immersion learning about and training in that side of things. On the day to day I will work on things that have been assigned to me whether that be fixing bugs or working on new stories.

As a graduate, you are responsible for ensuring software is delivered from start to finish, whether it be analysing the requirements, to developing them or fixing bugs, then finally testing the changes thoroughly.

There is always something to do at FNZ which is a double-edged sword. Can never say I've been bored at this job, but can get overloaded at points. With the new team system and having a manager more closely monitoring my work and my workload, I am always given a couple items to work on at a time which is perfect.

Check the status of tickets. Understand the prioritsization of tickets. Solve tickets and discuss issues and problems in the stand up

I enjoyed the job more and more as I grew more familiar with the codebase and learned to do my job better. I suspect this would have continued as I grew more experienced.

Do some test work.

I'm helping with testing of given platform. I know i can achieve bigger results doing these tasks

Lots of trainings, some of which it seems we will not be using in our current immersion

Workloads with a good opportunity to learn.

Over the past few months I've done work in testing, development, and production support. Testing involves executing manual tests and raising defects, developer work involves picking up defects and resolving them, and production support can be anything from fixing defects to reviewing sql scripts depending on the day

The day to day work is rewarding, coming in each day will see you face a new technical challenge or bug to resolve. This has meant, for me at least, that the days never seem to drag on or get boring. There's plenty to learn and FNZ do put a lot of effort into training those with a technical background in financial concepts too.

Finding bugs to fix, investigating the cause, implementing fixes, and keeping jira up to date.

Testing software and creating user stories.

Main role at the moment is in development; I either get assigned defects directly, or assign myself to ones from the general queue, and debug my project's codebase / discuss with testers and analysts to identify where and whether issues need to be resolved. Aside from a few meetings, that's the bulk of everyday responsibilities.

The work is enjoyable, I have been able to work on many different items already and have started forming a better picture about the business and project as a whole.

The main thing I do is fix bugs and work on stories. The analyst responsibilities are more varied but basically just require thinking through the end product and what would be best for the customer/performance/scalability/extensibility/etc.