Backend Software Engineer
Matheus
Henrique
I build the backend systems that large organizations depend on — enterprise Java, fiscal integrations, and infrastructure engineered for environments where failure is not an option.
- ROLE
- Backend Node
- ENV
- Production
- FOCUS
- Enterprise Systems
Four layers of a working system
The way I think about backend work — from the integration edge down to the reliability guarantees that keep production alive.
Enterprise Integration
Moving data reliably between systems that were never designed to talk.
Systems built for production
Real engineering from regulated, high-volume environments. Each one is a live case study — hover the diagrams to trace the flow.
Brazil Tax Reform Compliance Engine
THE PROBLEM
The 2024 tax reform introduced new tax categories (IBS, CBS, IS) that had to be applied correctly to every electronic invoice — in a regulated environment where an invalid document has direct financial and legal impact.
THE APPROACH
A validation-first pipeline: invoices are parsed on intake, run through a rule engine encoding the new fiscal model, persisted to Oracle with a full audit trail, and reconciled against SEFAZ and MasterSAF endpoints.
- Validation rule engine for IBS / CBS / IS tax codes under the 2024 reform
- Handles a high daily volume of NF-e documents with compliance guarantees
- Integrated with SEFAZ and MasterSAF API endpoints
XML Integration Tool for Fiscal Workflows
THE PROBLEM
Correcting fiscal documents meant manually intercepting payloads through Burp Suite and Postman — slow, fragile, and only doable by engineers, which bottlenecked the tax team.
THE APPROACH
Parse the integrator payload into a DOM, expose it through a structured XML editor anyone can use, then recompile and dispatch the corrected document straight to the MasterSAF API over an authenticated request.
- Replaced the manual Burp Suite / Postman correction process
- Full XML document traversal with structured node editing
- Authenticated POST dispatch to MasterSAF with the recompiled payload
SAP ↔ Oracle Bidirectional Data Bridge
THE PROBLEM
SAP and Oracle held overlapping financial data with different schemas. Keeping them consistent by hand risked drift, and drift in financial records is not an option.
THE APPROACH
A sync layer with idempotent operations and explicit conflict-resolution strategies moves records both ways, maps schema mismatches automatically, and feeds a reconciliation view for reporting.
- Idempotent operations with explicit conflict-resolution strategies
- Handles schema mismatches between SAP and Oracle without manual work
- Automated reconciliation reporting into Power BI dashboards
Engineering in the background
Most of what I build never shows a UI. It runs quietly inside large organizations — parsing invoices, reconciling ledgers, moving data between SAP and Oracle, keeping fiscal systems compliant.
The interesting problems are rarely the algorithms. They're the integration boundaries, the data contracts, and the edge cases that only surface in production. I've spent years learning to see them early.
More about me- location
- São Paulo, Brazil
- experience
- 4+ years
- domain
- Enterprise · Fiscal
- languages
- Java · Python · TS
- database
- Oracle · SQL
- status
- Open to roles
Let's build something reliable.
Available for backend and software engineering roles — Java, enterprise integrations, and systems that have to stay up.
mattenglish2177@gmail.com