Senior Software Engineer — end-to-end ownership & AI-native delivery
Java/Spring · TypeScript · Node.js · React. Two decades of architecture behind it. I'm looking for a product area to own end-to-end as a high-impact individual contributor.
Download my résumé
Senior Engineer résumé (EN)Senior Engineer résumé (PT)Not hiring for a single seat, but for someone to run the engineering side of your product end to end? That's the fractional engagement — same track record, part-time.
The numbers
repositories under my ownership, 3 in active development
client-reported issues a month (was ~100)
between production releases
automated tests (was 70)
Marked ● = measured from git, CI and the test suite.
What I own
I build delivery machines. I take over software that has become unsafe to change — or start systems that must never get there — and engineer an autonomous delivery operation around it: specs, tests, CI/CD, and agentic workflows that consume stakeholder requirements and produce reliable software.
I have run this migration in both directions — decomposing an EJB monolith into five services at Muvz, consolidating services back into a single backend at MedEspecialista — which is where a practical sense of what justifies a service boundary comes from. The machine's components were people then and AI agents now; the engineering is the same. Two decades of Java/Spring and TypeScript/React architecture back it.
Ownership
I take it over and engineer an autonomous delivery operation around it — requirements go in, reliable releases come out, and the technical and management overhead stops being yours.
Async operation
Requirements, architecture decisions, and backlog live in the repository as a single source of truth, with proactive high-signal updates instead of status calls.
Let's talk about it.
Thirty minutes, no slides. Tell me what you need owned; I'll tell you whether I'm the right person for it.