Prototype · content is a draft based on the CV and still needs Ivan's approval
Ivan Kuznetsov

QA Lead · TradingView · Tbilisi, Georgia

Ivan
Kuznetsov.

I turn manual QA routine into code: CI/CD quality gates, release pipelines and test automation that keep faulty builds out of production.

Ivan Kuznetsov, smiling, with an "Open to work" frame
  1. lint
  2. unit
  3. coverage
  4. deploy
  5. integration
  6. e2e
  7. production
Get in touchCase studies
backend services behind CI/CD quality gates
6
test cases in Allure, 573 of them automated
0 → 1069
QA engineers led
5
interviews conducted
35+

How I think
about quality.

  1. Manual routine

    Routine is a signal to automate.

    If the team does the same manual check every release, it belongs in code.

  2. Quality gates

    The pipeline enforces quality.

    Every build passes the same gates before it reaches users. No heroics, no exceptions.

  3. Shared knowledge

    No single point of failure.

    Playbooks, wikis and rotations spread knowledge so the team works without one person.

Five and a half years at TradingView, from junior manual QA to lead of a team of five. I own quality from test strategy to production release, and I stay hands-on while leading.

What I built.

  1. 2024 – now

    One release pipeline for six backend services

    Quality gates at every stage and a single release flow, so faulty builds stop before deployment.

  2. 2024 – 2025

    Test coverage from zero to 1069 cases

    API autotest repositories, Allure reporting and a test base that grew from nothing to 573 automated tests.

  3. 2025 – now

    Exploratory testing, automated with AI

    An LLM-powered framework that replaced hours of manual exploratory testing on every release.

  4. 2024 – now

    A QA team that doesn't depend on one person

    A duty rotation, shared standards and documented knowledge for a team of five.

Toolbox.

Strategy & process

  • Backend QA strategy
  • CI/CD quality gates
  • Release management
  • Change management (ITSM)
  • On-call rotations

Automation

  • Python
  • Pytest
  • Playwright
  • Selenium
  • Go
  • Bash
  • JavaScript

Testing

  • API & backend
  • Load & performance (k6, JMeter)
  • Regression
  • Exploratory, AI-assisted

Infrastructure

  • GitLab CI
  • Jenkins
  • Docker
  • Kubernetes
  • Grafana
  • Zabbix
  • PostgreSQL
  • Allure

Leadership

  • Team of 5
  • Hiring & interviews
  • Onboarding
  • 1-on-1s
  • Code review standards

From junior QA
to QA Lead.

TradingView, March 2021 – now. One company, four roles.

  1. Sep 2025 – now

    QA Lead

    • Unified release pipeline for 6 backend services
    • AI framework for exploratory testing
    • QA on-call rotation; Selenium → Playwright migration

  2. Apr 2024 – Sep 2025

    Senior QA Automation Engineer

    • Backend QA strategy and quality gates for 6 services
    • 0 → 1069 test cases, 573 automated
    • JMeter load testing framework for 3 services

  3. Dec 2022 – Apr 2024

    QA Product Engineer

    • Made pre-deploy regression mandatory
    • Error triage from 24 searches a day to one query
    • Highest QA throughput on the team

  4. Mar 2021 – Dec 2022

    Junior QA Product Engineer

    • Manual, API, regression and feature testing; 109 bugs reported
    • Pine Script community support on Stack Overflow (~2K reputation)

Don State Technical University, Radio Engineer, 2014 · English (C1) · Russian (native)

After hours:
boards, bots, firmware.

Outside work I design circuit boards and write the firmware that runs on them (NRF51, ESP32, STM32), and build Python services with LLMs that take routine work off people's hands.

Portrait of Ivan Kuznetsov

Let's talk about
your release process.

Open to conversations about QA leadership roles and quality engineering projects.