Skip to content
Projects

Three portfolio reference implementations built to support serious backend and Tech Lead conversations.

These are clearly labeled portfolio projects, not employer production case studies. The value is in the system design, trade-offs, operator surfaces, and the kinds of questions they help Bruno answer in a hiring loop.

Extraction-friendly structure

Each case study is designed so the concept could later be split into standalone repositories for backend services, admin surfaces, and shared packages if needed.

Case Studies

Payments, money movement, and architecture decision-making represented as reference builds.

Together, the projects cover fintech domain depth, distributed-systems thinking, and the technical-lead judgment involved in shaping systems that operators can actually live with.

Payments infrastructurePortfolio reference implementation

Payment Orchestration Platform

A reference implementation for multi-provider payment flows, retries, reconciliation, and operator visibility.

Designed as a realistic internal payments platform that routes transaction intents through multiple PSP connectors while keeping idempotency, auditability, and operational control first-class.

Core services

6

Transaction states

14

Recovery model

Retry plus DLQ

JavaSpring BootPostgreSQLKafkaRedisDockerAWSOpenTelemetry
Illustrative demo dataReference UI for the case study, not employer production telemetry.

Sample auth p95

182 ms

Sample queue depth

12

Sample mismatches

2

Illustrative transaction timeline

reconciliation-ready

Intent received

Idempotency key validated

Connector selected

Provider B routed after fallback rule

Webhook matched

Authorization confirmed and persisted

Settlement batch

Awaiting daily reconciliation

Illustrative connector health

Provider AHealthy
98.6%
Provider BDegraded
91.8%
Provider CHealthy
99.1%
Ledger and consistency systemsPortfolio reference implementation

Money Movement and Ledger Simulator

A reference implementation for holds, releases, settlements, reversals, and double-entry balance logic.

A portfolio system focused on the difficult parts of financial correctness: holds, releases, reversals, settlements, pending balances, traceability, and failure recovery across distributed services.

Ledger guarantees

Double-entry

Balance views

Available plus pending

Event integrity

Outbox pattern

JavaSpring BootPostgreSQLKafkaDockerAWSPrometheusGrafana
Illustrative demo dataReference UI for the case study, not employer production telemetry.

Illustrative wallet position

double-entry

Sample available

$ 124,880.43

Sample pending

$ 18,430.12

Hold

Card authorization reserved funds

Settlement

Posting confirmed to clearing account

Projection

Balance view caught up after replay

Illustrative event lineage

movement.created

sample-transfer-91eea2

ledger.posted

sample-journal-2041

projection.updated

sample-wallet-e4a8

settlement.completed

sample-batch-2026-03-21
Technical leadership platformPortfolio reference implementation

Architecture Decision Intelligence Hub

A reference implementation for ADRs, RFCs, system boundaries, risk tracking, and operational learnings.

A tech-lead portfolio project that focuses on architectural judgment, decision records, and the organizational memory that helps engineering teams scale sanely.

Knowledge domains

5

Primary workflows

ADR plus RFC plus risk

Primary value

Decision clarity

Next.jsTypeScriptPostgreSQLSpring BootSearch indexingMarkdownDocker
Illustrative demo dataReference UI for the case study, not employer production telemetry.

Illustrative decision feed

ADR plus RFC

ADR-041

Adopt event sourcing only for settlement stream

RFC-018

Rate limiting policy for partner APIs

Risk-007

Single-team ownership on payment gateway

Illustrative system boundaries map

Payments Core

Owned by Platform team

Risk Engine

Owned by Fraud squad

Ledger

Owned by Finance systems

Observability

Owned by Developer platform

Interview utility

Each project is written to support technical interviews, recruiter screening, and deeper architecture conversations without pretending to be employer work.