Project overview: Company builds DWH for reporting service. Responsibilities: • Build Data Lake/DWH from scratch on Redshift. • Establish data pipelines. • Build model on DBT. • Investigate/migrate necessary data. • Build/consult Tableau reports. Tools and environment: Postgres, MS SQL, Tableau. Technologies: Redshift, DBT, Python, Fivetran. Teamwork: 4 people.

Project overview: Company provides some of microcredit services. Responsibilities: • DWH expansion and support. • Establish data pipeline through Talend and Python. • ELT process optimization. • Creating/enhancement reports on Tableau. • Bug fixing. • Reviewing of teammates’ code before production releases. Tools and environment: Talend, Tableau. Technologies: MySQL, Python.

Project overview: BSS is the services division of SH, providing world-class shared services, including, technical systems and expertise, legal, accounting and human resources.SR provides actionable investment recommendations and research for individuals self-managing their portfolios. Responsibilities: • DWH expansion and support. • Establish data pipeline through Fivetran and Python. • ELT process optimization. • Reducing data copies. • Creating/enhancement reports on Looker/Tableau. • Bug fixing. • Reviewing of teammates’ code before production releases. • Week on-call duty: infrastructure troubleshooting, client support. Tools and environment: Snowflake, Looker, Tableau, RunDeck, SalesForce, VictorOPS. Technologies: SnowSQL, Python, Fivetran. Teamwork: 4 people.

Project overview: For more than 80 years, Lifetouch has been the professional photography company of choice for schools and families. Built on the tradition of “Picture Day”, Lifetouch captures smiling faces from preschool through high school graduation, as well as sports, special events, seniors and yearbooks; and also serves customers in JCPenney Portrait Studios and Church communities. Lifetouch is also a part of the Shutterfly family of brands. Responsibilities: • DWH expansion and support. • Designing and developing SSIS packages, stored procedures, tables, views. • Implementing best practices to maintain optimal performance. • Building efficient SSIS packages for processing the data. • Implementing error data capturing and reporting. • Creating reports on SSRS and Power BI. • Bug fixing. • Partial ETL migration from SSIS to Python. Tools and environment: MS SQL Server 2016, MS Visual Studio 2019, MarketingCloud (SalesForce). Technologies: C#, TSQL, SSIS, SSRS, Power BI, Python. Teamwork: 4 people.

Project overview: MyAlerts is a personalized alerting tool that helps you to track nearly any e-commerce page to search/track items online. It is considered to be a personal shopping assistant that will suggest you the best time to buy anything using intelligent mechanisms for monitoring prices for millions of products at thousands of top sites such as Amazon, Best Buy, Target and etc. As a part of ETL team I was involved in the integration of data provided by vendors and worked on data migration to RedShift. Our architecture included few steps for data movement: we migrated an archived data through S3 to RedShift. It allowed to save time and money. Responsibilities: • Refining development practices for this project specifics. • Working with Technical and Data Architects on ETL and data architecture. • Developed DDL and DML scripts, stored procedures. • Developed SSIS packages for implementation of integrated data warehouse loading process. • Painstakingly working on ensuring that implemented ETL jobs optimized from performance standpoint. • Working on resolving data and ETL issues (creating data and code fixes). • Creating support documentation and keeping it up to date. Tools and environment: Microsoft SQL Server BIDS/SSMS, RedShift, AWS, Confluence, Jira, Bitbucket. Languages and Technologies: SQL, SSIS, PostgreSQL. Teamwork: 8 people

Responsibilities: • Refining development practices for this project specifics. • Working with Technical and Data Architects on ETL and data architecture. • Managing team of 6 developers. • Working with QA team on bug resolution. • Reviewing DDL and DML scripts, views and stored procedures. • Reviewing SSIS packages. • Working on performance optimization of both SSIS packages and SQL stored procedures. • Mentoring junior developers and QA specialists on database development and ETL. Tools and environment: Microsoft SQL Server BIDS/SSMS (Database Engine, Change Data Capture, Replication), Microsoft TFS, ActiveBatch, Oracle SQL Developer. Languages and Technologies: SQL, SSIS, NZ/PL SQL. Teamwork: 16 people.

Responsibilities: • Refining development practices for this project specifics. • Working with Technical and Data Architects on ETL and data architecture. • Managing team of 6 developers. • Working with QA team on bug resolution. • Reviewing DDL and DML scripts, views and stored procedures. • Reviewing SSIS packages. • Working on performance optimization of both SSIS packages and SQL stored procedures. • Mentoring junior developers and QA specialists on database development and ETL. Tools and environment: Microsoft SQL Server BIDS/SSMS (Database Engine, Change Data Capture, Replication), Microsoft TFS, ActiveBatch, Oracle SQL Developer. Languages and Technologies: SQL, SSIS, NZ/PL SQL. Teamwork: 16 people.

