Experience

Problems I have helped teams solve

These examples focus on the work and leave company or product names out. They show how I have helped make complex software easier to change and teams more effective.

Aligning architecture across product teams

Current focus · Braga, Portugal

Problem: Several teams were evolving connected services with different assumptions about boundaries, quality and long-term ownership.

What I did: Supported architecture direction, reviewed technical decisions, raised delivery risks early and created reusable engineering patterns. Design reviews and mentoring helped the teams understand and apply those decisions themselves.

Impact: Teams had a more consistent technical direction, clearer trade-offs and a safer route for modernising services at organisational scale.

Improving delivery without losing engineering quality

Previous focus · Lisbon, Portugal

Problem: Pressure to deliver made it easy to push quality, automation and operational readiness aside.

What I did: Worked hands-on with Java and distributed systems, strengthened CI/CD pipelines and encouraged TDD, SOLID, Clean Code, pairing, code review and observability. The engagement also included facilitating continuous improvement.

Impact: Engineering practice became more visible in daily delivery. Teams could make smaller, safer changes with fewer surprises.

Connecting digital platforms to external services

2019 · São Paulo, Brazil

Problem: A digital platform depended on several external providers and internal systems, making integrations, releases and production support difficult to coordinate.

What I did: Designed solution architecture and data models, developed REST and service integrations, coordinated delivery tasks and supported deployments and production issues.

Impact: The team had clearer integration boundaries, more dependable releases and a stronger basis for extending the platform.

Making software delivery more repeatable

2013–2019 · São Paulo, Brazil

Problem: Project delivery depended too much on manual effort, individual knowledge and processes that had grown around the work.

What I did: Managed projects from feasibility to implementation, introduced Kanban and Scrum practices, created a reusable PHP framework and improved system integrations and data flows.

Impact: Average source-code production time fell by 40%, delivery became easier to organise, and business-critical data became more reliable.

Translating business requirements into working systems

2008–2013 · São Paulo, Brazil

Problem: Teams needed to adapt enterprise processes and customer-facing systems while working with changing requirements and older technologies.

What I did: Gathered requirements, mapped workflows, managed estimates and deadlines and contributed directly to development, testing, integrations and support.

Impact: Projects moved from unclear needs to usable software with better alignment between stakeholders and the delivery team.