Manual leadership + Playwright automation
I'm a QA engineer with 5 years of experience across fintech and e-commerce. Most of that time was hands-on manual testing; the last 1.5 years I've focused on building Playwright automation suites that actually pay off — fewer regressions, faster releases, predictable outcomes.
I treat tests as a feature, not a tax. The goal isn't coverage numbers — it's catching the issues that would have shipped, and giving the team enough confidence to move faster.
Location: Gdańsk, Poland · Open to international remote. Status: open-to-work. Experience: 5 years (3.5y manual testing, 1.5y test automation, Fintech & E-commerce).
Playwright + TypeScript test suite against a public e-commerce demo site. POM architecture, fixtures, parallel execution, CI on every push.
Tech: Playwright, TypeScript, GitHub Actions
Inherited a manual regression suite that blocked every release for three days. Designed and built a Playwright suite covering critical user paths; integrated into CI so regression ran on every PR.
Fintech · Senior QA Engineer · 2023–2024
Tech used: Playwright, TypeScript, Postman, JIRA
Gdańsk, Poland · Open to international remote
Any given morning: files open on the left, a test suite waiting on the right, the terminal blinking below. I rebuilt that view for the browser so you can sit in my seat for a few minutes. Click, run, type - every piece is real content about how I work.
AI didn't replace my testing instincts. It removed the friction between having them and acting on them.
What used to take days of test authoring now takes an afternoon
so I spend the rest hunting the bugs no script would catch.
Type help in the terminal below to see what it can do. A few favourites: cv, contact, whoami, or philosophy.
⌘K or CtrlK opens the command palette.
↑ in the terminal replays your last command.
And if you crack open DevTools, there's a hello waiting in the console.
Senior QA Engineer · Manual leadership + Playwright automation
I'm a QA engineer with 5 years of experience across fintech and e-commerce. Most of that time was hands-on manual testing; the last 1.5 years I've focused on building Playwright automation suites that actually pay off — fewer regressions, faster releases, predictable outcomes.
I treat tests as a feature, not a tax. The goal isn't coverage numbers — it's catching the issues that would have shipped, and giving the team enough confidence to move faster.
