SUMMARY

• 14 years of IT experience in software requirements, design, and data analysis.
• Experience in developing requirements for different types of software: databases and data warehouses, reporting systems, desktop and web applications, gateway applications.
• Extensive experience in conducting user interviews and gathering requirements, defining project vision and scope, creating project plan and identifying priorities and dependencies, developing and communicating functional and technical requirements, and managing requirements changes through the project lifecycle.
• Good in identifying, analyzing and understanding clients’ needs, in interviewing clients and asking the right questions to find out exact business requirements. Good in finding technological solutions and translating functional requirements into architectural solutions.
• Able to express ideas clearly and understandably, good at communication both with business clients and development teams.
• Excellent analytical and logical skills, ability to deal with complex information and large amounts of data, ability to structure information effectively, and present it in a simple form.
• Excellent knowledge of SQL and hands - on experience with databases, data warehouses, big data environment; data analysis, data profiling, data mining. Strong knowledge of DBMS concepts, experience with database and data warehouse design and implementation, reports design and development, data visualization and presentation.
• Working knowledge of full software development lifecycle, experience of work with different types of SDLC (Waterfall, RUP, Agile, SCRUM) and with every stage of SDLC: from initial requirements elicitation and analysis to system design, implementation, coding, testing and bug fixing, writing user documentation, system deployment, user training and support.
• Knowledge of software design methodologies such as UML, BPMN, DDD, OOP/OOD, and experience with modeling tools like MS Visio, IBM Rational Suite, ERwin.
• Experienced in preparing and conducting presentations, trainings and workshops.
• Experienced in writing technical and user documentation.
• Quick learner capable to adapt easily to new domains and technologies.

TECHNICAL SKILLS

Data analysis and manipulation: SQL, PL/SQL, Transact-SQL, PostgreSQL, Hive, MapReduce, Excel, R, Python pandas, regexp, grep

DBMS, DW and cloud platforms: Oracle, MS SQL Server, Netezza, GreenPlum, Access, Teradata, Hadoop, Azure, Spark, Bluemix

Data visualization: Tableau, Qlik View, MS Power BI

System design: MS Visio, ERwin, Rational RequisitePro, Rational Rose, Blueprint; UML, BPMN, OOP/OOD, DDD

Languages, protocols, etc.: Python, XML, JSON, HTML, UNIX, TCP/IP, HTTP, SSL, TLS

PROFESSIONAL EXPERIENCE

Confidential, Silver Spring MD

Systems Analyst

Responsibilities:

• Developed requirements for new systems and modifications of existing systems.
• Specified communication interfaces (XML, JSON)
• Created mapping between incoming and outgoing data formats (Excel).
• Created requirements for transaction processing that define how to handle different processing scenarios (successful transaction, time-out, processing error, communication error, voided and reversed transaction, etc.).
• Created requirements for transaction logging, masking, monitoring and reporting; designed internal databases for storing transaction data (Oracle).
• Investigation of fraudulent payments: analyzed transaction data to identify patterns of fraudulent activity, developed queries that can be used to identify specific patterns, provided recommendations for enhancements of our monitoring system so that in the future it can automatically detect and block these types of activities.
• Ad-hoc investigations of any issues in payments processing (delays in processing, network or application failure, missing or rejected transactions, etc.); pulled data from databases and log files and reconstructed transaction history/lifecycle by customer’s request; analyzed the data to identify the root cause of the issue.
• For repeating issues created queries that can be used by our technical support team and conducted trainings, created requirements for internal monitoring tools which would allow to resolve such issues automatically or semi-automatically.
• Reviewed existing company databases, and developed high-level DW requirements: space, availability, integration with 3rd party data sources, and expected patterns of data usage.
• Presented possible approaches to DW and ETL design: when and how often ETL will run, which data will be available in DW for users and when, how we can address modifications of the original data in the underlying OLTP systems, etc.
• Described possible strategies for phase-in implementation of DW; provided recommendations on choice of DW platform and ETL tools based on company’s development practices and expected data usage; provided rough estimates of work effort for different options.

