Arthur Liebhardt

Technical depth meets business relevance. Over a decade of building end-to-end applications across cloud platforms, paired with a founder's perspective from both startup and enterprise contexts. I lead cross-functional initiatives that translate complex AI capabilities into tangible solutions, building comprehensive demo storylines across multiple products and shaping their future direction for executive audiences.

Proven track record with AI systems. From contributing to SAP's Document Grounding Service , where I helped build the pipeline API for automated document indexing and RAG in SAP AI Core, to shipping the SAP-RPT-1 Playground for TechEd, I've worked across the full AI product lifecycle. Delivering several product and security standards to achieve a compliant software product release within 4 weeks, a process that normally takes 6 months or more.

Builder by default. I've shipped 9 SaaS products and several enterprise projects at SAP. The SaaS products I build on my own time aren't side projects; they're how I stay sharp. I go from idea to production solo, handling architecture, backend, AI integration, billing, and deployment. This constant cycle of shipping keeps me close to what developers and end-users actually need, and gives me a practical edge when advocating for any AI platform.

AI-native developer. I've been building with code generation tools since day one, from GitHub Copilot and OpenAI Codex to Cursor, Claude Code, and beyond. This isn't something I bolted on recently; it's been part of my workflow since these tools first shipped. That hands-on depth is exactly what powers the Global Agent-Assisted Coding Initiative I now lead at SAP: I don't just evangelize these tools, I use them daily to architect, prototype, and ship production software. It gives me credibility with developers and a practical lens when advising executives on what AI-assisted engineering actually changes.

Startup speed, enterprise scale. Co-founding si:cross taught me to ship with urgency, prioritize ruthlessly, and coordinate across time zones in async-first teams. At SAP, I brought that same energy into a complex enterprise environment, aligning stakeholders and delivering under pressure on a regular basis. I move fast in both worlds.

Builder who brings people along. Leading SAP's global Agent-Assisted Coding Initiative, running enablement sessions, and speaking at events like Devtoberfest comes naturally to me. I build trust across developer teams, decision-makers, and executives through a proactive, hands-on approach that drives product adoption and long-term engagement. I'm fluent in German and English and thrive in the space where advanced AI needs to become accessible and impactful for real businesses.

I want to be upfront: I'm not currently based in Munich and wouldn't be able to commit to three fixed office days per week in Munich. But I want to make the case that this doesn't have to be a limitation, and that a flexible setup would let me do my best work.

Remote is where I'm most productive. My entire career has been shaped by remote-first work. I co-founded and ran si:cross with a fully distributed team across time zones, I've shipped high-stakes projects at SAP while working remotely, and every SaaS product I've built was done from my home office. I know how to structure my day, communicate proactively, keep things visible, and deliver without anyone having to check in on me.

In-person when it matters most. I'm absolutely willing and available to travel to Munich regularly, for team workshops, planning sessions, sprint kicks, customer meetings, or any moment where being in the room makes a real difference. I've done this at SAP for years: working remotely as a default, then showing up on-site for the moments that count, like preparing demos with cross-functional teams under tight deadlines.

Reliable means reachable, responsive, and shipping. For me, reliability isn't about being seen at a desk; it's about consistent output, clear async communication, and being available when the team needs me. Whether it's a Slack thread, a quick huddle, or a deep-dive working session, I'm always reachable during working hours and often beyond.

I'd love to find a setup that works for both sides. I'm confident that with the right rhythm of remote focus time and intentional in-person collaboration, I can deliver at the level this role demands, and then some.