> Markdown version of [/jobs/ext/3864580-technical-support-enablement-specialist](https://www.wearedevelopers.com/jobs/ext/3864580-technical-support-enablement-specialist). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Technical Support & Enablement Specialist - **Company:** 1KOMMA5° GmbH - **Location:** Berlin, Germany (Remote available) - **Experience:** Starter - **Contract:** Internship / Graduate position - **Skills:** Application Programming Interfaces (APIs), Bug Tracking Systems, Business Software, Software as a Service, Issue Tracking Systems, Systems Integration, Bug Reporting, Webhooks - **Published:** October 22, 2026 - **Apply:** https://www.adzuna.de/details/5937691850 ## About the Role * 1 to 2 years of experience in support, customer success or a similar role. Internships and working student positions count. * German and English at C1 level or higher, written and spoken * Experience with business software, for example a CRM or ticketing system * Good technical understanding of how SaaS tools connect: data fields and objects, user roles and permissions, integrations, APIs and webhooks * A structured way of troubleshooting: you can reproduce an issue, narrow down the cause and describe it so that Engineering can act on it without follow-up questions * Experience in training or onboarding other people, or in building automations with low-code tools (e.g. n8n, windmill). One of the two is enough. * Experience in a startup or scale-up is a plus ## Description * Support branches and market teams in Germany, Australia, Sweden, Denmark, Spain, the Netherlands and Finland, in German and English * Diagnose each issue and deliver the matching fix: a guide or training for a knowledge gap, a bug report with reproduction steps for Engineering, a feature request with use case and impact for Product * Where a simple automation closes the gap for a bug or a missing feature, you build it yourself. It goes live after a review with Engineering. * Use ticket data and the support metrics we agree on (volume by topic, time to resolution, share of repeat requests) to find where time is lost, and propose changes * Improve our support setup: ticket categories, templates, routing and handover rules * Write and maintain help articles and run onboarding sessions for new users and new markets This role is a good starting point in our tech organisation. You work across the full system landscape and all seven markets, and you learn how Product and Engineering make decisions. From here you can develop in several directions, for example towards product operations, ownership of an internal tool, or automation and engineering.