Environment: Oracle, XML, XSD, JSON, Python, QlikView, Excel, Visio, UNIX, Solaris, TCP/IP, HTTP, SSL, TLS, Jira, PCI DSS, EMV

Confidential, Vienna VA

Senior Data Warehouse Analyst

Responsibilities:

• Gathered, analyzed, documented and maintained system and data requirements for Enterprise Data Warehouse. Consolidated requirements received from different business departments to eliminate duplicates and resolve discrepancies.
• Reviewed project lifecycle’s artifacts produced by other teams: data profiling results, logical and physical data models, and source-to-target mapping to ensure they meet the requirements. Established change control process for requirements and other related artifacts.
• Provided analytical support for all project participants (business users, data stewards, data analysts/profilers, logical and physical data modelers, developers, testers) by communicating and clarifying system and data requirements, business rules, and DW architecture.
• Worked with data stewards, data modelers, and ETL developers on developing data quality approaches and rules for resolving data issues (how to address missing dates in data loads, errors in data and data fixes, historical records and approaches to storing temporary data in DW).
• Worked with BI analysts on identifying requirements for data access layer, data marts, dashboards, customized views, reports, and ensuring data requirements are sufficient.
• Worked with Master Data Management (MDM) team on developing strategies for data cleansing and reconciliation, and establishing processes for resolving data issues.

Environment: Blueprint, ERwin, Teradata, DB2, VSAM files, COBOL, MS SQL Server, Access, Excel, Informatica (Power Center, Metadata Manager, Data Quality, Mater Data Management), ITIL

Confidential, Rockville MD

Business Analyst / Data Analyst

Responsibilities:

• Domain knowledge: Obtained and maintained knowledge of US Capital Market, and SEC and SRO/ Confidential regulatory rules. Understood formats and meaning of the data provided by different vendors: securities exchanges (NASDAQ, BSX, PSX, NYSE, Arca, AMEX, Direct Edge), quotation facilities (ADF, Pink Sheets, OTCBB), brokerage firms and ATS/ECN order reporting (OATS), trade reporting (TRF, ADF, ORF), and market data consolidators (SIPs, ISG, etc.).
• ETL requirements and data formats: Worked with data providers on developing and agreeing formats and interfaces for data submission. Developed schedules for data load and data consumption, and data synchronization between different systems. Specified requirements and designed applications for data ingestion and transformation (ETL).
• Logical data model: Responsible for defining the logical Market Data Model (objects, relationships, meaning and interpretation of the data) and communicating it to other team members. Documented the data model, data requirements, data relationships, data flow diagrams, use cases, and data samples.
• Physical data model: Actively participated in defining DW physical design by working with data architects and DBAs and providing information about business rules related to the data and expected patterns of data usage (for example what are dependencies/hierarchy between different data objects, by which attributes they are related and in what combinations - join, union, minus, subquery - they may be used together based on the business meaning of the data, what additional restrictions may be added to “where” clause for optimizing performance without losing related data). This information was used to define data loading rules, partitioning, distribution, indexing, etc.
• Trainings: Developed training materials and conducted educational sessions for new staff, business analysts, data analysts, developers and testers to help them understand the DW architecture, the data model, relationships between objects, and technical aspects of data usage like query optimization based on existing data design, partitioning, indexing, etc.
• Helping data consumers: Worked with consumers of the market data (application analysts and developers, business and financial analysts) to identify their needs, understand their desired usage of the data, explained them meaning and formats of the stored data, and provided recommendations on optimal usage of the data.
• Optimization of data usage: Reviewed business logic of applications using DW data to ensure that data usage and interpretation are correct and efficient (join criteria are correct, all needed objects are used, we don’t miss any data, filters are meaningful and optimal, all required data is co-located, etc.). Sometimes, if requested by developers or DBAs, did code review.
• Automation: Analyzed usage of the data by different applications in order to identify parts that are common for them and so can be automated once and delivered as a common functionality. Developed requirements for such common functionality and worked with developers and testers on implementation; conducted UAT and data verification.
• Change management: Participated in CCB (Change Control Board) and in release planning sessions, performed impact assessment for new initiatives, enhancements, and modifications: identified required changes in the DW and related applications, estimated development effort; helped data consumers in analyzing impact for their applications.
• Ad-hoc data analysis: Performed data analysis, wrote ad-hoc queries, analyzed data anomalies, investigated, reconstructed and analyzed events that happened on the securities market, reconstructed order lifecycle (Order Lifecycle Assembly, OLA) and related trade reports; documentation, visualization and presentation of the data analysis results.
• Data quality: Created requirements for automated data quality monitoring system and participated in development of the pilot version. Helped technical support team in identifying possible data quality problems, their source, scope, impact on data consumers, and ways to resolve them; worked with data providers on fixing the issues, helped technical team in developing requirements for data fixes, and in post-fix verification.

