Software Engineer

Description:

As a software engineer within the BST squad, you will be focused on delivering quality software solutions to the global BST group.

The group manages the interest rate risk and maturity mismatch of the assets and liabilities on the bank's balance sheet.

Arm

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.

• 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

Responsibilities

Participation in a daily Scrum and other events

You will be assigned a JIRA to add a feature to support a new feed in the ETL layer, in the last sprint planning, and have been working on it for a few days. This involves changes to the ETL code, the database DDL and some hibernate OEM entity changes.

As you work on the feature you have some questions for a BA, about the requirements and acceptance tests. You will have a Teams call with BA to update 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.

Then you will get a notification asking you to review a PR (pull-request) for a feature 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. 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 will 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.

If the feature is complete you'll 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.