Open to QA Lead roles

QA that holds up in production.

I’m a QA Lead with ten years in fintech, banking, logistics and SaaS. I own the test lifecycle from strategy to UAT, whether I’m the only QA on the project or leading six testers.

Book a 30‑minute call (opens in a new tab) See the work

10 years in QA
6 testers led
100% defect traceability at Umbrage
0 critical production escapes at Umbrage

sample

A sample access-control test scenario, written in Gherkin and then in plain language. All three steps pass.

role-access.feature

Feature: Record access by permission set

Scenario: A user outside the role can’t open the record

Given a user with the read-only permission setSign in as a user with read-only access.

When they open a record owned by another roleOpen a record that belongs to another role.

Then access is deniedCheck that access is denied.

A sample Playwright test in TypeScript that checks a read-only user is denied access. It passes in Chromium, Firefox and WebKit.

role-access.spec.ts

test('read-only user is denied',
  async ({ page }) => {
  await signInAs(page, 'read-only');
  await page.goto('/records/other-role');
  await expect(page.getByRole('alert'))
    .toHaveText('Access denied');
});

chromium

firefox

webkit

A sample CI pipeline on a pull request: install, API tests in Postman, Playwright regression, and results reported to Qase. Every stage passes.

Selected work

Held at Umbrage and Softtek. 100% defect traceability and no critical production escapes at Umbrage.

Multi-org Salesforce validation

Each program ran in its own Salesforce Lightning org. I executed the same flows org by org to confirm they behaved the same across record types, page layouts and business logic, and triaged defects with the developers and admins.

Sole QA resource, Umbrage

Role-based access testing

Checked profile, role and permission-set boundaries on an enterprise field-operations platform, so each user could reach only the data and actions their access level allowed.

Umbrage

AI-assisted regression

Mapped a partner platform’s screens, flows and behavior from its codebase with Claude Code on the command line, then wrote the suites and test cases in Qase, a tool I proposed and rolled out. Runs go through Seldon, a natural-language visual automation tool, and I send findings straight to the vendor’s engineers.

QA Lead, Umbrage

API testing for Dynamics 365

Built a Postman framework with SQL checks that validated data exchange between Dynamics CRM modules and external integrations. Introduced Playwright as the base for automated regression.

Sole QA resource, Softtek

Leading a team of six

Led six testers for over three years. The QA processes and documentation standards I wrote became the blueprint for client handovers.

QA Lead, Umbrage

How I work

I document what I find, escalate it, verify the fix, and leave the resolution to the developers who own it.

DocumentWhat I find, with steps to reproduce.
EscalateTo the people who own the fix.
VerifyThe fix, before it ships.
Hand offThe resolution stays with its developers.

Where I fit

Umbrage Senior QA Analyst, QA Lead · 2022 to now
Softtek QA Tester to QA Lead · 2015 to 2022

Owning quality for a product

I do my best work owning test strategy from the first test case through UAT, and leading the people who run it.

Distributed teams

I’ve worked with EMEA teams across several time zones on enterprise desktop automation platforms for Mac and Windows.

Automation: Playwright (TypeScript, JavaScript), Postman
API and data: Postman, Swagger, SQL
AI-assisted QA: Claude Code, Seldon, AI test case generation
Test management: Jira, Azure DevOps, qTest, TestRail, Qase, QMetry, Zephyr
CRM platforms: Salesforce Lightning, Microsoft Dynamics 365
Process: Agile, Scrum, Kanban, CI/CD

Hiring for QA leadership?

Pick a time that suits you. Thirty minutes, no prep needed.

Book a 30‑minute call (opens in a new tab) Download CV (PDF)

r.magalllanesp@gmail.com

Or find me on LinkedIn.