Compensation:
$50/hr to $70/hr.
Exact compensation may vary based on several factors, including skills, experience, and education.
Benefit packages for this role will start on the 31st day of employment and include medical, dental, and vision insurance, as well as HSA, FSA, and DCFSA account options, and 401k retirement account access with employer matching. Employees in this role are also entitled to paid sick leave and/or other paid time off as provided by applicable law.
Here is a little more information about our client’s .Net/Angular Developer that is operating REMOTE (EST Hours).
Local to: Charlotte, NC or Willing to relo to Charlotte for Duration of Contract
Duration: 18 Month Contract
MUST HAVES:
7+ years experience with dotnet WebAPI development (C#) based on industry best practices with REST
Strong experience with Angular front end development Layered architectures (will be taught & presented)
Adherence to code quality standards (including code scanning, security scanning, unit test coverage, etc)
Understanding of Excel macros and VBA code
Financial Industry Experience
Job Description:
Assist in taking existing spreadsheets that have embedded VBA code and recoding them completely using a modern dotnet tech stack. This will include dotnet 8 WebApis that interact with existing sql databases, other REST apis, GraphQL Apis, etc Assist in taking existing spreadsheets that have embedded VBA code and wrapping them with a .net 4.8 framework restful endpoint that utilizes COM to interact with the excel macros directly. The APIs should be written in a layered way that would allow for us replace the spreadsheet with code and port to dotnet 8 in the future. Assist in taking existing spreadsheets that call external dotnet code (framework currently) to run existing models and wrap them in dotnet (framework or core depending on dependencies) REST apis The purpose of the Wrapper API is to support existing model functionality, specifically those functions currently handled by Excel VBA and older .NET Framework implementations. Given the complexity of these functions, and the expected tight MVP timeline, the proposed solution is to create a wrapper API around these functions, thus minimizing exposure to older technology. The API will be developed using .NET 8 and will have a dependency on Office.Interop. API Deployment needs to happen on a Windows OS. The choice between using a VM or a Container for the underlying infrastructure will depend on whether Office.Interop is supported. Further research is needed to make this determination. As this API is a unique / one off requirement, it's important to think more on CI/CD Pipeline support (overall from time / effort perspective).