Project overview: The goal of the project was to replace legacy Credit and Collections systems with a new vendor solution. Since there were numerous objects in the Data Warehouse (IDW/IDM) that source data from the legacy systems, there was a need to remap them to interface with the new vendor solution. The scope of BI part of Apollo project was remediating all affected data entities as well as ETL flows on all levels of Data Warehouse solution implemented in the scope of previous (IDW/IDM) project. The biggest challenge was the fact that the only interface to interact with the new vendor solution were multiple flat files transmitted on daily basis. It worth mentioning that files were transferred independently but not as a set. As a result, taking into account the following obstacles: • Legacy Credit and Collections systems were regular OLTP systems • All other major source components of Data Warehouse Solutions are OLTP systems • There is no precise and trustworthy schedule for delivering flat files from new vendor solution – only expected timeframes required integration approach for new system was very nontrivial. The key component of designed approach was new multi-layered staging area, which helped to handle all exceptional processing cases properly. Besides that, all downstream ETL flows were remapped to new sources and revised to accommodate specificity of new system processing. As I lead of development team, I took part in defining the concept of new staging area and was responsible for establishing development practices in order to make implementation process smooth and resulted code artifacts standardized. I closely worked with both BA/DA and QA teams to make sure that defined requirements and design are implemented according to users’ expectations and with the high level of quality.

Project overview: The project aimed to creating an enterprise-level Data Warehouse system from the scratch. Resulted solution should integrate data from various departments of the company, as well as from external vendors and collection agencies in order to provide business consumers the single source of relevant and truthful data instead of endless reconciliation between multiple legacy department-specific warehouse systems. Responsibilities: • Developed DDL and DML scripts, views and stored procedures. • Developed SSIS packages for implementation of integrated data warehouse loading process. • Painstakingly working on ensuring that implemented ETL jobs optimized from performance standpoint • ETL jobs orchestration using ActiveBatch • Working on resolving data and ETL issues (creating data and code fixes) • Creating support documentation and keeping it up to date Tools and environment: MS SQL Server, Netezza Aginity, ActiveBatch, Microsoft TFS. Languages and Technologies: SQL, SSIS, SSRS, NZ/PL SQL. Teamwork: 12 people.

Project overview: The goal of this project was to create a robust application supporting all Kazakhstan’s municipal services activities: from collection of water/energy/gas/etc. consumption to billing and sophisticated reporting functionality. As a lead of backend development team, I was responsible for creating architecture of ETL process, modeling OLTP and Data Warehouse databases, as well as OLAP cubes. Responsibilities: • Architecture, design and development of OLTP systems. • ETL architecture and development. • Implementation of custom CDC engine. • Architecture, design and development of Data Warehouse. • SSRS reports development. • SSAS cubes development. • SQL query optimization. • Managing sub-team of 6 developers. Tools and Environments: SSMS, SVN, SQL Server 2005-2014, SSIS, SSRS, SSAS. Languages and Technologies: T-SQL, Delphi, MDX, XQuery. Teamwork: 48 people.

Client overview: AsiaUniversalBank (AUB) is the largest commercial bank in Kyrgyz Republic, holding about a quarter of the combined assets and deposits reported by the entire Kyrgyz banking system. Largest branch network, largest ATM & cashin network in the country in addition to a number of alternate delivery channels. Project overview: The goal of this project was to support and extend existing reporting functionality required for both operational needs and end users: Responsibilities: • ETL development using SSIS. • SSRS reports development. • SQL query optimization. • Testing and bug fixing. Tools and Environments: SSMS, SVN, SQL Server 2005, SSIS, SSRS. Languages and Technologies: T-SQL. Teamwork: 14 people.

Client overview: Altyn is the holding company, which includes the biggest in Kyrgyzstan jewelry manufactory and distribution network. Project overview: The goal of this project was to create a software platform, which will enable control and reporting for the full cycle of jewelry production – from procurement to sales to end consumers. Our team provided closely worked with business representatives to gather requirements as well as did actual coding, testing and bug fixing. Responsibilities: • Requirements gathering. • Software design and development. • Testing and bug fixing. • Technical support and maintenance. Tools and Environments: SSMS, SVN, SQL Server 2000. Languages and Technologies: T-SQL, Delphi. Teamwork: 12 people.