Improving engineers’ productivity and removing all pain points by automating nearly all day-to-day flows. Built dozens of pipelines for CI/CD with GitHub, Jenkins, Spinnaker, Kubernetes, Terraform, Atlantis and tooling that I built myself mainly using typescript.

— Significantly improved the overall engineering department efficiency by building a system that creates a fully-functional disposable environments with all microservices and dependencies required for the Parsable ecosystem in about ten minutes using Slack bot for user interaction.

— Saved months of engineers’ work by creating automation that generates an initial version of a fully functional microservice with code and project settings in GitHub, CI flows in Jenkins, and CD pipelines in Spinnaker, automatically deploying the first version to the staging and production environments.

— Helped engineers save, on average, one to five hours for each release by creating a Jenkins pipeline library framework that automates all mundane release tasks such as bumping the project version, preparing a build, publishing packages, and docker images, issuing Jira tickets, creating GitHub releases with notes and more.

— Reduced build times for all legacy services on average by more than 30% by refactoring Jenkins pipelines, improving the overall readability and maintainability of the system.

— Stabilized, refactored, and sped up nightly regression automation by ~20% using smarter job parallelizations and previous builds statistics utilizing Kubernetes infrastructure with Jenkins.

— Promptly resolving all help requests from engineers, saving their valuable time

— Maintaining Jenkins and Spinnaker systems

After the company reorganization, I was made a lead of the backend team.

So today, my role includes:

— leading the whole cycle of feature development: communicating high-level feature requests from the PMs to the team, designing architecture and infrastructure, planning, setting priorities, development, code reviews, deployment, releases.

— troubleshooting of the issues, reviewing incidents;

I still write code but mostly infrastructure

I've moved to San-Francisco and started leading at first four and then five engineers in a Vendor Services team.

As a team lead, I have been working closely with PMs to achieve our business goals by providing necessary information about the system, potential problems, and breaking down significant product initiatives into small achievable tasks and distributed them to my team.

Besides product initiatives:

— I made a local proxy for our frontend engineers to be able to develop UI locally with QA backend which significantly saved nerves and time for them;

— I made a presentation about database indexes to show engineers basics about indexes in general and how to deal with them;

— To move to CI/CD, I worked on overall development and deployment process improvements from the organizational side as well as from automation. I have prepared deployment scripts, Jenkins jobs, Jira workflows, and filters; I have thoroughly planned, documented, and communicated transition to a new process to everyone, and it went smoothly;

— To move to CI/CD, I wrote a testing framework with Java, cucumber, rest-assured, and selenium with selenide library to reanimate our QA automation and be able to run our regression under 30 minutes instead of 2 days — engineers are actively contributing there as of now.