Арсен

Arsen Turkin
Manual QA Engineer
Ivano-Frankivsk, Ukraine [open contact info](look above in the "contact info" section) [open contact info](look above in the "contact info" section)

SUMMARY

Manual QA with real experience on a full end-to-end product, from sign-up and onboarding all the way to
contracts, rate logic, timesheets, invoices and payouts. I write checklists and Gherkin test cases, file bug
reports that devs can actually reproduce, and use AI to get test design and reporting done faster.
Studied Computer Science and Mathematics.

EXPERIENCE

Manual QA Engineer Nov 2025 - Apr 2026
SoftServe
• Tested the whole platform end to end: candidate, client and expert sign-up, onboarding, vacancy
search and scoring, interview scheduling and shortlisting.
• Owned QA for the money side of the product: contract offers, rate logic across freelance, payroll and
permanent employment, commissions, timesheets, invoices and payouts. Caught a lot of issues in
role-based rate visibility, which was the trickiest part to get right.
• Wrote checklists and Gherkin (Given/When/Then) test cases and kept them up to date with the
team's QA standard.
• Filed bug reports devs could reproduce in one go: Jam recordings, console and network logs, exact
steps. Followed them through to closed together with frontend and backend.
• Ran cross-browser and responsive checks, compared builds against the Figma designs, and tested
the multilingual UI and the notification system.
• Set up an AI-assisted workflow: built a reusable Claude prompt setup that turns a feature description,
screen recording or mockup into Gherkin test cases, and drafts structured bug reports.
• Worked in Scrum: sprints, grooming and reviewing acceptance criteria. Tracked tasks in Jira and
Asana.

EDUCATION

Computer Science and Mathematics 2022 - 2024
Université Paris-Saclay, two years completed

COURSES

• QA Engineer Bootcamp, manual software testing (Udemy)
• Software Manual Testing on a live project (Udemy)

SKILLS

Testing: functional, regression, smoke, cross-browser and responsive testing; checklists; Gherkin test
cases.
Tools: Jira, Asana, Confluence, Figma, Jam, Chrome DevTools, Crowdin, Claude (AI-assisted QA).
Technical: DevTools, reading HTML and CSS, HTTP status codes, basic SQL for data checks.

LANGUAGES

Ukrainian (Native) English (B2) French (B2)

Portfolio
Sample QA artifacts from a talent-platform sign-up flow. Product details anonymized.

1. TEST SUITE — CANDIDATE SELF SIGN-UP

Scope: manual registration flow: sign-up form, email verification, profile setup via CV upload or LinkedIn
link, with a skip option.
Scenarios: 7 total — 1 critical, 3 high, 3 medium.
Coverage: happy path, alternative paths (LinkedIn, skip), negative validation, and data-driven edge
cases (password rules, phone country code).
Format: BDD / Gherkin, each scenario tagged by priority; happy path automated as a smoke test, full
suite run in CI on merge and nightly.

2. TEST CASES (GHERKIN)

Three representative scenarios from the suite: a critical happy path, a negative validation case, and a data-driven
edge case.
Happy path — sign up and build a profile from a CV
@critical
Scenario: Visitor creates an account and builds a profile from a CV
Given I am a visitor on the sign-up page
When I fill in the sign-up form with valid details
And I accept the Privacy Policy, Terms of Service and Code of Conduct
And I click Next
Then my account is created and I am automatically logged in
And I am taken to the "Thank you for joining" page
When I click Verify email
Then I see a confirmation that the verification email has been sent
When I click Complete account
Then I am taken to the profile setup page
When I upload my CV and click Next
Then I see a "Parsing in progress..." loader while my CV is parsed
And a profile is generated from my CV
And I see the "Review your profile" message

Negative — invalid field input shows an error
@high
Scenario Outline: Sign-up form shows an error for invalid input
Given I am a visitor on the sign-up page
When I enter "<value>" in the <field> field
Then I see the error "<error_message>"

Examples:
| field | value | error_message |
| Email | test.email | Please enter a valid email |
| Phone | (empty) | Phone number is required |
| LinkedIn| profile-x | Please provide a valid LinkedIn URL |

Edge / data-driven — password rules validated as you type
@medium
Scenario Outline: Password rules are validated as I type
Given I am a visitor on the sign-up page
When I enter "<password>" in the Password field
Then the "<rule>" requirement is marked as "<state>"

Examples:
| password | rule | state |

| shortA1 | 9+ characters | failed |
| lowercase123 | Uppercase & lowercase | failed |
| SecurePass1 | 9+ characters | passed |

3. BUG REPORT (SAMPLE)

Title: Sign-up: "Next" stays enabled when Confirm Password does not match Password.
Environment: Chrome 126 / macOS 14.5, staging build.
Severity / Priority: Major / High.
Preconditions: visitor on the candidate sign-up page.
Steps to reproduce:
1. Fill in all sign-up fields with valid data.
2. Enter "SecurePass1" in Password.
3. Enter "SecurePass2" in Confirm Password.
4. Accept the Privacy Policy, Terms of Service and Code of Conduct.
5. Observe the Next button.
Expected: Next is disabled while Password and Confirm Password differ, and a mismatch error is
shown.
Actual: Next stays enabled; clicking it submits the form and creates the account with mismatched
passwords.
Attachments: Jam recording, console log, network request for the create-account call.