What are the responsibilities and job description for the Data Business Analyst(Payments, Sanctions/Compliance)-Local to FL position at Lorvin Technologies?
Job Details
Summary:
Payments: Candidates should have a solid understanding of payment products. While they don t need to master all products, familiarity with at least one, such as real-time payments (e.g., Zelle) or wires, is essential. They should be able to explain the end-to-end process, including how transactions work, how settlements occur, the types of checks involved, and the message types used, such as SWIFT or ISO standards. A detailed understanding of these aspects will significantly improve their chances of clearing the interview.
- Sanctions/Compliance Knowledge:
- Candidates must demonstrate experience with sanctions/Compliance, explaining the processes for transactional and static screening, the lists or rules involved, and the screening and disposition workflows.
- A deeper understanding is required, including how transactions are monitored, rules applied, and stakeholder involvement.
- Superficial answers (e.g., broad statements about sanctions) are insufficient; candidates should provide detailed insights into the workings of sanctions.
- SQL Proficiency:
- Candidates should have the ability to write moderately complex SQL queries, including tasks such as:
- Handling joins.
- Finding maximum or second-highest transaction values.
- Grouping transactions by customer ID or account number.
- While not expected to handle extremely lengthy or advanced queries, they should demonstrate competence in handling queries with some complexity.
- Data Analysis Experience:
- Candidates must have experience in data-related roles, including:
- Performing data mapping.
- Conducting gap analysis.
- Managing various data activities.
- candidate s involvement and depth of experience in these areas.
Evaluation and Rating: Please share the detailed feedback and rating on the key skills like sanctions, SQL, and data analysis, with explanations for the ratings (e.g., 3/5 in SQL due to moderate complexity handling).
