QA · Localization · IT Support · Automation
Technical professional with a background in Systems Analysis and Development and hands-on experience in troubleshooting, test execution, localization, scripting, and technical documentation.
I build practical tools, investigate problems from both user and technical perspectives, and document the path from an imperfect first version to a reliable result. My current focus is software and game QA, Brazilian Portuguese localization, and automation for operational workflows.
システム分析・開発を学び、ITサポート、QA、ローカライゼーション、自動化に取り組んでいます。現在はゲームQA、ソフトウェアテスト、ブラジルポルトガル語へのローカライズを中心に、実践的なプロジェクトを開発・改善しています。
English-to-Brazilian-Portuguese game localization case study covering UI, missions, dialogue, system messages, terminology consistency, in-game validation, and linguistic QA.
Localization LQA Game QA Documentation
PowerShell toolkit for Windows server administration and repeatable operational routines. Includes bilingual documentation and a practical guide for adapting the project with proper attribution.
PowerShell Windows Server Automation Operations
An academic Python data-analysis project redesigned as an Excel add-in prototype. It reviews and standardizes spreadsheet data, generates charts, and compares current results with imported historical datasets.
TypeScript Office.js Data Quality Excel
Modern C++20 reconstruction of a legacy XBT tracker for Windows 11 and Linux. The project replaces a broken Windows port with a tested Winsock/POSIX architecture, modern CMake, CI, and security documentation.
C++20 Winsock Networking CMake
| Area | Experience |
|---|---|
| QA | Functional testing, reproduction steps, exploratory testing, usability review, bug reporting |
| Localization | EN → PT-BR adaptation, terminology consistency, contextual review, linguistic QA |
| Support | Windows, hardware/software diagnosis, issue isolation, user-oriented troubleshooting |
| Automation | PowerShell, Python, workflow utilities, repeatable operational processes |
| Development | C++, TypeScript, JavaScript, HTML/CSS, Git, technical documentation |
- Reproduce and isolate the problem before changing the system.
- Keep user impact and technical evidence in the same report.
- Prefer reviewable automation over hidden side effects.
- Preserve project history while making the current version useful.
- Document limitations honestly instead of presenting prototypes as production software.
Opportunities in software QA, game QA, localization QA, PT-BR localization, technical support with testing responsibilities, and junior technical roles where analytical thinking and clear documentation matter.
Building reliable things from unreliable starting points — which, judging by these repositories, has become a specialty.