Computer Engineer · QA Analyst
I analyse how software
is supposed to work.
And what happens when it doesn't.
Combining functional analysis, software quality and technical depth to understand complex systems beyond the test layer.
Beyond test execution
Quality starts before the first test is executed.
Understanding requirements, business rules, system behaviour and technical dependencies makes it possible to identify risks before they become production problems.
- Understand
- Analyse
- Validate
- Improve
Selected analysis
Functional analysis
From Requirement
to UAT
Turning an ambiguous business request into clear requirements, business rules, acceptance criteria and UAT scenarios.
System analysis
When the payment succeeds,
but the order doesn't.
Investigating a distributed order-processing failure across REST APIs, microservices and asynchronous messaging.
Banking · System analysis
Rejected transfer.
Funds still blocked.
Investigating a SEPA transfer that is correctly rejected by Compliance while the customer's funds remain incorrectly reserved.
Expertise
Analysis
- Requirements Analysis
- Business Rules
- Risk Analysis
- Functional Analysis
- AI-Assisted Analysis
Software Quality
- Functional Testing
- Integration Testing
- Regression Testing
- End-to-End Testing
- AI-Assisted Testing
Systems
- REST APIs
- Microservices
- Event-driven systems
- Logs
Tools & technology
- Postman
- AWS SNS/SQS
- Jira
- Xray
- Generative AI
- Cypress
- Cucumber
- Selenium
About
Engineering mindset.
Quality perspective.
Computer Engineer specialising in QA Analysis, combining functional analysis and software quality with a strong technical understanding of complex systems.
Leticia works closely with Front End and Back End teams, analysing requirements, application behaviour, APIs, microservices and incidents throughout the software lifecycle.
More about Leticia