Adobe wants vs. what I actually have
15+ years; currently owning digital content and campaigns at Raiffeisenbank Rigi.
Strategy, governance and multi-channel discoverability in a regulated environment.
Interviews, problem framing and validation across 5+ launched products.
Journey design across digital and personal banking; CAS UX Management at HSLU.
Full lifecycle ownership: discovery, prioritisation, launch, iteration.
Two AI-native products: EndlichSichtbar and the GEO Diagnostic Agent.
Claude-based agent with tool use and prioritised output — small scale, not enterprise.
Be able to draw my agent's loop on a whiteboard: signals → context → analysis → tools → recommendation → approval → measurement. Name one thing that broke and how I fixed it.
Daily use since vocational training; semantic markup, layout, responsive.
Write and debug it in my own products; not a framework engineer.
Refresh: async/await vs promises, event loop in one sentence, fetch with error handling, DOM manipulation, and why blocking JS hurts INP.
WordPress-level PHP; SQL for my own product data.
Be able to explain a JOIN out loud and why you would model content as related tables rather than one wide table.
Authoring, publishing, workflow and content operations on an AEM-based site.
Nail the vocabulary: page, component, template, content fragment, experience fragment, DAM, workflow, publish. Say which of these I have personally touched.
No Java, Sling, OSGi or custom component development.
One clean sentence declining the claim, then redirect to what I do bring. Know roughly what a component's dialog and the author/publish split are, so the conversation can continue.
Understand the concepts from SEO work; details are rusty.
LCP / INP / CLS: definition, good threshold, two typical causes, two fixes. INP replaced FID in March 2024.
Practised on real sites: structure, metadata, internal linking, intent.
Prepare one example where SEO analysis changed a content decision, with numbers.
Building a diagnostic agent around LLM visibility, citations and authority signals.
Define GEO crisply, name three signals that influence being cited by an LLM, and say honestly which parts are still hypotheses.
No experience with large codebases, release trains or production on-call.
Prepare the honest framing plus a question for Dirk about how product engineers and platform engineers split work on his team.
Claude and Lovable daily, with review, testing and iteration discipline.
Own clients, bank stakeholders, pilot customers for EndlichSichtbar.
Founder since 2015 — most work started without a defined brief.
Problem to working prototype in days, repeatedly, with real users on the other end.
Interview ready = every red row has a sentence I can say calmly, without apologising and without inflating.