Uladzislau Muraveika Email & Phone Number

Support, development, monitoring of the hosted nodes for Filecoin users as part of Glif.io team.Nodes have load around 60 million request per day or 700 op/s.Our goal is to provide free for all RPC nodes service 24/7/365.Diving into the following topics:* Lotus node client nodes as RPC backend* terraform - all the stuff around k8s and AWS, writing custom modules to keep code DRY * deep dive into AWS - EKS, EC2, Route53* dived in containers stack - used best practices in creation containers - made them as small as possible, used dive tool to check layers and hadolint linter to don't make silly mistakes * K8S - ingresses(Kong), services, CRDs, pvc, how to cook stateful sets properly * helm charts - creation/updates, tried use community charts as examples * monitoring stack - Prometheus => Grafana, created custom dashboards

Belarus

There were two projects: 1. Improvement of Jenkins pipelines connected with software quality metrics like reports from static analysis tools, compiler warnings, visualized them in Splunk. The team was working with various data sources and created parsers.2. Splunk dashboards automated testing.The customer has engaged the team to help with the problem of testing Splunk dashboards. The main problem was that product teams found UI defects after rollout. This idea has assisted the Splunk UI team find and effortlessly fix bugs in the test environment and prevent further support tickets.Solution (more details in attachment):* Proof of concept with Page Object Model approach was implemented and shown to the customer team.* I have analyzed use cases, found out that elements are the same on all dashboards, presented the idea to use a template engine for tests.* Used JSON-formatted files to describe input data as the source for template files.* Implemented continuous integration mechanism for dashboards developers. This solution has been checking every change with tests.* Used Junit and Html reports for tests, implemented screenshots on failure feature. Additionally, screenshot functionality has been added to the Html report.* Added customized Teams notification and reports publishing at the end of Jenkins test run.

Minsk

Bench time with self-learning about:* Go programming language - used "A tour of go" - https://tour.golang.org/list* Terraform - read awesome "Terraform: Up & Running: Writing Infrastructure as Code" by Yevgeniy Brikman * learned basics of Kubernetes

Belarus, Minsk

The main field of work was the writting of Jenkins pipelines using Groovy language.I had deep dive in Groovy and Jenkins internals. I used shared libraries as advanced technic and good example DRY principle.Additionally, I had a lot of fun with fixing and understanding of Non-Serializable problems in groovy code.

Minsk, Belarus

I joined Epam system engineering lab to get new skills and start working as a system engineer.I've learned next items most of them on beginner level:• Web-servers (Nginx and apache) - setup of virtual host and forward-proxy• Java from an application performance perspective - basics of java virtual machine what is garbage collector and its types, what is a heap, types of memory.• docker - how to create an image, how to deploy • Continuous integration / Continuous deployment (delivery) - basics from jobs to pipelines: Tools: - Jenkins as the main integration tool - docker as containerization tool - nexus as artifact proxy and artifact storage both for jars and docker images - sonar - just basics usage• Python - beginner level, wrote a small script for automation• Ansible - basics usage - playbooks, roles, variables• Basics of Monitoring with Zabbix - graphs, metrics, alerts

Belarus, Minsk

As ops:• good knowledge of scripting with bash and python• using complex SQL-queries• deal with end to end PGP-encryption setup• key person in customers file processing questions• support and development all file processing infrastructure for the customer (more than 400 of scenarios)

Belarus, Minsk

As tester:• participated in few exotic types of testing like ETL testing, data migration, data center migration, failover testing(crashing parts of the system), compressing testing(two non-equal system use one dataset)• have practical experience in requirements analysis; creating documentation such as test cases, test plans, checklists; communication with customer and vendor, test result reporting, participating in test planning, quality reports creation;• have taken participation in adaptation process for newcomers: test-tasks preparation, execution control & support• lead demos for customers• have paid bounties for bugs in bug bounty programs • very proactive and always caring about end-users first of all

Belarus, Minsk

Project:The main idea of the project - implementation and stabilization of new billing solution for the major telecom operator. This system has a complex architecture and business logic. The project is divided into functional areas, components, and business processes.Participation:- Functional testing;- Defects validation and regression testing;- Mentoring and adaptation of newcomers;- Calendar planning of functional testing in one functional area;- Test documentation creation (Acceptance sheet, test survey, test cases, UAT, etc.), test scope reconciliation;- Test model creation, it's quality control and reconciliation with the customer;- Regular Quality reports creation;- Consulting of the customer (user guide creation);- Knowledge transfer to the customer’s team;- Administration of the comparative test (test methodology updating, report creation, data analysis);- Communication with customers and vendors for resolving difficult questions' purposes.