Petr Komissarov
Тестировщик
11+ years exp
7+ years ML exp
Dart
SQL
Go
Python
Java
TypeScript
Kotlin
Swift
C#
JavaScript
Active 23 days ago
+7 (921) 5636424 Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
A mid-level SDET/test-engineering practitioner with cross-stack automation experience across Python unit helpers, API service tests in TypeScript, and Playwright end-to-end tests. The strongest proven skill is building CI-aware test automation infrastructure and pragmatic fixtures, evidenced by the Vitest runner configuration, Playwright fixtures, and pytest parallel/rerun setup. There is limited public evidence of contract/schema testing, performance/load engineering, or formal bug-triage artifacts and RCA.
Technical skills
Dart
SQL• Junior • 11y+
Go• 9y+
Python• Middle • 9y+
Java• Senior • 7y+
TypeScript• Middle • 6y+
Kotlin• Junior • 5y+
Swift• 5y+
C#• Middle • 3y+
JavaScript• 3y+
Python
Asyncio
Aiohttp
FastAPI
Litestar
Pydantic
SQLAlchemy
C#
ASP.NET Core
gRPC for .NET
WPF• 11y+
Databases
Google BigQuery
PostgreSQL
MS SQL• 11y+
MySQL• 8y+
Oracle• 8y+
ClickHouse• 4y+
RabbitMQ• 4y+
Apache Kafka
Frontend
ESLint
Prettier
Vite
DevOps
Docker
GitLab CI
Graylog
gRPC
Kubernetes
Prometheus
Observability
CI/CD• 9y+
TeamCity• 8y+
GCP• 7y+
Git• 7y+
Jenkins• 7y+
Rest API• 4y+
GitHub Actions• 3y+
Grafana
VictoriaMetrics
QA
TestRail
Playwright
Allure Reporting
Selenium• 11y+
Pytest• 9y+
TestNG• 7y+
Cypress• 6y+
Rest-Assured• 6y+
XCUITest• 6y+
Charles Proxy• 4y+
Cucumber• 4y+
Mobile
Flutter
JUnit
AI/ML
Hadoop• 7y+
Spark• 7y+
Timeline
Head of Automated Testing Direction
•
Executive
Set Partnerstv
•
Full-Time
Led an automated testing direction for a loyalty program, subscription, and partner offers. Built Python and Kotlin frameworks, tools, and web applications, performed code reviews, and introduced CI/CD. Managed a QA automation team and delivered monitoring, log parsing, and mocking to improve reliability and reduce manual testing effort.
Python
SQLAlchemy
Aiohttp
FastAPI
Litestar
Pydantic
Apache Kafka
VictoriaMetrics
Grafana
Software Developer
•
Middle
Test IT
•
Full-Time
Worked on integrating TestIT with test frameworks and delivering functionality to customers. Developed testing frameworks and tools, including IntelliJ IDEA plugins. Contributed to CI/CD adoption, performed code reviews, and supported delivery in collaboration with stakeholders.
Java
JavaScript
C#
Go
Python
Kotlin
Git
GitHub Actions
SDET
•
Middle
Test IT
•
Full-Time
Developed automation solutions for a test automation team within the TestIT product ecosystem. Implemented and expanded automated testing frameworks and adapters for multiple languages. Improved and maintained existing automation by debugging failing tests, conducting code reviews, and supporting continuous delivery pipelines.
C#since 2023
Selenium
Rest API
RabbitMQ
QA Automation Engineer
•
Middle
VK
•
Full-Time
Managed a QA team inside a product team for VK Market, covering manual and automated testing for web and mobile. Organized beta testing and managed testing execution strategy. Implemented automation using a stack that included reporting and analytics tooling to support release quality.
Java
Cucumber
ClickHouse
TeamCity
Charles Proxy
Head of Testing Department
•
Executive
Sumsub
•
Full-Time
Led a QA team and introduced automated testing for mobile and web platforms. Created testing strategy and test plan, ran technical interviews, and trained team members. Built mobile automation from scratch and improved regression speed through expanded automated coverage.
Kotlinsince 2021
Swift
XCUITest
YouTrack
QA Automation Engineer
•
Middle
Unlimint
•
Full-Time
Owned QA automation efforts for a CRM and reporting initiative. Led QA team activities, defined testing strategy, and implemented automation from scratch. Delivered both load and visual testing, built regression checks for CRM and reports, and enabled faster and more reliable releases.
TypeScript
Cypress
Java
Rest-Assured
Jenkins
Jira
Software Developer
•
Middle
Grid Dynamics Poland
•
Full-Time
Migrated Big Data projects to a new technology stack and stabilized related CI pipelines. Implemented unit, functional, and integration testing as part of delivery across multiple teams. Performed code reviews and coordinated changes with 7+ teams while improving test coverage and execution reliability.
Python
Pytest
Spark
Hadoop
Javasince 2019
TestNG
GCP
MySQL
Oracle
SDET
•
Middle
ePayments
•
Full-Time
Built and maintained a test automation team for test and reporting systems. Developed a test framework, created automated tests and mock components, and supported manual QA engineers through coaching. Focused on improving execution speed and maintainability by reworking the project architecture for large test suites.
MS SQL
TeamCitysince 2018
Jira
QA Engineer
•
Middle
Intermedia
•
Full-Time
Implemented automated testing for a security product including web UI and REST API. Combined automation with manual testing when needed. Worked with databases and issue tracking, and used CI/CD to ensure repeatable builds and test execution.
Pythonsince 2017
Pytestsince 2017
Jirasince 2017
MS SQL
CI/CD
QA Automation Engineer
•
Middle
Katharsis
•
Full-Time
Delivered web and desktop automation for software used by regional authorities in labor and social protection. Implemented UI automation to increase coverage and reliability of test results. Set up reporting and improved coverage for automated testing scenarios using a Windows desktop UI focus.
WPF
MS SQLsince 2016
Seleniumsince 2016
Saint Petersburg State University of Economics and Finance
Bachelor's Degree •
Economic Theory and Policy; National Economy
Middle Frontend Developer
Confidence: Medium Generalist
A hands-on QA/test automation engineer at a middle level who writes end-to-end and API test code and simple service wrappers. The strongest proven skill is building practical test infrastructure and automation, demonstrated by Playwright fixtures that route-block resources, a Vitest configuration using availableParallelism, and a small service layer (orders.service.ts) used by tests. There is little or no evidence of frontend component design, accessibility testing, measured performance telemetry, or advanced state-management patterns in public code.
UI Component Architecture
How interface parts are built
Not evidenced in public code
Responsive & Cross-browser
2/10
Works on all screens and browsers
Basic cross-browser/test-target configuration exists but it is narrow - Playwright is configured for Chromium/Chrome only and there is no evidence of responsive/layout strategy or RTL/i18n work.
Evidence
playwright-tests/playwright.config.ts: explicit browserName set to "chromium" and channel "chrome"
playwright-tests/tests/example.spec.ts: layout/role-based selectors used for assertions (functional, not responsive)
Performance Optimization
3/10
Speed of the interface
Some practical performance-minded choices for test speed and concurrency are present (resource blocking, parallelism, concurrent requests), but there is no measurement-backed optimization, bundle analysis, or advanced runtime tuning.
Evidence
playwright-tests/tests/fixtures.ts: page.route aborts image requests to speed tests
debridge-tests/vitest.config.ts: sets maxConcurrency to availableParallelism()
debridge-tests/tests/orders.test.ts: uses Promise.all to fetch details concurrently
Accessibility & Semantics
Usable for everyone
Not evidenced in public code
State Management & Data Flow
2/10
Managing data in the app
Server-client data flows for tests and simple service layers exist with basic error assertion, but there is no advanced server-state discipline (cancellation, optimistic updates, cache invalidation) or state machines.
Evidence
debridge-tests/src/services/orders.service.ts: encapsulated getAll and getDetails functions using fetch and assertResponse
debridge-tests/tests/orders.test.ts: sequence of tests that exercise filtering and concurrent details retrieval
UX & Visual Polish
Look and feel quality
Not evidenced in public code
Expertise
Frontend Architecture & Build Tools• Middle
Technologies
TypeScript• Middle • 6y+
Vite
ESLint
Prettier
Recommendations
- Develop E2E and API test suites and test automation infrastructure including fixtures, test-runner configuration, and CI integration.
- Build and maintain test tooling and developer ergonomics - e.g., shared service helpers, logging, retries, and environment-loading utilities.
- Work on improving test performance and reliability with measured benchmarks, deterministic mocking/stubbing, and request cancellation or retry strategies.
- Expand into test-related build tooling or developer platform work such as curated lint/config presets, CI pipelines, and local developer scripts.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle QA Engineer
Confidence: High SDET
A mid-level SDET/test-engineering practitioner with cross-stack automation experience across Python unit helpers, API service tests in TypeScript, and Playwright end-to-end tests. The strongest proven skill is building CI-aware test automation infrastructure and pragmatic fixtures, evidenced by the Vitest runner configuration, Playwright fixtures, and pytest parallel/rerun setup. There is limited public evidence of contract/schema testing, performance/load engineering, or formal bug-triage artifacts and RCA.
Test Automation Frameworks
5/10
Building automated tests
Has an automation framework mindset - custom pytest config with parallelization and reruns, Playwright config and a page fixture that aborts images, and Vitest config with concurrency and retry settings; shows practical fixture and selector discipline but lacks evidence of an extensive bespoke framework or mock servers with business logic.
Evidence
histogramer/tests/pytest.ini: '-n auto --reruns 1' parallelization and reruns configured
playwright-tests/tests/fixtures.ts: Playwright page fixture aborting image requests
debridge-tests/vitest.config.ts: test.maxConcurrency and retry driven by env, Allure reporter setup
Test Coverage & Strategy
4/10
What and how to test
Tests demonstrate negative-paths, parametrized checks and explicit assertions for failure modes and input validation, plus test markers to group responsibilities; lacks property-based tests, mutation testing, or a visible risk-based test taxonomy.
Evidence
histogramer/tests/test_datetime_helper.py: parametrize negative cases and explicit exception assertions
histogramer/tests/test_args_helper.py: negative-path tests asserting NotADirectoryError and SystemExit
debridge-tests/tests/orders.test.ts: sequential tests with skip logic and multi-step validations
API & Integration Testing
4/10
Testing how parts work together
Clear API/integration testing present: service layer calling endpoints, a response assertion utility and retry/reporting configured in test runner; lacks formal contract/schema testing, explicit schema validation or testcontainers-based integration environments.
Evidence
debridge-tests/src/services/orders.service.ts: service calls to /api/Orders endpoints with fetch and JSON handling
debridge-tests/src/tools/validation.tool.ts: centralized assertResponse used across API tests
debridge-tests/vitest.config.ts: reporters and retry configuration for API test runs
Performance & Load Testing
Testing speed under load
Not evidenced in public code
Bug Reporting & Analysis
2/10
Finding and describing bugs
Some attention to flakiness and cleanup is shown (reruns, handler closure, teardown), but there are no reproducible bug reports, RCA artifacts, or linked issue fixes in the code to demonstrate bug triage capabilities.
Evidence
histogramer/histogramer/tests/test_log_helper.py: explicit handler closure and teardown in finally blocks
histogramer/tests/pytest.ini: global reruns configured ('--reruns 1') indicating flake handling
CI Test Integration
5/10
Running tests automatically
CI/test-run integration is visible via project scripts and runner configs (ci:test scripts, reporters, env-driven retry/timeouts); missing are CI-level test-sharding by diff, quarantine mechanics for flaky tests, or historical trend artifacts.
Evidence
debridge-tests/package.json: 'ci:test' script and other CI-oriented scripts
playwright-tests/package.json: 'ci:test' and 'browser:install' scripts for CI orchestration
debridge-tests/vitest.config.ts: reporter and retry settings suitable for CI
Verified artifacts
Expertise
SDET & Test Engineering• Middle
Industries
Blockchain & Crypto• Middle
Technologies
Python• Middle • 9y+
Go• 9y+
JavaScript• 3y+
Java• Senior • 7y+
SQL• Junior • 11y+
C#• Middle • 3y+
gRPC
TestRail
TestNG• 7y+
Selenium• 11y+
Cucumber• 4y+
Cypress• 6y+
Playwright
GCP• 7y+
SQLAlchemy
GitHub Actions• 3y+
FastAPI
Prometheus
VictoriaMetrics
Allure Reporting
GitLab CI
CI/CD• 9y+
Jenkins• 7y+
Git• 7y+
Docker
Kubernetes
ASP.NET Core
Grafana
Asyncio
gRPC for .NET
Rest-Assured• 6y+
Pytest• 9y+
WPF• 11y+
Pydantic
XCUITest• 6y+
Charles Proxy• 4y+
Litestar
Aiohttp
Graylog
TeamCity• 8y+
Recommendations
- Develop a contract/schema testing layer (e.g., add Schemathesis or JSON Schema validation) for API services and encode expected error codes for negative paths.
- Introduce property-based tests for core helpers (use Hypothesis for Python) to capture boundary conditions and invariants beyond example-based tests.
- Add a quarantine or per-test retry policy and CI test selection (run only impacted tests on PRs) so flaky tests are isolated rather than globally rerun.
- Start a simple performance test harness (k6 or Locust) for key API endpoints and codify SLO thresholds and percentile checks in CI
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Junior Backend Developer
Confidence: Medium API Engineer
A developer focused on API test automation and Node.js-based test tooling at a junior level. The strongest proven skill is building API-driven test clients and test suites, demonstrated by debridge-tests/src/services/orders.service.ts and the end-to-end tests in debridge-tests/tests/orders.test.ts. There is little or no evidence of database design, production-grade distributed architecture, advanced security token handling, or performance engineering in public code.
API Design
2/10
How well APIs are designed
Basic API client code exists with simple pagination parameters and response assertions but no versioning, idempotency, or clear error contract across boundaries.
Evidence
debridge-tests/src/services/orders.service.ts: POST /api/Orders/filteredList with skip/take params and GET /api/Orders/{orderId}
debridge-tests/tests/orders.test.ts: end-to-end tests hitting the API and asserting results
Data Layer & Database
Working with databases
Not evidenced in public code
Scalability & Performance
2/10
Handling load and speed
Some concurrency and test-level parallelism are used (Promise.all, test runner concurrency and asset route aborting) but no caching, queueing, or measured performance work.
Evidence
debridge-tests/tests/orders.test.ts: uses Promise.all to fetch details concurrently
debridge-tests/vitest.config.ts: sets maxConcurrency and test retry via env
playwright-tests/tests/fixtures.ts: aborts image requests to speed tests
System Architecture
2/10
Overall system structure
A small, conventional module layout (models/services/tools/tests) is present indicating basic separation of concerns but no evidence of multi-service architecture or documented inter-service contracts.
Evidence
debridge-tests/src/services/orders.service.ts: service module for API interaction
debridge-tests/src/tools/log.tool.ts: separate tooling module for logging
Security & Auth
2/10
Protecting data and access
Minimal security awareness - logger redacts sensitive keys and requests use content-type headers, but no auth lifecycle, input validation, token handling, or secrets management is visible.
Evidence
debridge-tests/src/tools/log.tool.ts: pino logger configured with redact for password and token
debridge-tests/src/services/orders.service.ts: explicit content-type header on API requests
Reliability & Observability
3/10
Stability and monitoring
Basic observability and reliability practices for test automation are present: structured logging, test retries, reporters, and an assertResponse pattern, but no resilience patterns (timeouts/backoff/circuit breakers) or metrics/alerts configuration.
Evidence
debridge-tests/src/tools/log.tool.ts: pino + pino-caller + pretty configured
debridge-tests/vitest.config.ts: retry and reporters configured
debridge-tests/src/services/orders.service.ts: calls assertResponse after fetch
Expertise
Node.js• Junior
Technologies
Observability
Rest API• 4y+
Recommendations
- Lead development of API client libraries and automated API test suites (contract tests, integration tests) that exercise REST endpoints and validate schemas.
- Improve reliability of API interactions by implementing retries with exponential backoff, timeouts, and idempotency handling in the service layer.
- Enhance observability and CI - add structured metrics, test-flakiness tracking, and integrate tests into CI pipelines with clear failure reporting and artifact collection.
- Work on API contract testing and mock servers to decouple tests from upstream services and enable reliable local/CI test runs.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: