Artem Katashev

Staff Software Engineer

SiriusXM

Mar 2026 - Current (7 months)

Senior Software Development Engineer

Workday

Jul 2023 - Mar 2026 (2 years 9 months)

Backend Software Engineer (Band 8) at Zelta

Merative

Oct 2022 - Jul 2023 (10 months)

Backend Software Engineer (Band 8) at IBM Clinical Development

IBM

Mar 2022 - Sep 2022 (7 months)

Scala Backend Software Engineer at IBM Watson Health.

Software Engineer (Band 8) at IBM Cloud Databases

IBM

Oct 2020 - Feb 2022 (1 year 5 months)

As a Software Engineer and Site-Reliability Engineer, I worked on adding new databases and features to IBM Cloud Databases offerings and on improving and ensuring the stability of databases in Production. Achievements to mention: ● Lead development of IBM Cloud Databases for MySQL 5.7 offering from an initial prototype to GA. ● Created a plugin for MySQL 5.7 to increase its security level to the one necessary for a Cloud database. ● Fixed bugs in a MySQL-related open-source project, paying back to the community. ● Improved team standards about code quality, proposed and implemented numerous process changes to make developer experience better. ● Onboarded numerous new hires. ● Improved acceptance tests used for all databases, making them ~20

B

Backend Software Engineer

Jul 2019 - Oct 2020 (1 year 4 months)

Being a Software Developer for an AI startup that started a new project from scratch, I was mostly working on creating a Data Processing pipeline that was running on IoT devices collecting data on farms, processing it, and uploading results to storage in the Cloud. ● Created a microservices architecture and persuaded the team to use it. ● Designed and implemented almost every part of this architecture. ● Heavily optimized every application to use limited resources of IoT devices most effectively. ● Created a release tool to deploy updates to multiple IoT devices in parallel. ● Configured Jenkins for building images for ARM devices and auto-testing them. ● Configured K8s on IoT devices to auto-heal application even if connectivity was lost f

Q

Quality Engineer

Dec 2018 - Jun 2019 (7 months)

As the only Quality Engineer in the company I: ● Participated in making decisions about quality assurance strategies, orchestrators, and CI/CD tools and approaches for a brand new product. ● Participated in bringing principles of TDD and BDD to everyday developer's life. ● Participated in making design and architectural decisions for both Cloud and On-Premise teams. ● Built functional testing frameworks for On-Premise software automated testing and Cloud solution automated testing. ● Built functional test suites for this software. ● Integrated functional testing in CircleCI pipelines for Cloud software. ● Created Jenkins pipelines for automated functional testing of On-Premise software.

Senior Software QA Automation Engineer (SDET)

DINS

Nov 2017 - Dec 2018 (1 year 2 months)

As a part of a mixed Software Developers and QA Engineers team, I used Scala and Java to develop testing frameworks and automated tests for C++ and Haskell-based products. In addition to contributing to CI through automated regression testing and test documentation, I performed the following activities: ● Was leading a switch from Java to Scala and functional programming for JVM applications and Routers testing platform. ● Implemented HTTP routers using Akka-HTTP. ● Developed numerous extension libraries for testing frameworks and performant stub-servers suitable for testing high-load routers. ● Internal performance testing of HTTP and SIP services with Gatling 2 and sipp tools. ● Participated in the Software Design discussions with System

Software QA Automation Engineer (SDET)

DINS

Nov 2016 - Nov 2017 (1 year 1 month)

Senior Software QA Engineer

Genesys

Apr 2016 - Oct 2016 (7 months)

During my work in Genesys Telecommunications Laboratories I participated in three projects: two backend servers, responsible for processing and intellectual routing of VoIP calls, and an automated testing system for Genesys Cloud Solution. In the last project I was a technical lead of its local St. Petersburg team, that was a part of a bigger distributed team. My responsibilities included: ● Examination of developent builds for bugs and race conditions, investigation of their roots and tracking them in Jira. ● Preparation of a testing documentation by reviewing developers feature description documentation and determining key requirements for new features. ● Predicting possible conflicts between an old and new functionality. ● Developing aut

QA Automation Engineer

Genesys

Nov 2012 - Apr 2016 (3 years 6 months)

F

Linux System Administrator / Technical Support Engineer

FastVPS Group of Companies

Aug 2011 - Nov 2012 (1 year 4 months)

Linux System Administrator responsible for helping troubleshoot and resolve various customer issues in unix environments: ● Investigated and solved countless problems on NIX-based VPSs and dedicated servers with HTTP, Mail, DNS, XMPP and other kinds of services as well as networking and RAID systems problems. ● Developed a tool for routine task automation in Perl that solved numerous frequently occurring simple problems in a second, saving engineers' time for more complicated tasks. ● Developed a server monitoring tool in Perl that was able to perform a number of tests and present their results to an engineer in an easy readable format. This tool saved a lot of time and prevented loss of customer data on numerous occasions by detecting RAID

Technical Support Engineer (L2)

Devexperts

May 2011 - Aug 2011 (4 months)

Second level technical support on financial software problems in a B2B company: Responsibilities: ● Providing technical support to customers engineers via Atlassian Jira and LiveChat. ● Investigating customers problems. Fixing them when it is possible. Gathering data and preparing requests for developers, system administrators or DBA when L2 technical support wasn't able to fix a problem. ● Making SQL selections from a historical database on customers request. ● Preparing SQL updates to be approved by DBA. (Oracle DB) ● Servers performance monitoring via internal software.

T

Techical Support Engineer

Jul 2010 - May 2011 (11 months)

Being a night shift technical support engineer in a virtual hosting company, I had the following responsibilities: ● Investigate and solve customers problems with sites, databases and mail system, processing their requests, received via phone, char or OTRS support desk tool. ● Represent the company during night shifts in any situation, technical or administrative. Keep the conversation constructive and effective no matter how angry or inexperienced the calling or writing customer was. ● Monitoring the state of virtual hosting servers using Nagios, and solving any problems or escalating them to the systems administrators team.

About

Detail

Timeline

Résumé

Artem Katashev

About

Detail

Behavioral traits