We use cookies — so the site works and to count visits. By pressing "Got it" you also allow Webvisor session recording. Details and how to opt out
Russia
KHD Architect-Analyst / Lead Architect
4 hours ago
Contacts
Reach out directly about this role
Details
Grade
Senior
Experience
from 5 years
Work Format
Remote
Employment
Full-time
Average salary for this role
By country
431,922RUBper month
330,789615,829
country: Russia
A cover letter in a minute
AI writes it from your resume. You only have to send it.
Description
Client: Bank
Employment: Full-time
Location: Russian Federation
Citizenship: Russian Federation
Work schedule: Moscow time ±2 hours
Format: Remote work
Position:
Role: KHD Architect-Analyst
Level: Senior
Required:
At least 5 years of experience in FinTech within a DWH team;
Experience managing a team of 2+ people, establishing processes within the team, training and mentoring the team;
Higher education in natural sciences, technical, or economics;
At least 3 years of experience in implementing/developing Data Warehouses and/or Data Lakes;
Deep knowledge of SQL (Oracle, PostgreSQL dialects), writing complex queries, reading PL/SQL code;
Experience in designing database objects across all layers, understanding data warehouse architecture;
Skills in describing data loading processes for the data warehouse (DWH), creating technical documentation (Source2Target, Technical Specifications, FSD);
Experience working with business stakeholders and clarifying business requirements;
Experience in approving FSD and conducting Code Reviews;
Understand the purpose of UAT and SIT;
Knowledge of principles for building regulatory reporting, understanding PD, LGD, EAD, EL;
Experience with tracking systems, specifically JIRA.
Desirable:
Experience with ETL tools, preferably Informatica Power Center.
Tasks:
Development of new data marts, refinement of existing data marts in the Bank based on business requirements as part of the Bank's transition to IFRS;
Development and implementation of an industrial database (data mart) for defaults, based on developed default criteria, including necessary attributes (e.g., default date, recovery date, default events, etc.);
Development of a data mart with historical data, certain constants for past periods;
Integration of historical data marts into current (future) processes and data flows;
Interaction with business stakeholders;
Design of target data marts (develop logical and physical structure of data marts);