Fernando DamasioSenior QA Engineer · SDET

I find the riskbefore it finds your users.

For over seven years I have worked on quality in mission-critical financial systems. I connect automation, APIs, performance, backend, and AI agents to turn uncertainty into a release decision.

Explore my workDownload résumé

7+ years in software quality
Mission-critical financial systems
Java · Kotlin · Selenium · Cucumber
Backend in Java, Python, and Node.js

Abstract composition of quality engineering: automation, API contracts, performance metrics, and agents

API CONTRACT verified

CRITICAL PATHScovered

I turn software risk into confidence.

years engineering software quality

70%

more efficiency from a Python tool I developed

API → UI

quality from the contract to the final experience

How I think

I start with risk, not a script.

Before I automate, I understand the product, its impact, and what cannot fail. Then I turn that reading into coverage, code, and observability.

quality-pipeline.yml

PASS

01risk_model: critical_paths

02api_contracts: verified

03regression_suite: green

04observability: connected

05release_confidence: ready

Understand

I translate product and business into verifiable behavior.

Prioritize

I focus coverage where risk and impact are highest.

Automate

I build fast feedback across UI, APIs, data, and regression.

Observe

I connect testing, performance, and production to keep learning.

Skills in context

I would rather show how I work than list tools.

Pick a skill to see how I apply it and what evidence it produces.

I start by asking what cannot fail, and only then write a test.

How I apply it

I map the impact of each flow before deciding where to invest coverage.
I turn business rules into verifiable behavior, not click scripts.
I record the risk I chose to accept, so the release decision stays explainable.

Where I built thisLarge-scale financial systems · Stefanini

Evidence I producerisk → coverage

01flow: account-to-account transfer02impact: financial · irreversible03risk: duplicate on retry → high04risk: error message leaking data → medium05decision: contract + concurrency before UI

Test designRisk analysisBDDAcceptance criteria

Experience

I built my view of quality inside systems that cannot fail.

2019 — 2026

Mar 2022 — Present

Senior SDET / QA Engineer

Stefanini Brasil Large-scale systems · financial services

I develop Java and Kotlin automation with Selenium, design BDD scenarios in Cucumber and Gherkin, run load tests with JMeter, and validate APIs. I maintain third-party automation and legacy code with Git and code review, including work on an Itaú project, and use Dynatrace to observe system behavior throughout test cycles.

Java · Kotlin · SeleniumCucumber · GherkinJMeterDynatraceCode review

Dec 2019 — Mar 2022

QA Engineer / Test Automation

Global Hitss API testing · cloud environments

I automated and validated REST API tests in cloud environments with a focus on data consistency, implemented regression testing and critical validation for production systems, and developed an internal Python tool that increased the team's data-analysis efficiency by 70%.

REST APIsPythonRegressionData consistency

Jan 2019 — Dec 2019

Software Developer

Foursys Backend development · Banco Next

I developed Java and Spring Boot backend services for the Banco Next mobile application and contributed to the project's initial phases, directly supporting the product launch inside an agile squad.

JavaSpring BootAgile squad

Case studies

I use my projects to turn knowledge into products.

Every project below is mine. I describe the problem, the decisions I made, and the risks I had to handle.

Current stage: Completed project

CyberAudit Pro

I built a SaaS that consolidates public security signals about a domain and turns them into a report a non-technical reader can act on.

Problem

Security signals exist across many public sources, but they arrive scattered, in different shapes, with no sense of priority.

My contribution

I am the sole developer. I implemented authentication, the external integrations, the security score, branded PDF reporting, and the Linux server operation.

Engineering decisions

I isolated every external integration behind its own layer, because each API has different limits, latency, and error shapes.
I treated third-party downtime as an expected report state rather than a product failure.
I separated tenant data from the first version instead of paying that debt later.

Risks I had to handle

Data leaking across tenants
A report generated from partial sources without telling the user
An external dependency going down mid-audit

Quality Lab

Enter my Quality Lab. Here, quality stops being a claim and becomes a decision.

Investigate simulated incidents, choose a strategy, and see how I connect risk, engineering, and product. Then try my local feature analyzer.

INTERACTIVE EXPERIENCE · REAL QUALITY DECISIONS

Do not just read what I do. Make a decision with me.

Enter an engineering control room, investigate failure signals, and see how I turn risk into release confidence.

QUALITY SYSTEM / ONLINEFD / LAB 02

Select a station or choose a guided experience.

LOCAL DEMO · NO DATA IS SENT

01Context

02Risks

03Coverage

04Validation

This is the same path I would follow in a refinement session: understand, map risk, define coverage, and validate the output.

This demo runs entirely in your browser, using rules I wrote. There is no external model call and nothing is transmitted.

FERNANDO / QUALITY AGENT

LOCAL DEMO · NO DATA IS SENT

Ask about my experience

I turn recurring risks into automated feedback using Java, Kotlin, Selenium, BDD, and API validation. My priority is a suite that is readable, stable, and useful for release decisions.

Source in my résumé: Experience · Stefanini

Fernando Damasio · Senior QA Engineer · SDET

About me

I build confidence because I understand both sides of software.

I began my professional journey building backend software in Java and Spring Boot. Over the years, I deepened my work in automation, APIs, performance, and mission-critical financial systems.

Today I combine both worlds: I understand how software is built and apply quality engineering to make it more reliable, observable, and ready to evolve. In my own products, I practise that from the first commit to the deployment.

Education

Software Quality Engineering — EBAC
Technical Diploma in Systems Analysis — UNINOVE

Languages

Portuguese — native
English — intermediate (working technical reading)

Let's talk

If quality is an engineering decision, I want to be part of it.

I am open to conversations about QA, SDET, automation, development, and products that need to grow with confidence.

I read every message and reply personally.

Email me

RésuméPortuguês English