Job Title: Cloud Engineer
Job Duration: 8 months
Location: Charlotte, NC (Hybrid)Job Description -
Is this a remote position? If not, what Client locations can a resource work and how many days a week will they be required to work onsite?- Either remote or HUB (preferred Charlotte, NC - 3 days a week in office)
Can you please provide a summary of the project/initiatives which describes what’s being done?AFE 44250 - FMR Mainframe Modernization Initiative
The FMR (Financial Management & Regulatory Reporting) platform is a mission‑critical Client system that supports core financial close, management reporting, and multiple regulatory submissions (including Federal Reserve and other supervisory reporting). The platform processes and transforms data from a large and diverse set of upstream systems and serves as a foundational component of the Client Finance and Treasury reporting ecosystem
The application is currently hosted on a legacy mainframe architecture, which introduces increasing operational, cost, and people risk, including limited agility, rising run costs, and concentration of critical knowledge in a small set of specialized resources. To address these risks, FMR is part of an active enterprise mainframe modernization program within the Finance organization, focused on a controlled, auditable migration to cloud‑native platforms, aligning with Finance Data Strategy on AWS
As part of this initiative, FMR workloads are being migrated to AWS, with Databricks and Snowflake serving as the core data and analytics platforms. The modernization effort includes re‑architecting data ingestion, transformation, and reporting pipelines; establishing cloud‑native security, encryption, and PII controls; and aligning the solution with ISS, Data Governance, and Risk Information Management (RIM) standards. The program targets a full mainframe decommissioning over the next ~15 months, while ensuring uninterrupted financial close and regulatory reporting throughout the transition.
The initial phases of the program require deep domain expertise, close collaboration with onshore stakeholders, and hands‑on technical leadership to navigate regulatory dependencies, data integrity concerns, and complex downstream integrations. As the cloud platform stabilizes and operating procedures mature, steady‑state production support and ongoing operations are planned to transition offshore in Q4, aligning with the Bank’s long‑term cost optimization, scalability, and global delivery operating model objectives. This phased transition ensures risk is reduced early while enabling a sustainable and cost‑effective support model post‑modernization.
What are the top 5-10 responsibilities for this position? (Please be detailed as to what the candidate is expected to do or complete on a daily basis)Scope of work includes:
· Performing deep technical analysis of the existing mainframe environment, including the use of GenAI‑based tooling for code and data assessment
· Designing the target‑state architecture using AWS, Databricks, and Snowflake services
· Driving initial implementation activities, including:
o Foundational EDM data requirements
o ISS, PII, and security controls
o Encryption and compliance standards
o CI/CD pipeline setup
o Critical downstream system integrations
This work requires continuous, hands‑on collaboration with multiple internal teams, including the FMR application team, ISS, Security, and Data Governance, to address complex design, compliance, and security dependencies within tight regulatory and delivery timelines.
What skills/technologies are required (please include the number of years of experience required)? ETL - 7 years
- SQL / PLSQL - 7 years
- Database - 7 years
- BIG DATA - 4 years
- AWS Data Engineering - 2 years
- AWS Glue - 2 years
- AWS EMR - 2 years
- PySpark / Python - 2 years
- Databricks - 2 years
- Snowflake - 2 years
- AWS Services (S3, EFS, Lambda, SNS, EFS, DMS, DataSync) - 2 years
- Mainframe migration project - 2 years
- What skills/attributes are preferred (these are a desired, not required)?
- GenAI developer tools like GitHub Copilot, Claude, etc.,
- What does the interview process look like?
o How many rounds? - 2 rounds - Video, phone, or in person? - Video
- How technical will the interviews be? - The interviews will be highly technical and role‑appropriate. They will focus on assessing hands‑on experience, architectural thinking, and practical problem‑solving rather than deep theoretical questions
