Abdulsattar Beyioku
Software Engineer specialising in QA Automation & System Reliability
Open to remote QA Automation roles — available to start immediately
I build automated testing systems using Playwright, API testing, and CI/CD to help teams ship reliable products faster.
Stack I ship with
This portfolio’s own test suite runs in CI—Playwright, real user flows, and actionable reports—not a slide deck. I bring the same rigour to product teams: stable automation, API coverage where it matters, and pipelines developers trust.
What I do
QA automation
End-to-end and API suites, stable selectors, parallel runs, flake control, and reports that engineers actually use.
Reliability
Risk-based coverage, smoke vs regression splits, and clear ownership when builds break—without masking risk.
Backend & systems fluency
Comfortable in Python and TypeScript on the server: API contracts, auth flows, idempotency, and async paths. I design tests and harnesses that respect how distributed systems actually fail.
Testing & automation
A concrete example you can verify: this site ships with automated checks in the repository.
Testing & automation
Automated testing suite (Playwright)
- Built end-to-end tests for critical user flows (including contact form validation and core routes) and edge-case behaviour.
- Integrated with CI/CD using GitHub Actions so every change is exercised before deployment.
- Keeps regressions visible early—consistent quality signals instead of manual smoke tests only.
Tools & stack
Playwright and Cypress for UI automation; Postman for API testing; GitHub Actions / CI/CD for quality gates—plus Python, TypeScript, and Node where tests meet the backend.
Playwright
E2E automation with reliable selectors, parallel runs, traces, and CI integration.
Postman
API testing with Postman: validating endpoints, status codes, and response bodies—collections and environments for repeatable checks.
CI/CD
Pipelines that run the right tests at the right time—with artifacts engineers can act on.
Cypress
Browser tests for critical user flows, component tests, and fast feedback on PRs.
Python
Backend services, scripting, and test tooling—data validation, load fixtures, and glue between APIs and CI.
Typescript
Typed frontend and Node/Nest services—shared contracts, safer refactors, and clearer tests across the stack.
Why hire me
You get a QA mindset with an engineer’s ceiling: faster diagnosis, credible automation, and remote execution without babysitting.
Communication
Concise updates, explicit blockers, and repro steps that save engineering time. You always know what passed, what failed, and what I need next.
Remote execution
Experienced shipping with distributed teams across time zones. Overlap is agreed up front; decisions and CI artifacts stay visible so progress does not depend on constant meetings.
Reliability and ownership
Flaky tests and broken pipelines get the same rigour as production issues: reproduce, fix root cause, prevent recurrence. I treat environments, config drift, and dependency boundaries as first-class—same mindset as systems engineering, applied to quality.
How I contribute from day one
- Map critical user journeys and API contracts (Python or TypeScript services included); propose a minimal smoke suite immediately.
- Integrate tests into existing CI or stand up a lean GitHub Actions workflow—with artifacts for services and workers, not only the browser.
- Standardise reporting so failures are actionable for developers—not noise.
Formal foundation
Aerospace engineering trained me in rigour, constraints, and system-level reasoning. Postgraduate software engineering and an in-progress MSc sit on top of years shipping mobile, web, and payment integrations—so when I advocate for quality, it is from someone who has carried pager-grade ownership, not only filed tickets.
Experience
Production software across mobile, web, APIs, and integrations—release quality, test strategy, and delivery with remote teams.
Open to remote QA Automation roles — available to start immediately