.Net Cloud Software Engineer

Skills

Working knowledge of Azure development and workflows Proficiency creating applications and features in C# Exposure to event driven architecture/paradigms Understanding of asynchronous distributed data flows Working knowledge of testing best practices (unit automated acceptance) Familiarity with cloud-based state storage technologies Tech: Azure Kafka Cosmos DB and/or Azure Durable Entities

Description

Project Background: Client is integrating our homegrown TMS, Navisphere, with Oracle’s Accounting Hub (AHCS) and Financials Cloud Services in alignment with our long-term future state objective of implementing Cloud Financials Trade Accounts Receivable and Accounts Payable sub-ledgers.

The Accounting Hub will provide transactional sub-ledgers which will feed the Oracle GL.

We’re leveraging Oracles Autonomous Datawarehouse to build the Financial Datawarehouse (FDW) to provide finance reporting to the organization.



The custom integration layer between Navisphere and AHCS/FDW, Accounting Transformation Layer (ATL), is being built in Azure.

The ATL cleans, aggregates, and transforms the transactional finance data from Navisphere into a format that the Oracle can process.



The project has rollouts scheduled on July 1 and Aug 1 for different regions.

We are currently entering our second phase of system integration testing and are preparing for UAT in May/June.



Current Need: There is additional work required to complete the ATL that is pushing us to look for external staffing.

The work would be fully encompassed in the Azure ATL layer, not in Navisphere or Oracle products.



About the Team:

We currently have a CHR development team dedicated to the project (5 engineers, 2 EPM/BA, 1 architect).

Candidates would receive direction from the arch and EMPs. We operate in an agile environment on two-week sprint cycles.

All work associated to the project is deployed using Azure DevOps pipelines backed by GitHub.

Responsibilities

• Mapping Navisphere data (financial and operational) to FDW contract in the ATL following established patterns
• Assist in upgrading the ATL’s state storage from Durable Entities to Cosmos
• Partner to build out the ability to reverse and repost transactions between the ATL and Oracle (includes providing a mechanism for modifying the state of previously processed transactions)
• Write integrations between established Kafka topics and ATL (i.e. exchange rates, MDM data, etc.)
• Close the gaps in monitoring and logging across kafka producers/consumers and the Azure function apps that make up the ATL
• Partner to establish reports for SOX controls