René SiklenkaGAME QA PORTFOLIO

GAME TESTING · MANUAL QA

Game mechanics.
Clear reports.
Player perspective.

I'm René. I test game mechanics, investigate unexpected behaviour and turn findings into reproducible bug reports. I care about how a game works—and how it feels to play.

Explore the reportsMy QA experience

01 / LAST TRAIN HOME

Bugs I found in the released game.

Three findings from the Steam version: a progression blocker, an item interaction issue and a misleading cursor.

Found on PC (Steam) on 23 January 2025 during a recruitment task. The text is edited for readability; reproduction rates come from my original reports.

Severity reflects the impact on play.Critical: blocked progression · Minor: limited impact or an easy workaround

02 / MY QA APPROACH

How I test games

I focus on gameplay, clear reproduction and the effect a bug has on the player.

QA ≠ DESIGN

I distinguish a reproducible defect from a design preference. If the intended behaviour is unclear, I ask about the rule and describe the player friction before calling it a bug.

03 / PRACTICAL EXPERIENCE

Game QA experience.
A wider testing toolkit.

My focus is game testing. My experience with API and fintech testing helps me investigate bugs by checking the data and following how the system responds to each action.

YouTrackJiraPostmanGraphQLSQL basics
GAME QA

Grip Digital

Tested game mechanics and features during early alpha development. Reproduced defects, reported them in YouTrack and verified fixes with developers and designers. Took responsibility for QA of selected features ahead of milestone deliveries.

API & FINTECH QA

Vacuumlabs

Worked on banking and fintech products. Tested a backend without a frontend using GraphQL and Postman—a useful foundation for investigating data and application state.

RELEASED-GAME TESTING

Last Train Home

Found and documented three issues in the Steam release during a recruitment task, including a cross-mission progression blocker. A former producer later confirmed to me that the blocking issue was fixed following my report.