Resume / CV

Context: An own initiative, not a client engagement. Since July 2026, research, drafting, operations monitoring and reporting in my own business run through a team of specialised AI agents. Each role has its own profile, its own Atlassian account and its own Slack channel.

My Role

Design, build and operation: role boundaries, tool access via MCP, workflow development in n8n, running the LLM gateway on my own server, and the approval and documentation rules the agents work under.

Highlights

• Seven agent roles, each with its own profile, Atlassian account and Slack channel
• 34 active n8n workflows: 11 Slack agents, 12 scheduled jobs, 10 sub-workflows, 1 chat
• 615 workflow executions between 1 and 15 August 2026, 7 of them failed — 98.9 % success rate
• Approval workflow as a hard rule: research and drafts autonomous, publishing and sending only after sign-off
• Architecture decisions recorded as ADRs in a decision log, not just implemented
• Own LLM gateway (LiteLLM) on own infrastructure, model chosen per role rather than one for all

Stack

Claude (Opus/Sonnet) · MCP · n8n · LiteLLM · Slack · Jira · Confluence · Baserow · Docker

Context: Publicly available AI assistant on jacomeit.de, in production since July 2026. A dedicated Symfony module of 43 classes, connected to a self-hosted LLM gateway rather than directly to a vendor.

My Role

Sole design and implementation — module boundaries, streaming, abuse protection, operations, data protection and AI disclosure under Article 50 of the EU AI Act.

Highlights

• Response streaming via server-sent events, connected to a self-hosted LiteLLM gateway
• Prompt injection prefilter ahead of every paid call, plus rate limiting and signed session tokens
• Two-stage kill switch: env flag and admin toggle, shutdown without a deploy
• Versioned system prompt managed through the admin UI, with a code fallback
• Automatic deletion of sessions after 90 days as a scheduled job
• Article 50 EU AI Act disclosure implemented on the day it took effect: server-side transparency instruction on every prompt, disclosure before the first user input, dedicated section in the privacy policy
• 22 test classes in the module, PHPStan level 8 with no exemptions

Stack

PHP 8.5 · Symfony 8.1 · LiteLLM · Server-Sent Events · Doctrine · Stimulus · PHPUnit · PHPStan

Context: A business line built together with a partner, aimed at owner-run SMEs in the Bremen region. The goal is reusable automation building blocks with a fixed delivery format rather than bespoke project work. As of August 2026: concept complete, first client installation still pending.

My Role

Technical building blocks and feasibility: selecting the components, the operating model, effort and pricing calculations, and the legal assessment.

Highlights

• Full concept documented: use case catalogue, technical building blocks, delivery format, business model and pricing, legal and risk, go-to-market
• Business case for sales conversations fully calculated, every figure sourced rather than estimated
• External AI second opinions are captured and reviewed in a structured way, not simply adopted
• Same technical base as my own operations — whatever ships has been running here first

Stack

n8n · LLM gateway · Baserow · Docker

Context: Full-time engagement at the energy provider EWE AG from February to June 2026 in a 3–5-person team: introducing event-driven architecture (EDA) and gradually retiring PHP legacy.

My Role

Symfony developer focused on EDA adoption. Designing and implementing asynchronous processing with Symfony Messenger and contributing to the breakdown of grown legacy structures.

Highlights

• Introducing event-driven architecture via Symfony Messenger
• Asynchronous command processing
• Step-by-step migration from PHP legacy to Symfony
• Establishing clean domain boundaries in the new stack

Stack

Symfony · PHP · Symfony Messenger · Event-driven Architecture · CQRS · Async Command Processing

Context: Almost 2 years on an 11-person team at a German shipbuilding company. Step-by-step migration of a grown legacy PHP system to Symfony, partly in a classified (Verschlusssache) environment.

My Role

Backend-leaning fullstack work on legacy modernization and selective greenfield migration to Symfony 5+. Shared responsibility for complex database access, asynchronous processing and frontend modules.

Highlights

• Extending & modernizing a complex legacy PHP system
• Selective migration to Symfony 5+
• Complex Oracle SQL for business logic & reporting
• AMQP/RabbitMQ messaging for asynchronous processing
• Custom JavaScript/ExtJS frontend modules
• Compliance, resilience & security training (classified)

Stack

PHP · Symfony 5+ · Oracle · RabbitMQ/AMQP · JavaScript · ExtJS · Jira/Kanban

