Tech Lead & Senior Backend Engineer
Payments, fintech and distributed systems.
I'm Bruno. I bring 8+ years of backend engineering across banking and fintech, with hands-on technical leadership from architecture decisions to production troubleshooting.
Open to senior backend and Tech Lead opportunities in Canada.
A payment crosses more than an API.
API contract
Validate intent. Establish idempotency.
Domain & state
Own the transition. Persist the evidence.
Provider boundary
Handle uncertainty. Reconcile the result.
Professional experience
My work connects implementation detail with the architecture and operational decisions around it.
Full career historyJava and Spring Boot services connecting banking, card and crypto providers. Clear contracts, explicit transaction states and careful handling of asynchronous callbacks.
Moving established systems toward AWS and container-based delivery, with attention to migration sequencing, CI/CD and operational continuity.
Architecture reviews, ownership boundaries and delivery planning. I stay close to implementation and help teams resolve risk before it becomes expensive.
Engineering studies
Independent architecture studies with interactive models and API contracts. Each explores a specific design problem, its failure cases and its trade-offs.
Separating payment intent from provider attempts, so retries and late confirmations don't create a second charge.
What happens when the provider accepts a payment, but the response never arrives?
Architecture · API sketch · Tested model
Holds, settlement and reversals modelled as balanced journal entries, not destructive balance updates.
Can every balance change be explained, even after a reversal?
Architecture · API sketch · Tested model
Versioned decisions with explicit ownership, review boundaries and a record of the trade-offs a team accepted.
Six months later, can the team still explain why a decision was made?
Architecture · API sketch · Tested model
How I work
I care about clear ownership, written trade-offs and delivery plans grounded in the actual system. I mentor through implementation and keep architecture connected to what the team can operate.
More about meA timeout is not a declined payment. I prefer clear state transitions, stable identifiers and enough history to reconstruct what actually happened.
A service boundary should clarify ownership and change. I challenge abstractions that add coordination without making the system easier to maintain.
Retries, reconciliation and operational visibility belong in the design discussion. Recovery should be a procedure the team understands.
Occasional thoughts on engineering and the work around it.
Posts & field notesStart a conversation
I'm interested in senior backend and Tech Lead roles across fintech, payments, SaaS and platform engineering in Canada.