Dmitrii Voitovich Email & Phone Number

Tallinn, Harjumaa, Estonia

• Writing good new Go code• Converting existing bad Go code into good Go code

Tallinn, Harjumaa, Estonia

• Implementing and re-implementing features with Go• Doing good code reviews• Optimizing services performance• Setting up service monitoring with Grafana• Managing test and production infrastructure with Ansible• Automating CI/CD pipelines with GitHub Actions• Restricting code standards with linters and vulnerability analyzers• Checking logs and setting up monitoring alerts with Prometheus

Tallinn, Harjumaa, Estonia

• Leading integration with Visa Token Service• Making Apple and Google Pay projects real• Managing the healty team of happy developers• Act as a systems analyst when necessary• Making qualitative code reviews, one-to-ones and performance reviews• Composing and moving tasks asross the boards• Writing hundreds lines of code

Tallinn, Estonia

• Adopted GitHub flow and CI process• Adopted "PR and code review as a must" policy• Convinced teammates to write lots of tests• Introduced static code analysers• Introduced automated API documentation with SwaggerHub• Introduced Kubernetes• Migrated services to Azure Kubernetes Service (set up with Terraform)• Writing good Golang code• Juggling tasks in Jira• Drinking coffee, joking about weather

Tallinn, Estonia

• Golang development• Kubernetes migration• Gitlab CI automation

Tallinn, Estonia

• Leading QA automation• Selenium testing• CI/CD integration• Docker containerisation• Java development

Tallinn, Estonia

Have been mostly focused on dev and test environments. Started from lasting for 3 hours unstable Jenkins builds we've made over the whole process with Travis and Docker. The build process was made the way, that project could now be run the same way on the developer machine and on travis, that simplified maintainability and made the code clear. 20 running in parallel travis containers allowed us to speed up getting a feedback dramatically: for unit tests developers now get results after half of an hour, for system tests it takes from 1 to 1.5 hours, but up to 5 developers can have their PR under testing simultaneously. The Allure reporting system, that we've integrated, allowed them to see all the system information regarding each test: system and mysql query logs, requests and for selenium tests video of a running browser. We also got rid of rerunning tests in case of fail process, that forced people to write them carefully and increased stability. For code quality we applied code reviews of PRs and Scrutinizer. Also to add some visualisation we drew test statistics charts on a screen in dev room to see the progress and add some gamification.

Saint Petersburg, Russian Federation

The company had a need of automated tests, so I was invited to build it into existing manual tested release process. A selenium testing framework based on PHPUnit, Yandex Allure report system, Selenium Facebook Web Driver and Page Object pattern was developed by me. Then we collected most widely used user scenarios, covered them by system tests and built the CI process with TeamCity. It allowed developers to add new tests easily, was watching releases and notifying responsible people in case of troubles. All the legacy unit tests were also migrated to new architecture and integrated into the process. We’ve lectured a couple of times to bring clarity and help other developers with TDD and understanding of a framework and benefits it brings. And we also had weakly pair-programming events for writing tests. Most of my time I was spending maintaining, improving and speeding up the tests, the framework and the CI process itself.

Rostov-On-Don, Rostov Region, Russian Federation

I joined a legacy project, written in pure PHP, with main goal to increase code maintainability. Started from organizing testing procedure we built a cluster of virtual servers and run production environment, Jenkins and Selenium Grid there. That allowed to develop a fast set of system tests and to start refactoring of the system. We implemented coding standards and code review procedure, unit testing, CI and rewritten almost all the code to ZF2 and Doctrine2. I was also involved into regular development, where the most challenging task was GEO based routing mechanism with POI searching support.

Rostov-On-Don, Russian Federation

Rostov-On-Don, Russian Federation

I started as a part of QA team, performing manual, automated and stress testing for high-loaded distributed ad network, but after half of a year was promoted to Web developer and mostly focused on bug fixes and implementation of custom features for client needs. Email-based customer technical support, development of documentation and technical specifications, designing architecture and evaluation of tasks were also a significant part of my responsibilities.

Taganrog, Rostov Region, Russian Federation

Worked for half of a year as a junior sysop for the university I studied at. Was maintaining soft- and hard-ware of approximately 50 PCs and part of a LAN, helping with all IT-related tasks and consulting users as well.