Technical Customer Success · Product · Berlin
I bridge the gap between complex technical products and the people who use them — turning integration chaos into measurable business results.
About
My career started at 16 writing code — and never fully stopped. Over the years, I moved through web development, design, communications, and performance marketing, always ending up at the same intersection: where the technical and the human meet.
In Berlin, I spent over 2.5 years as a Performance Analyst working with user acquisition, behavioral data, and publisher management. I don't just report on KPIs — I build solutions. I automated monitoring systems, investigated MMP logs, and managed daily feedback cycles with ad publishers and internal teams to fix problems at the root.
I recently completed a React course at ReDI School Berlin. My edge is that I speak engineer, speak marketer, and speak client — often in the same meeting.
How I work
Most support issues are symptoms. I dig into data, trace the integration, and find what's actually broken — not just what's visible on the surface.
I've worked with engineers, designers, marketers, and executives. I adapt how I communicate so nothing gets lost between teams and clients.
When I identify a recurring problem, I automate or systematize the solution — so it doesn't need to be solved again next week.
Work
Three situations where I had to bridge a gap — between data and decision, between product and client, between process and reality.
Performance · Publisher Management · Technical Troubleshooting
A key client flagged dissatisfaction as purchase rates declined. Working from 3 years of historical reports, I identified underperforming traffic sources, renegotiated with publishers, and managed daily feedback cycles — including live incident response when new sources triggered rejection spikes.
A client's display campaigns had seen purchase rates stagnate and decline. When they flagged dissatisfaction, we requested historical data — and received 3 years of reports (2023–2025) covering every source, sub-source, and creative. The scale of the data made the patterns visible: certain traffic sources had quietly degraded over time while budget kept flowing to them.
I analyzed KPIs across the full historical dataset — Purchase Rate, Session Rate, Retention, and Rejection Rate — to identify which publishers and sources had consistently delivered quality since 2023, and which hadn't. I cut budget from low-quality publishers and worked directly with the best-performing ones to reactivate proven sources or find comparable alternatives. From there, I ran daily feedback cycles with publishers, monitoring new sources closely as they launched. When a new source triggered a rejection rate spike, I acted immediately: alerted the client, asked the publisher to pause the source, and investigated the MMP logs to understand exactly why it was being rejected — then fed that back into the next round of decisions.
Purchase rate increased by 160% over 3 months. The process combined data analysis, publisher negotiation, and live technical troubleshooting — the kind of work that sits at the intersection of account management and implementation. The client went from flagging dissatisfaction to having a clear, monitored strategy with daily visibility into what was working and why — and ultimately approved a budget increase based on the results.
Automation · Process · Ops
Daily reporting required 20–40 minutes of manual data copying — peaking on Mondays after weekend accumulation, adding up to 2+ hours per week in busy months. On top of that, monitoring rejection rates meant checking a platform repeatedly throughout the day. I automated both entirely.
Every day started with manual data copying from our app install tracking platform into Google Sheets — 20 to 30 minutes on regular days, up to 40 minutes on Mondays when weekend data had accumulated. In high-volume months with many active campaigns, this added up to over 2 hours of manual work per week. On top of that, monitoring rejection rates meant checking the platform repeatedly throughout the day. When workload was high, checks got missed — and a spike could go unnoticed for hours, directly affecting campaign performance and client results.
I built two automations in Google Apps Script. The first ran daily, pulling data directly from the tracking platform into Google Sheets — eliminating all manual copying. The second ran every 10 minutes, checking rejection rates across active campaigns. If any exceeded the threshold, it immediately sent a Slack message and email to the responsible team member with the campaign name and exact percentage — so issues were caught and acted on within minutes, not hours.
Manual data errors dropped to zero. The team recovered hours of focused work per week — no longer interrupted by reactive monitoring. The system kept running independently during vacations and sick leave, with alerts automatically routed to the right colleagues. What had been a daily source of cognitive overhead became fully invisible infrastructure.
Tech · UX · Client Onboarding
A client needed to manage 40+ workshop participants during live sessions, which involved manual access control and form distribution. I designed and built a login-based landing page that automated the entire flow.
A recurring client ran live workshops with 40+ participants and was managing access and form distribution entirely by hand during sessions — someone had to individually share the right form with each participant in real time. It was chaotic, error-prone, and took attention away from the workshop itself.
I designed and developed a login-based landing page — solo, handling both UX design and frontend development. Each participant logged in with their own credentials and was automatically redirected to their personalized Google Form. No manual distribution, no coordination overhead during the live session.
All manual logistics during live sessions were eliminated. 40+ participants could access their materials independently and instantly. The client, who was already recurring, had a noticeably smoother experience — and the system continued to be used across subsequent workshops.
Contact
I'm looking for roles where I can sit at the intersection of product and client — helping teams build better products while ensuring users actually get the value promised. If you think there's a fit, I'd love to hear from you.