Evgeny Tkachenko

Evgeny Tkachenko

Profile picture for user evgeny.tka4enko@gmail.com

Member for

9 years 1 month

Evgeny Tkachenko boasts over fifteen years of extensive experience in the realms of test management, automation testing, and release management, predominantly within the domains of telecommunication, financial services, healthcare, and online entertainment industries. Presently, as a Head of Quality Engineering at One Medical, he leverages his wealth of expertise and knowledge to diligently ensure the delivery of exceptionally high-quality products. Evgeny's eminence extends beyond his professional pursuits, as he frequently graces prestigious QE/Dev/Agile conferences both in the United States and Europe, captivating audiences with his insights. Moreover, he holds the esteemed distinction of being an esteemed author, contributing his erudition to renowned international test and QE publications.

Company
One Medical
Job Function
Quality Engineering
Job Title
Head of Quality Engineering
Industry
Computer Software - SaaS
Interests
Agile
Project Management
Release Management
Test Automation
Country
United States

Evgeny Tkachenko has more than ten years of experience in test management, automation testing, and release management, mainly on complex projects in the telecommunication, financial, and online entertainment industries. Previously his experience as a QE Manager in Russia’s most important technology center gave Evgeny a unique perspective in test process development. Now at Wayfair, he applies his experience and expertise to do whatever is required to deliver the highest quality product possible. Evgeny is a frequent speaker at QA/Dev/Agile conferences in the US and Europe, and an author for international test and QA publications.

All Articles by Evgeny Tkachenko


All Stories by Evgeny Tkachenko

A list of requirements with checkmarks Testing the Requirements: A Guide to Requirements AnalysisEveryone knows testing requirements is important, and everyone says they do it, but it seems like no one knows exactly how. The best way to solve this problem is to introduce a requirements analysis stage that has to be done before coding starts. No one knows a product as well as a tester who works with it every day!