"I treat production behavior as the real specification: isolate variables, find root causes, fix structurally so the failure class cannot recur."
|
PostgreSQL & Database Engineering
|
Automation & Data Engineering
Early signal: OBMEP Silver Medal (2016), Bronze (2014), 2x Honorable Mentions; top 0.01% among 18M+ participants nationally. |
name: João Victor Mendes
role: L2/L3 Technical Support Engineer
company: Pedroso Automação # B2B fiscal compliance ERP SaaS
location: União da Vitória, PR, Brazil
specialty: [PostgreSQL, Incident Response, ETL, Windows Server Automation]
clients: 500+ corporate # 1500+ end-users
proof_point: OBMEP Silver Medal # top 0.01% among 18M+ participants
featured_now:
- "receita-cnpj-etl-pipeline # Receita CNPJ ETL + PostgreSQL client classifier"
- "incident-response-runbook # PostgreSQL incident response + NVC + post-mortems"
- "pg-incident-recovery # Windows-first PostgreSQL multi-cluster recovery tool"
open_to: [Support Engineering, Database Engineering, SRE]
contact: linkedin.com/in/mendes-victor| Area | Public artifact | What it demonstrates |
|---|---|---|
| Data engineering | receita-cnpj-etl-pipeline |
Windows-first ETL for Receita Federal CNPJ open data, PostgreSQL staging, large-file classification, sanitized release packaging |
| Incident response | incident-response-runbook |
PostgreSQL severity classification, triage, communication, escalation, and post-mortem structure |
| Recovery automation | pg-incident-recovery |
Safe Windows service recovery boundaries for PostgreSQL crash-recovery scenarios |
| Restore tooling | pg-restore-tool |
Operator-controlled local restore flow with explicit safe/fast/unsafe profiles |
| Deployment automation | windows-postgres-deployment-installer |
Human-reviewed PostgreSQL deployment automation for Windows workstations and small servers |
| Fiscal support utilities | nfe-xml-organizer, tls-fix-erp-updater |
Practical PowerShell utilities around NF-e file handling and Windows TLS registry failure modes |
| Data visualization | one-piece-ratings-timeline |
Static-site data product, source policy, scheduled refresh, and GitHub Pages publishing |
A production-grade PostgreSQL incident response framework that combines:
- WAL disk exhaustion recovery (
pg_walzero bytes free) - SCRAM/MD5 and
pg_hba.confauthentication failures - Connection pool exhaustion and lock contention diagnosis
- Worked post-mortems for both infra and application-layer incidents
- NVC-based client communication and war-room protocols
This is the clearest public artifact of how I approach production systems: diagnose from first principles, document the failure mode precisely, and encode the fix so the class of incident does not recur.
A Windows-first PostgreSQL recovery orchestrator for multi-cluster hosts. It automates the safe parts of post-reboot incident handling:
- discovery of stopped PostgreSQL services
- data-directory resolution from service definitions
- stale
postmaster.pidcleanup pg_controldata-based missing WAL triage- parallel startup with bounded retries
- crash-recovery monitoring and clean handoff back to Windows SCM
- persistent queue files so interrupted runs can resume cleanly
This is the executable complement to the runbook repo: the runbook explains how I reason about incidents; this tool shows how I automate one of the ugliest recovery paths without crossing into unsafe automation.
windows-postgres-deployment-installer and pg-restore-tool cover the less glamorous support paths around PostgreSQL: workstation/small-server deployment, local rebuilds, restore profiles, and operator-reviewed automation. They are deliberately scoped tools rather than platform claims: the goal is to remove repetitive failure-prone steps while keeping destructive choices explicit.
|
FGV — Data Science & Economics (2020-2022) Full-ride OBMEP scholarship |
IFPR — Systems Analysis & Development (2023-2024) Grade A in Mathematics for Computing |
Public artifacts are sanitized: no client data, private hostnames, credentials, or internal support tickets.


