Brazilian Portuguese language professional with an Information Technology degree. 10+ years in LQA for consumer electronics for major companies. I don't just find bugs: I report them so engineers can fix them faster.
Every defect filed with numbered reproduction steps, annotated screenshots, severity classification, and suggested fixes. This methodology was adopted company-wide and accelerated fix cycles by 40%.
Manual localisation testing across macOS, iOS, Android, Windows, and hardware UI. Functional testing in beta environments for software and apps. 100K+ strings fixed. Process optimization for AI training data. Ready for Cork.
I'm a native Brazilian Portuguese linguist and Localisation QA Engineer with an IT background that lets me bridge the gap between engineering and linguistics. I've spent over a decade finding the bugs that slip through — text expansion on iOS, truncation on macOS, functional failures that only surface when a string is translated into Portuguese.
My approach is methodical: I document every issue with reproduction steps, screenshots, and screen recordings, categorised by severity and type. Engineering teams I've worked with adopted my reporting format company-wide because it accelerated fix cycles by 40%.
I've worked cross-functionally with international QA centres, documentation engineering teams, translators, and project managers — exactly the environment GlobeTech builds. I'm currently developing Python skills for test automation, building on my existing HTML/XML/JSON experience.
Four real-world cases demonstrating systematic reporting, cross-platform testing, functional beta testing, and QA lifecycle management — each directly aligned with the responsibilities in the GlobeTech Localisation QA Engineer role.
High-volume localisation projects for consumer electronics software (macOS, iOS, hardware UI) required systematic testing of Portuguese (BR) strings. Engineering teams were receiving vague bug reports that were difficult to reproduce, leading to slow fix cycles and re-test loops.
Developed a structured reporting methodology: every bug filed with OS version, device model, build number, numbered reproduction steps, and suggested fixes.
PT-BR expansion +30% causing layout failures across platforms.
Test cases per platform, regression passes, screenshots from devices.
Sample test coverage matrix from a multi-platform localisation cycle, showing the systematic approach applied across devices, content types, and issue categories:
| Test Area | macOS | iOS | Android | Print / Docs | Hardware UI | Issue Type |
|---|---|---|---|---|---|---|
| UI String Length / Truncation | BUG | BUG | PASS | N/A | BUG | Functional + Linguistic |
| Text Expansion (PT-BR is ~30% longer) | BUG | BUG | BUG | PASS | N/A | Layout / Functional |
| Cultural Adaptation (date, currency) | PASS | BUG | PASS | BUG | N/A | Linguistic |
| Help Content Consistency | PASS | PASS | PASS | BUG | N/A | Linguistic |
| Special Characters / Encoding | PASS | BUG | PASS | PASS | PASS | Functional |
| Hardware Label Alignment | N/A | N/A | N/A | N/A | BUG | Functional + Layout |
| Terminology Consistency | PASS | PASS | PASS | BUG | PASS | Linguistic |
A software family suite required validation of new features, frequently asked question pages, and updates in beta versions of programs for the Brazilian Portuguese market.
Executed systematic functional testing across beta builds. Each issue documented with annotated screenshots, reproduction steps, and actionable suggestions for engineering teams.
Fragmented QA process for CRM software and chatbot interfaces serving 30,000+ call centre agents caused terminology drift, slow issue resolution, and inconsistent quality across releases.
Led full QA lifecycle: test plan design, execution, bug filing in Jira with numbered reproduction steps, engineering handoff, regression testing, and QA dashboard reporting with structured error taxonomies.
Led the full QA testing lifecycle for CRM software and chatbot interfaces used by 30,000+ call centre agents. Click each phase to explore the approach:
Designed manual test plans covering CRM content, chatbot scripts, and documentation. Defined test scope, entry/exit criteria, test cases by severity, and assigned coverage to 15+ team members. Plans were stored in a shared repository and versioned alongside software builds.
Accommodation already arranged in Ireland. EU citizenship in final stage. Available onsite.
