Oleksander Pyavchik | Manual QA Engineer Manual QA Engineer portfolio

Quality First

Oleksander Pyavchik

Manual QA Engineer

Manual QA Engineer with hands-on experience in web application testing, adaptive and cross-browser validation, API testing in Postman, and full-cycle test documentation.

I plan detailed test cases, analyze requirements and mockups for ambiguity and completeness, validate client-server behavior using DevTools, HTML/CSS, SQL, and basic Git or Ubuntu tooling, and communicate clearly with developers and product managers. Based in Kyiv, open to remote and international roles.

View My QA Projects Download CV Contact Me

Core Strengths

Key skills overview

A recruiter should be able to scan this section and see practical QA coverage, not just tool names.

Web Testing

Functional and responsive validation

Validate key user flows across browsers, breakpoints, and device classes with clear evidence and reproducible findings.

API Testing

CRUD scenarios in Postman

Design chained multi-step API scenarios with environment variables, collection variables, and response assertions.

Documentation

Traceable, actionable artifacts

Create test cases, checklists, bug reports, and summary reports that support release decisions and team alignment.

Analysis

Requirement and mockup review

Identify ambiguity, contradictions, missing acceptance criteria, and UI inconsistencies before defects reach production.

Recruiter Fit

Why I am a strong fit for this QA role

This content is written to address the hiring manager’s question: can this candidate contribute to product quality from planning through reporting?

Structured testing mindset

I break features into clear scopes, risks, and measurable checks so testing remains systematic instead of ad hoc.

Balanced technical understanding

I use HTML, CSS, browser tools, SQL basics, and client-server knowledge to investigate issues faster and communicate root causes clearly.

Reliable communication

I work comfortably with developers, PMs, and designers by reporting what matters, asking precise questions, and documenting impact.

Featured Work

Featured QA projects

Use the custom post type to manage projects per subsite. If no projects exist yet, the template shows implementation-ready examples.

Application shell, interface layout, controls, settings and fullscreen behavior, viewport handling, cross-browser checks in Chrome, Firefox, Edge, and Safari, breakpoints 320/375/768/1024/1440, public technical endpoints such as robots.txt and sitemap.xml, documentation of 76 manual test cases, and a high-severity visual integrity bug report.

pyavchik.space SPA Web Testing

Real manual QA case study for a browser-based SPA with explicit responsive and cross-browser coverage across Chrome, Firefox, Edge, Safari and breakpoints 320, 375, 768, 1024, and 1440.

  • Functional testing
Requirement review, acceptance criteria, browser support, API contracts, database assumptions, priority levels, traceability matrix, and testability analysis.

Requirement and Mockup Analysis

Static testing case study backed by a public SRS-style artifact: 91 requirements with priorities, browser support, API contracts, database assumptions, and traceability to test coverage.

  • Static testing
Authentication, token handling, game initialization, spin flow, balance and history validation, wallet scenarios, negative paths, security-focused API checks, review of Swagger / OpenAPI documentation, and SQL reference review for persistence and constraint validation.

REST API Testing in Postman

API testing case study with public Postman, Swagger, and SQL evidence: 57 tests, documented contracts, and database-aware validation across auth, chained scenarios, negative cases, security checks, and response handling.

  • Functional API testing

Tools

Testing tools and technologies

Keep this section short on the homepage and link deeper details to the Tools page.

Postman

API collections, variables, assertions, and scenario chaining.

TestRail

Structured test case management and execution tracking.

Chrome DevTools

UI inspection, responsive checks, network diagnostics.

MySQL / SQL

Data verification, query-based validation, state checks.

Testing Mindset

My testing process

  • 1. ClarifyReview requirements, mockups, edge cases, and risks
  • 2. DesignChoose coverage using EP, BVA, decision tables, and error guessing
  • 3. ExecuteRun structured UI, API, database, and regression checks
  • 4. ReportDocument defects with evidence, impact, and reproduction steps

Recommendations

Testimonials placeholder

“Reliable in finding edge cases early, documenting issues clearly, and keeping quality visible across the team.”

“Strong attention to detail and good judgment about what should block a release versus what should be monitored.”

Read more about my QA approach

Artifacts

Examples of QA documentation

Recruiters often respond well to visible artifacts because they show working style, not just claims.

QA Notes

Short notes on testing approach

Optional thought pieces and review notes that show how QA thinking is applied beyond checklist execution.

Contact

Open to Manual QA Engineer opportunities

Based in Kyiv and open to remote or international teams. I can contribute through structured web and API testing, strong documentation, critical requirement analysis, and clear communication with cross-functional stakeholders.

pyavchik@gmail.com LinkedIn GitHub Telegram

How I Work

What I validate in real projects

  • Functional flows and edge cases
  • Responsive behavior and layout consistency
  • Cross-browser compatibility
  • API contracts and CRUD paths
  • Data persistence and UI-data alignment
  • Release-risk summary for stakeholders