Capgemini Invent
Solutions Architect · Development Architecture
My job is to decide where one service ends and the next begins — and to leave behind a written reason for every line I draw.
What I do here
Design the solution
Architectures for custom builds (Vue, C#, Node.js) and low-code (OutSystems) on Azure and AWS: authentication, persistence, integration and asynchronous processing, with scalability, availability and security in line with enterprise standards.
Write it down
Architecture documents (DSA), reasoned decisions and technical standards. Every design states the alternatives, the chosen one and how to implement it.
Review and govern
Architecture boards with the teams, and design and code reviews against the corporate quality and security gates.
Proofs of concept
Technical POCs to validate patterns before they become standards: Kubernetes deployments, database CI/CD and AI agents built into the development lifecycle.
How a decision travels
from a request to something running- 01 A need arrives A team needs data or behaviour that lives somewhere else.
- 02 Options on the table Two or three ways to draw the boundary, each with a cost.
- 03 The ADR One chosen, written down, with the reasoning attached.
- 04 Review & ship Implementation reviewed against quality and security gates.
Worth naming
- Corporate framework for adopting AI agents across the development lifecycle: RAG indexing of the architecture corpus, deployment model, access, security and integration.
- Phase-based development standards across the lifecycle, covering pipelines, containers and security.
- Solution designs (DSA) for custom and OutSystems applications on the corporate templates.
On this job
- Azure
- AWS
- REST API design
- Vue
- C# / .NET
- Node.js
- Kubernetes
- Database CI/CD
- OutSystems
- Azure DevOps
- AI agents and RAG