Software Engineer

Job Title: Specialty Software Engineer Duration: 24 Months Contract Location: Charlotte, NC – 28202 – Hybrid Role Interview process: 2 hours in person interview, string of multiple technical one on ones Required Qualifications: This position is for a software developer to work on applications and enhancements to support regulatory reporting described in the software stack below. Area of Job Within the Company: The role is within the CCAR team of the broader Capital Markets Risk Technology (CMRT) group. CMRT works with its business partners to identify, measure, aggregate and report firm-wide market risk. The CCAR team is responsible for building and maintaining automated tools to support enterprise and regulatory reporting requirements on Comprehensive Capital Analysis and Review (CCAR) – both market risk and counterparty credit risk, Risk Not in Model (RNiM), and Private Equity Reporting Tool (PERT). Part of the group responsible for the risk simulation platform as it currently exists while a new version is built and stood up on a 2–3-year timeframe. This team works more on the reporting side of the group. It is responsible for reporting to the Fed and less on the simulation platform. Has ownership of the Comprehensive Capital Analysis and Review (CCAR) part of the process. Currently have SSRS in the environment but want to phase it out. Looking for a Java developer with decent Web UI and SQL to go with it. Position is needed to scale up in support of the doubling and tripling of the trading population that the risk simulation project is addressing. Should be capable of acting as an individual contributor. Able to perform according to a team goal rather than an individual goal, willing to jump in and help as needed. Daily scrum calls in the morning. Weekly cadence to review business needs, work with business stakeholders together. Quarterly and Monthly ritual retrospectives. Do design reviews and code reviews, unit testing. No assigned QA’s, so everyone on the team acts as a QA. Everyone on the team should be able to act in all capacities across design, coding, and testing in the lifecycle. Reporting happens quarterly and a different set is sent annually. Internally support lighter CCAR tests ad hoc and then according to a monthly reporting cycle. Software Stack : The CCAR applications built and maintained by this group utilize technologies including core Java, Angular, RESTful web services, SQL Server, Autosys, etc. The developer will work in a team to create new risk processes, and to re-factor, and in some cases completely re-architect and replace, large components of the existing application. The successful candidate will be expected to: Have advanced Object-Oriented development skills to create Java code that can be easily maintained and extended to meet the growing demands. Have solid RESTful web services and web UI development skills to create UIs. For new development, the developer will be expected to work with business partners as well as upcoming regulatory guidelines to understand the needs and requirements and to analyze and design the necessary software. Design solutions that meet the business needs encompassing the full technology stack from backend database design, front end views and back-end services and working with other developers to meet the requirements. The developer is expected to work as an individual contributor and coordinate with cross functional engineers to deliver functional enhancements and platform improvements Assures quality, maintainability, and extensibility for supported systems and risk applications. Key technical resource on team building sophisticated and complex risk applications BS/BA in Computer Science, Engineering, or related discipline Strong analytical skills with high attention to detail and accuracy Good verbal, written, and interpersonal communication skills Top Skills 5+ years of Java 3+ years of React/Angular 2+ years of SQL – 2 – 4 Years Agile/Jira – 1 – 2 Years Java Developer - 4 - 6 Years React, Angular or NodeJS – 2 – 4 Years All your information will be kept confidential according to EEO guidelines.