Context: Working in a 2-person team on a community platform (API, frontend, admin + WebSocket service) built on Symfony.

My Role

API & backend feature focus including WebSocket extensions. Lead on the Docker migration of the whole system. Occasional frontend work.

Highlights

• Docker migration of the full Symfony stack (API, frontend, admin, WebSocket)
• Extensions to the in-house Symfony API
• New WebSocket features for real-time communication
• Microservice setup, GitLab workflow

Stack

Symfony · PHP · WebSockets · Docker · GitLab · Microservices

Context: 18 months on an 8–9-person team building a headless platform for a cross-regional public-sector authority. Symfony API + React frontend, CQRS and event-driven architecture.

My Role

Backend focus: API architecture, auth layer and test coverage. Selective contributions to the React frontend. Code reviews & tech-daily sparring.

Highlights

• Extending & modernizing the Symfony 5+ API in a CQRS environment
• Event-driven patterns with Symfony Messenger
• Custom auth via JWT, DTOs & TransferModels
• PHPUnit coverage consistently > 98.3%
• Microservice architecture, heavy use of design patterns

Stack

Symfony 5+ · PHP 8 · CQRS · Event-Messenger · JWT · React · PHPUnit · Docker · XDebug · Scrum/Jira

Context: Follow-up to the 2019 theme build. Modernization in a 2-person team to meet current SEO/SEA requirements and performance standards.

My Role

Refactoring & modernization of the existing custom theme — responsible for code modernization and SCSS migration.

Highlights

• Migrated from Bootstrap to plain SCSS/Sass
• PHP code modernized to >= 7.4
• SEO/SEA, responsive behavior & performance updated
• Kanban workflow

Stack

WordPress · PHP 7.4+ · SCSS/Sass · Kanban

Context: Return to the dev team — this time with a multi-brand focus across Parship and ElitePartner. 5-person team, mostly pair programming.

My Role

Custom WordPress theme and plugin development across multiple brands, including Gutenberg blocks and per-brand theme customizations.

Highlights

• Cross-brand WordPress plugin development
• Custom Gutenberg blocks for editorial & marketing
• Delivery via GitHub & private Packagist
• Docker containerization & CI/CD with Jenkins, end-to-end pair programming

Stack

WordPress · Gutenberg · PHP · React · Docker · Jenkins · GitHub · Composer/Private Packagist · Jira

Context: Follow-up engagement to the previous project. Continued development of the booking & landing page system on the Symfony 5 stack.

My Role

Solo continuation per client requirements, run alongside my main engagement at the time.

Highlights

• Feature extensions on the Symfony 5 system
• Expansion of the Twig templating layer
• Continued clean separation between public & admin layers

Stack

Symfony 5.2 · PHP 8 · Twig · Doctrine

Context: After an insurance incident, the voucher download system of a music label & artist marketing agency had to be rebuilt from scratch. Solo engagement.

My Role

Full backend & frontend ownership for phase one (dynamic delivery). Architecture, implementation and rollout end-to-end.

Highlights

• Symfony 5.2 greenfield relaunch
• Dynamic Twig landing pages mapped to custom project URLs
• Download streaming via HTTP sockets based on configuration
• Clean architectural split: dynamic delivery + later admin area

Stack

Symfony 5.2 · PHP 8 · Twig · Doctrine · HTTP sockets

Context: 9 months on a 6-developer team working on the Parship and ElitePartner brands. Marketing sites + community forums.

My Role

Fullstack across two platforms: custom WordPress themes/plugins for brand sites and custom Xenforo add-ons for the community area. Mostly pair programming.

Highlights

• Custom WordPress theme with custom Gutenberg blocks (PHP/React)
• Multiple custom WordPress plugins
• Complex Xenforo add-ons for the community
• Test-driven plugin development with CodeCeption & PHPUnit

Stack

WordPress · Gutenberg · PHP · React · Xenforo · CodeCeption · PHPUnit · Docker · Jenkins · Composer/Private Packagist · GitLab · Jira/Scrum

Context: Marketing theme relaunch for one of Germany's largest hosting providers. Solo engagement.

My Role

End-to-end theme development — deliberately minimizing third-party plugins for full control over performance & maintainability.

Highlights

• Responsive layout with Bootstrap 4.2
• Custom Gutenberg blocks instead of third-party libraries
• Tailored shortcodes for editorial workflows
• SEO & performance optimization

Stack

WordPress · PHP · Gutenberg · Bootstrap 4.2 · SCSS