Environment: Netezza, GreenPlum, Hadoop, Hive, Oracle, SQL Server, Excel, Visio, SAS, UNIX, shell, Python, StarTeam, SVN, Jira

Confidential

Lead Business Analyst

Responsibilities:

• Developed requirements for system enhancements and new features. Worked with customers (banks’ financial specialists, accountants, and technical specialists responsible for developing financial products) on identifying requirements for new products and features, created functional requirements for new functionality; agreed requirements with the customers.
• Monitored changes in banking law and analyzed if such changes may require corresponding changes in our software.
• Presented business requirements to architects and developers, participated in system design discussions, and reviewed architecture/design documents to ensure that the architecture met functional requirements.
• Created high-level project plans and effort estimates.
• For complex projects, created high-level test plans and reviewed detailed test plans created by testers to make sure all requirements are covered; conducted user acceptance testing.
• Developed and maintained user documentation.
• Prepared and conducted presentations of new products and features for our clients and technical support teams.
• Developed educational materials and quizzes, provided user trainings and workshops; was awarded “The Best Company Trainer” for the year 2007-2008.
• Improved existing system by studying current practices, identifying trends, forecasting future changes in business requirements, and suggesting enhancements.
• Identified problems and inefficiencies in current work process and developed recommendations and procedures for improvement.
• Analyzed the new banking law, identified necessary changes in the system and prioritized them, developed requirements specification.
• Prepared an official announcement of the planned changes for our bank clients with a questionnaire covering open problems and requirements that were disputable or not clear; analyzed clients’ feedback. Led a seminar for client banks (over 100 participants) with discussion of the planned changes for credit subsystems.
• Discussed changes with our architects and developers, participated in system design.
• Communicated with analysts of other modules of CFT-Bank system (system core, general ledger, checking, reporting, etc.) to understand mutual impact and coordinate the changes.
• Supervised projects implementation, provided consultations for developers and testers.
• Prepared a high-level test plan and reviewed detailed test plans and test cases. Conducted UAT.
• Developed and documented technology for transition from the old version of the system to the new one (which operations shall be performed in the system and in what sequence, and how these operations will be reflected in bank’s accounting).
• Conducted a series of workshops for our bank clients presenting and explaining the changes, new features, and transition procedure (about 200 participants); conducted trainings for our customer support team.
• Communicated with clients on critical issues, answered questions and provided consultations on transition procedure and the possible technologies of work for the new version of the system.
• Solved critical problems related to the last minute additional changes in the law introduces less than a week before the transition by developing a technological solution that made possible to resolve the issue.
• Provided on-call support during the transition period for difficult questions and critical situations.

Confidential

Project Lead, Business Analyst, Database Developer

Responsibilities:

• Gathered requirements by discussing desired system functionality with the client and studying the company business; created mock-up screens and reviewed them with customers.
• Designed user interface, defined business logic, designed database structure.Implemented database, wrote stored procedures and triggers in Transact-SQL; implemented reports (Excel).
• Participated in system testing, deployment, and user training.
• Provided system support and troubleshooting.

Environment: MS SQL 2000, Delphi 6, ADO, Excel

Confidential

Programmer Analyst

Responsibilities:

• Gathered requirements by studying current business practices and interviewing users.
• Designed and implemented databases, created triggers, stored procedures, reports.
• Designed and developed user applications (Delphi) and reporting systems (Access, Excel, VBA).
• Tested applications, deployed, prepared user documentation, provided user training and support.