• 1Search for courses by Study Area, Level and Location
  • 2We deliver you all the matched results
  • 3Choose one or more course providers to contact you
Industry

Distance from location (kms)

Exact 5 10 25 50 100

Posted since

All 2 Days 1 Week 2 Weeks 1 Month

Sort results by

Relevance Date

4

April

Engineer

ANZ - Sydney, NSW

IT
Source: uWorkin

Source: uWorkin

JOB DESCRIPTION

As a Software Engineer within the Balance Sheet and Treasury squad, you will be focused on delivering quality software solutions to the global Balance Sheet Trading group.
The Balance Sheet Trading group manages the interest rate risk and maturity mismatch of the assets and liabilities on the bank's balance sheet.
Your team has built a system called ARM. ARM is a Risk and P&L system used by the Balance Sheet trading group. ARM's functionality is being continually expanded and improved. ARM:

  • Is rolled out globally
  • Has users from Front-Office, Market Risk and Finance
  • Is an internally developed system; Java/Linux server side with a C# WPF UI
  • Uses OLAP/MDX to produce reports and allow filtering and drill-down
What might a 'day in the life' look like?
Only the names have been changed… At 9:15 you log in and shortly after call into the team scrum where you report on your sprint tasks. You listen to your other team members Alisha, Mehar, Francis, Darna and Anatoly about what they've been doing.
You were assigned a JIRA to add a feature to the ARM UI, in the last sprint planning, and have been working on it for a few days. This involves changes to the C# WPF UI code, Java client services code and some DB entity changes.
As you work on the feature you have some questions for Alisha (Business Analyst), about the requirements and acceptance tests. You have a Teams call with Alisha at 11am, she updates the JIRA with some changes you both agree.
You develop your solution following the coding standards of the team, writing some new classes and changing existing code. As you go you add unit tests and check the code coverage.
At 2pm you get a notification asking you to review a PR (pull-request) from Anatoly for a feature he's implemented. You stop your task and review the PR, reading the JIRA to make sure you understand the feature. This PR makes changes to the rates-service, which is a part of the system you've not worked on. So you read the Confluence pages on this service. You spend some time reading the rates-service code and ask a couple of questions to the Anatoly. You think the confluence pages are missing some important information, so make a couple of edits to add these details. As you do the review you notice there doesn't seem to be any unit tests for one of the acceptance tests. You also think that by adding an interface some of the code can be simplified. You add these as comments, and mark the PR as needing more work.
Back to your feature now. You think the feature is complete so you deploy it to the server, and perform the acceptance tests. One of the test fails so you realise you need to add some changes. This involves a code change and an extra unit test. After redeploying the acceptance criteria pass.
You raise a pull-request and before requesting a review, check it yourself and make sure you're happy with the change-set. Its 5:30pm and the day's flown by.
Who are you?
Three months into the role... You love learning and want to understand what the Balance Sheet Trading desk does, and their business processes. When you started you knew very little, but now you know some basics and are reading some books others have recommended. Others team members have lots of knowledge so you ask them questions and when they show you how to do something, or explain you take notes. You like to document things you've learnt so you check Confluence and updated the documentation.
You didn't have any experience of OLAP, MDX and Spring when you started but you've learnt and understand them well.
When you write code, you like to it to be simple, clean with nice inversions of control. You love seeing what you've done help users and increase their efficiency.
What will you bring to this role?
The following skills are important for this role:
  • Java and Spring
  • UI development
  • Maven
  • Dependency injection
  • Unit testing and test coverage
  • SQL
  • JSON
  • HTTPS
The following skills and experiences will help you succeed:
  • C#
  • WPF
  • Dev Express WPF controls
  • Nuget
  • OLAP and MDX
  • Oracle RDMS
  • Experience learning a large code base
About ANZ
At ANZ, everything we do boils down to 'why' - our purpose - to shape a world where people and communities thrive. We're focused on seeing our people thrive just as well as our customers. We'll give you every opportunity to develop your career.
We are responding faster to changing customer requirements, focusing on the things that matter most, energising our people, eliminating waste and reducing bureaucracy.
A happy workplace is a thriving one. So in order to attract and keep the best talent, and say thanks for the hard work, we make sure all our employees are rewarded.
We work flexibly at ANZ and encourage you to talk to us about how this role can be flexible for you and any adjustments you may require to our recruitment process or the role itself. If you are a candidate with a disability, let us know how we can provide you with additional support.
To find out more about working at ANZ or to view other opportunities visit www.anz.com/careers. You may apply for this role by visiting ANZ Careers and searching for reference number AUS128746.

eFinancialCareers