Strategy and risk
Requirements analysis, test design, and risk-based priorities: not everything needs to be tested in the same way.
Senior Software QA Engineer · Milan, Italy
Let's talk about quality,
not just testing.
A pragmatic, risk-oriented QA Engineer focused on product quality. I work with teams to decide where attention matters most, reduce uncertainty, and deliver with greater confidence.
Approach
How I work.
I do not see QA as a final phase, or as the role that finds bugs at all costs. To me, it means understanding the product, challenging assumptions, and helping the team make informed decisions about risk. Automation is a tool: it frees time from repetitive work so the team can focus on what really matters.
My QA approach
I do not start with tests.
I start with questions.
What could go wrong? For whom? How serious would it be? And how can we find out before a release?
The full diagram exists, but in practice my work is closer to an ongoing conversation with product and engineering.
Spoiler: not everything should be automated. And not everything deserves the same level of testing.
01Understand before testing
+
I start with objectives, requirements, impact, and prerequisites: data, access, environments, APIs, and logs. If something is not testable, I clarify why and evaluate useful alternatives - such as a mock - instead of blocking the whole flow.
02Decide what to test
+
Together with the team, I choose the right level of coverage: smoke, regression, end-to-end, integration, API, or UI. Then I define clear test cases and distinguish manual, exploratory, recurring, and automation-candidate tests.
03Execute with evidence
+
Automated suites run in the CI/CD pipeline. Reports feed traceability in Jira, so outcomes do not remain scattered across GitLab, tools, and conversations.
04Improve the system
+
I analyse results and recurring defects to update tests, requirements, and suites. The goal is to reduce risk in future releases.
Skills
Automation
Playwright frameworks in Python or C#, designed to be readable, reusable, and easy to extend.
QA process
CI/CD pipelines, dashboards, and Jira integrations that make quality visible throughout the development lifecycle.
Collaboration
Working with developers, Product Owners, and stakeholders: first understand the problem, then propose a solution.
Challenges tackled
Complex situations,
with a practical contribution.
Refactoring a Selenium suite with Playwright and Python
- The challenge
- A frontend Selenium and TypeScript suite was difficult to read and scale across a QA team with different seniority levels. Flaky tests were also creating false positives.
- My contribution
- I refactored the suite with Playwright to reduce code and increase reliability, and chose Python to make it more accessible to the whole team.
- What changed
- More readable and maintainable tests, a simpler shared foundation for the team, and less noise from unstable results.
Bringing pipeline outcomes into Jira
- The challenge
- Automated tests ran in GitLab, but test cases and Test Executions in the test-management tool were not updated because doing it by hand was seen as wasted time.
- My contribution
- I created an automation that creates a Test Execution on every pipeline run, synchronises test cases, and updates their status automatically.
- What changed
- Pass/fail outcomes no longer stay in GitLab: QA and managers can see each run and use the data for dashboards and KPIs.
When part of a flow is not testable
- The challenge
- Part of a flow was blocked by two-factor authentication.
- My contribution
- Instead of stopping the work, I started with practical questions: why does this API exist, what information does it provide, and can we simulate its response?
- What changed
- We chose a mock for the blocking part and moved forward on the higher-value steps, without pretending to have coverage that was not possible to achieve.
Experience
Professional journey.
Jan 2026 - Jul 2026
Software QA Engineer
iliad · Milan
QA for B2C and Logistics domains. Python automation, TypeScript test refactoring, CI/CD integration, and AgileTest for automated reporting.
May 2024 - Dec 2025
Senior QA Engineer
agap2 Italia · Milan / Lucca
Experience in Betting, Automotive, and High Finance, focused on test automation and product quality.
May 2023 - May 2024
Software Quality Expert | Test Automation Engineer
CCH Tagetik · Lucca
Led and mentored three junior testers; redefined the test process and introduced BDD practices with Robot Framework.
Jan 2021 - Mar 2023
Test Automation & CRM Dynamics 365 Developer
Avanade · Florence
Test automation in an international Playwright project; .NET and JavaScript development on Dynamics 365 CRM and communication of results with Gherkin.
May 2019 - Dec 2020
Functional Consultant Dynamics Business Central
F1 Consulting & Services · Milan
ERP consulting focused on logistics and accounting, functional analysis, and an end-to-end view of the product.
Dec 2017 - May 2019
Technical Consultant CRM Dynamics 365
Avanade · Milan
Dynamics 365 customisation, functional analysis, system testing, and Unified Service Desk maintenance.
Nov 2016 - Nov 2017
Chat Bot Blockly & JavaScript Developer
Sysmo · Milan
Chatbot development, JavaScript, SQL, Excel/VBA report automation, and early cloud projects.
Tools
Tools and technologies.
PlaywrightPythonC# / .NETSpecFlow / CucumberNUnit / JUnitGitLab CI/CDJiraXray / AgileTestREST / SOAP APISQLPostman
What I am looking for
I am looking for an environment where QA is involved early: in requirements discussions, test-strategy decisions, and the creation of tools and processes that help the whole team. I am not looking for total control, but for collaboration and quality treated as a shared responsibility.