Experience
As Process & Quality Coordinator in financial services, I work across process excellence, quality, governance, automation direction, and cross-functional delivery. Through Evorigo, I also remain hands-on with product scope, architecture, software, infrastructure, and security. Together, these roles keep leadership decisions close to operating and technical reality.
Current
Financial services institution
Leads process excellence, quality, governance, and automation direction. Turns transformation priorities into clear ownership, decision routines, standards, and delivery across functions.
Independent venture
Evorigo
Defines product scope and technical decisions, with direct involvement in architecture, software development, infrastructure, security, observability, and release readiness.
Observe how value, information, and decisions move across teams. Map controls, handoffs, exceptions, ownership, and the gap between the documented process and the work people perform.
Turn operating knowledge into standards, prioritization criteria, decision rights, review cadences, and feedback loops that leaders and teams can use in real work.
Choose automation, data, APIs, software, or infrastructure only when the intervention improves reliability, decision quality, control, or scale across the full lifecycle.
Plan communication, capability building, exception handling, observability, support, and controlled change as part of the solution, not as work to discover after release.
Formal systems education and agile leadership study support a practice that keeps operating design, technology, and people leadership connected. Focused courses in data, Power BI, development tooling, and software engineering extend that foundation through applied learning.
Dec 2023 to Dec 2024
Postgraduate Specialization
Pontifícia Universidade Católica do Paraná
2018 to 2021
Technology Degree
Instituto Federal de Educação, Ciência e Tecnologia de Mato Grosso
Make work and ownership visible, establish decision and review routines, then automate only where process stability, risk, and support make the operating case sound.
Structure operational evidence so leaders and systems can use it for decisions, monitoring, reliable services, and analysis that changes what happens next.
Carry a product decision into consistent mobile, web, service, and API implementation without losing the user need, operating constraint, or release boundary that justified it.
Build delivery environments that are repeatable, observable, recoverable, and proportionate to the product risk, team capability, and support commitment.
Define trust boundaries, authentication, data flows, failure behavior, abuse controls, and resilience mechanisms while architecture is still being shaped.
A useful first conversation starts with the real context: what is failing, who owns the consequence, which constraints matter, and what decision needs attention.
