← Back to talent
V

BENCH+ PROFILE

Vladislav

QA Engineer
Test automation for web, API, and business-critical financial systems using C#/.NET-based tooling

Senior QA Automation Engineer with strong hands-on experience in C#/.NET test automation, Selenium, SpecFlow, NUnit, Playwright exposure, API testing, database checks, and automation framework maintenance for fintech and enterprise subscription systems.

BEST-FIT USE CASE

A quality engineering role focused on building and maintaining automated UI and API regression coverage for complex web platforms with business workflows, integrations, and structured data validation.

Not the primary fit: Less aligned with roles centered on product management, manual-only QA, AI model engineering, platform ownership, or production DevOps responsibilities.

EVIDENCE HIGHLIGHTS

What supports the assessment

01

Owned automated test coverage for new functionality in an enterprise lending workflow using C#, SpecFlow, Selenium, and NUnit.

02

Worked on automated validation around structured documents such as spreadsheets, PDFs, CSV, and XML as part of test scenarios.

03

Performed API testing to verify backend integrations and data consistency.

04

Supported an existing BDD automation framework for a cloud subscription and payment platform and participated in a prototype Playwright-based framework.

05

Participated in manual testing of new functionality, database testing, performance-testing activities, code review, and Scrum ceremonies.

06

Refactored and stabilized an inherited automation codebase on a current project, with positive feedback on improvement suggestions and onboarding into the domain.

WORKING STYLE

How they show up

  • Raises questions when clarification is needed and works with relevant teammates to resolve them.
  • Suggests improvements to automation and process flow.
  • Can work in a mostly independent QA automation setup while coordinating approvals and implementation details with stakeholders.
  • Participates in Scrum ceremonies, code reviews, and cross-functional discussions around testability and release readiness.