The Role
The automation framework isn’t built yet — or isn’t built well enough. This role exists to change that. You’ll own the test architecture from design through CI gates, converting complex system flows into reliable automated coverage and keeping it reliable as the product scales. This isn’t a manual QA role with some scripting on the side: Python and Pytest are the core tools, and framework design is the actual job.
About the Product
The platform is a security product operating close to the threat layer — backend-heavy, multi-component, with system flows that span UI, API, and backend in the same execution paths. Test coverage here isn’t just about feature correctness: it’s about release confidence in a domain where failures have security implications. The CI pipeline needs to be trustworthy, and right now there’s meaningful work to do to make it that way.
Technology Stack: Python and Pytest as the framework core. Playwright for UI automation. GitHub Actions for CI. The product is security-focused, backend-heavy, and multi-component — test flows need to cover the full system, not just surface-level UI interactions. Cloud infrastructure (AWS, Azure) and containerised test environments are in scope for candidates who’ve operated at that level.
What You’ll Be Doing
- Design and build the automated test framework in Python and Pytest — fixtures, parametrization, architecture, not just individual test cases
- Convert complex manual test flows into scalable E2E and integration coverage across UI, API, and backend in unified runs
- Debug and eliminate flaky tests — environment-sensitive failures, timing issues, infrastructure instability
- Integrate tests into CI/CD pipelines (GitHub Actions) and own the reliability of those gates
- Identify coverage gaps and push automation-first thinking across the engineering team
- Evolve the framework architecture as the product expands to new platforms and components
- Partner with backend and DevOps engineers on test infrastructure, not just hand off test results
What We Expect
Must-have
- 7+ years of hands-on QA Automation / Test Engineering
- Strong Python — design, architecture, and debugging, not just scripting to make tests pass
- Deep Pytest experience: fixture design, parametrization, framework-level decisions
- E2E and integration testing for complex multi-component systems
- Playwright for UI validation combined with API and system-level testing in the same flows
- Strong debugging instincts for flaky and environment-sensitive failures
- CI/CD integration experience — GitHub Actions preferred
- Proven track record converting manual test suites to automated coverage
Nice to have
- Security product background — the closer to the threat layer, the better
- Penetration testing concepts
- Performance testing
- OS-level debugging: process/service lifecycle, filesystem, permissions, execution flows
- Distributed systems or microservices testing
- Cloud test infrastructure — AWS, Azure, containerised environments
- Observability and reporting: ReportPortal, Grafana
- Test management tooling: Xray, Jira
- Software engineering principles applied to test code: OOP, SOLID, KISS, DRY, and relevant patterns (Singleton, Factory, Builder, Strategy)
Why This Role Is Worth Your Time
- Framework ownership is genuine — you’re making architecture decisions, not implementing a test plan someone else designed
- The security domain adds real technical depth to the QA work: coverage decisions have consequences beyond feature completeness, and system-level debugging is a core skill, not an occasional edge case
- Direct impact on release confidence means your work is visible and load-bearing — not a supporting function that gets skipped when timelines compress
- The role has room to grow: as the product expands to new platforms, the framework needs to scale with it, which means the architectural decisions you make now will matter for a long time
