I'm a QA engineer with 5 years of experience in Telecom. Most of that time was hands-on manual testing, now extended with Playwright automation suites that actually pay off: fewer regressions, faster releases, predictable outcomes.
These days QA is half thinking, half tooling. AI runs alongside me through test design, debugging, and code review. One engineer with the right tools can do what a team used to.
Location: Gdańsk, Poland · Open to international remote. Status: open-to-work. Experience: 5 years (3.5y manual testing, 1.5y test automation, Telecom).
New B2C/B2B self-service web portal for one of Poland's largest TV & internet providers (pay invoices, modify services, track data usage, and more). Built on top of the existing mobile-app backend - adapted for web without regressing mobile. Employer: Asseco Poland S.A. Client: Cyfrowy Polsat S.A.
Polkomtel (Plus) - Telecom QA across 25+ UAT releases
Senior manual QA on a rotating portfolio of telco projects for one of Poland's largest mobile operators - sales-force tools, regulatory programmes (PKE), digital signatures, and B2B/B2C self-service portals. End-to-end QA ownership under ~6-week UAT cycles, scrum and waterfall. Employer: Asseco Poland S.A. Client: Polkomtel Sp. z o.o.
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.
Quick navigation
- Who I am as an engineer, what I focus on, how I work with teams, and what I think tests are actually for
- 23 tools across 7 categories: automation, manual, API, CI/CD, debugging, test management, and the AI stack I actually use
- Two telecom chapters, both via Asseco: a dozen-plus Polkomtel/Plus subprojects shipped through manual UAT (25+ releases), then Cyfrowy Polsat self-service built in automation (ongoing)
- Every way to reach me - email for serious chats, LinkedIn for the slow lane, CV available on request
Case studies
The long-form story behind - what I actually did, what broke, and what it taught me.
- The full story of the Cyfrowy Polsat self-service build: solo tester on the dev side, a Playwright framework from scratch, MVP shipped in under two months
- Three and a half years across Plus's ~150-app portfolio: junior to senior, a dozen-plus subprojects, 25+ UAT releases, ending as lead of my own UAT team
Try the terminal
Type help in the terminal below to see what it can do. A few favourites: cv, contact, whoami, or philosophy.
Keyboard
⌘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.
PROBLEMS(0)OUTPUT●TERMINALTEST RESULTS(·)
jakubruniecki@0.1.9 · published 2026-05-26
portfolio · zsh
Welcome. Type 'help' for commands, or click files in the explorer.
Open on desktop for the full IDE experience - interactive file tree, terminal commands, and a live test runner.
I'm a QA engineer with 5 years of experience in Telecom. Most of that time was hands-on manual testing, now extended with Playwright automation suites that actually pay off: fewer regressions, faster releases, predictable outcomes.
These days QA is half thinking, half tooling. AI runs alongside me through test design, debugging, and code review. One engineer with the right tools can do what a team used to.
