Vista previa generada por IA
...
...
Discover your future at Citi Working at Citi is far more than just a job. A career with us means joining a team of more than 230,000 dedicated people from around the globe. At Citi, you’ll have the opportunity to grow your career, give back to your community and make a real impact.
Job Overview
Job Overview Role Summary: We are looking for a technical problem-solver to join our Global Regulatory Reporting Analytics Team. In this role, you will act as the \"Gatekeeper\" of our regulatory data. You will be responsible for two critical functions: (1) Proactive Impact Analysis, where you assess how upstream system changes (product updates, migration, schema changes) will affect our regulatory reports, and (2) Reactive Root Cause Analysis, where you investigate data anomalies reported by the reporting team. You will sit at the intersection of Technology and Finance. You must be fluent in SQL to dig into the data and fluent in Financial Products to understand the business context. ________________________________________
Key Responsibilities
Key Responsibilities 1. Upstream Change Impact Analysis (The \"Shield\") • Monitor and review upcoming changes in upstream source systems (e.g., changes to General Ledger, Data Warehouse, Product Processors, or Reference Data). • Analyze the \"Blast Radius\" of these changes: Use data mapping files and SQL to determine if an upstream attribute change (addition/removal/logic change) impacts specific regulatory report lines. • Conduct \"content analysis\" to verify if the nature of the data is changing, even if the schema remains the same. 2. Incident Triage & Root Cause Analysis (The \"Detective\") • Investigate \"perceived data issues\" raised by the Regulatory Reporting team. • Execute complex SQL queries to trace data lineage back to the source. • Determine the verdict: Is this a true upstream Data Quality (DQ) issue, a logic gap in our transformation layer, or a valid business event? • Prevent false alarms from reaching the technology development team by filtering out non-issues. 3. Testing Strategy & Requirements Management • Translate findings into actionable JIRA tickets. Clearly define: o The Change: What is changing upstream? o The Impact: Which report cells are affected? o The Test Plan: How exactly should this be validated? • Define test cases for User Acceptance Testing (UAT) to ensure upstream changes do not cause regression in reporting. 4. Communication & Stakeholder Management • Act as the translator between the Reporting Team (who speak in \"Reg Rules\") and the Technology Team (who speak in \"Code/Schema\