Piotr Obara
PLDownload CV

Software tester · Test analyst

I test systems where every detail matters.

Banking, payments and insurance. I analyse requirements, design tests and verify data from the UI, through the API, down to the database. I am building my test automation skills in Playwright.

Download CVLinkedInGitHub
  • E2E tests: no data
  • WCAG 2.2 AA: no data
  • last run: no data
Piotr Obara, software tester
Availability
Immediately
Contract
Employment contract · B2B
Work mode
Remote · hybrid · on-site (Lublin)
Languages
Polish · English B2 (documentation, meetings, communication)
Certification
ISTQB CTFL 4.0

About me

Hi, I'm Piotr.

I am a software tester from Lublin. I started on the other side of the systems - in customer service and IT support at PKO Bank Polski, where I saw how an application defect turns into a real problem for a specific person.

At Fenige, as a Second Line Support Engineer, I learned to look for root causes in logs, APIs and databases. Moving into testing was a natural next step: I would rather find a problem before release than explain it afterwards.

Why software testing?

  1. Customer serviceI saw what a defect means for the customer.
  2. Help DeskI solved users' problems with banking applications.
  3. Second Line SupportI looked for the root cause in logs, APIs and SQL.
  4. QA EngineerI catch defects before they reach the customer.

Outside work

I like to spend my free time actively. Sport teaches me regularity and patience, which help in long regression cycles too.

Piotr on a mountain trail with a mountain ridge in the background
Mountain trailsHiking is my way to reset after a busy week.
Piotr running a race with a start number
Charity runsI take part in charity runs - sport with a purpose.Photo: Daniel Musiał Fotografia
Piotr with a gravel bike on a country road
CyclingGravel and road rides - my favourite way to spend a weekend.

IKE · IKZE

Finance and the stock market

I invest long-term and follow the capital market. It helps me understand the financial products I test from the customer’s perspective.

Domains

Industries and processes I know

Honestly marked: where I have worked and where I am still learning.

  • worked in

    Card payments and e-commerce

    Authorisation, 3DS, clearing, refunds, reversals, Visa and Mastercard chargebacks.

  • worked in

    Fraud and AML

    Monitoring rules, IP and gambling-domain blocking, profiling, alerts.

  • worked in

    Banking

    Supporting banking applications in branches, handling the loan process by phone.

  • worked in

    Regulation and settlement

    CESOP reporting to the Polish tax authority, settlement files, deposit currency conversion.

  • learning

    Insurance

    Loan repayment insurance and premium calculation - in my QA Lab.

How I test

Testing starts before the first line of code

  1. Requirements analysis

    I question requirements before code is written and write acceptance criteria that can be verified.

    ✓ Specification in Figma

  2. Test design techniques

    Boundary values, equivalence partitioning and decision tables instead of random clicking.

    ✓ Criteria 6-10 in the spec

  3. Risk-based testing

    I scope regression and UAT around what could hurt the customer or settlement.

    ✓ Test story

  4. Diagnosis: API → logs → database

    Postman, SQL and PostgreSQL. A bug report should be reproducible without my help.

    ✓ GET /api/profile.json

Experience

From customer service to quality assurance

  1. 07.2024 - present

    Manual QA Engineer

    Fenige S.A. · fintech, payments

    • The only tester in a team of three developers, in two-week Scrum sprints.
    • I test Visa and Mastercard chargebacks, fraud and AML rules, and CESOP reporting.
    • I test REST APIs and data flow: application → API → microservices → PostgreSQL.
    • I run UAT and choose the regression scope based on risk analysis.
    • I write tests and scripts in Postman, run with the Collection Runner.

  2. 04.2023 - 07.2024

    Second Line Support Engineer

    Fenige S.A.

    • Diagnosed production incidents by correlating APIs, logs and SQL data.
    • Verified transactions and settlements together with banks, Visa and Mastercard.
    • Generated and submitted CESOP reports to the tax authority via API.

  3. 10.2021 - 04.2023

    IT Support Specialist (Help Desk)

    PKO Bank Polski

    • Handled incidents and access issues in banking applications used by branches.

  4. 10.2020 - 10.2021

    Customer Service Consultant

    PKO Bank Polski

    • Handled the loan process by phone: data and creditworthiness checks, completing applications.

Test story

One fix, three more defects

Situation
A fix for saving monitoring rules when editing a merchant in the admin panel.
Action
Besides the fix itself, I tested the neighbouring edit paths and checked the data in the database.
Result
I found three independent defects, including a risk of overwriting another merchant’s configuration.

Evidence

Every claim comes with evidence

Things you can open and check. Statuses come from the latest test run of this site in GitHub Actions.

Growth

What I am learning

  • certifiedISTQB Certified Tester Foundation Level 4.0
  • in progress · tests of this sitePlaywright + TypeScript
  • in progress · audit of this siteDigital accessibility, WCAG 2.2

Contact

Let’s talk about testing in your team

Email is the fastest way to reach me. I am happy to walk you through my tests in an interview.

Email
piotr.obara.97@gmail.com
Phone
I will share my number in reply to your email.
Download CVLinkedIn