Stack
Grouped by what it is for rather than by language, and each group names where I used it. A list of technologies without that context is just a list.
An in-product RAG assistant for merchant owners at Payway scale, MCP and LLM pipelines for independent clients, and agentic engineering workspaces at Rampy, Teamcubation and Cooperativa Obrera.
Microservices and BFFs in production at Payway and Cooperativa Obrera, and the REST API behind Filomena.
Used across every role listed on this site.
A microfrontend embedded in the Payway merchant portal, the SGA back office, and the Filomena application.
Event-driven ingestion at fintech scale, hexagonal and layered services, and query tuning on exam and permission paths.
Application development on AWS managed services, and containerised workloads I built, configured and diagnosed as a developer — not cluster administration or infrastructure ownership.
Monitoring and access control in production on SGA and Filomena, and test tooling across JVM and JavaScript services.
Agile practice in every role, with the tooling each organisation used.
Production fintech experience at Payway, plus blockchain knowledge in consolidation. Listed as complementary knowledge, not as a primary specialisation.
Cloud and container entries describe application development: building services, integrating managed services, configuring and diagnosing workloads. They do not claim cluster administration, infrastructure provisioning or platform ownership, because that was not my role.
Names appear as text rather than as vendor logos. Redistributing third-party marks on a personal site is restricted by several of those vendors' own brand policies, and a logo would not tell you anything the name does not.