Das ist der Job
The difficult tickets are not looking for someone who simply follows a script.
Darum lohnt es sich
They require a person who can step into unclear situations, misconfigured systems, conflicting evidence, unhappy customers, and AI outputs that lead nowhere—then determine what the actual problem is.
This role is designed for the support engineer who enjoys the unresolved case: replicating the error, analyzing logs, tracking API activity, examining JSON payloads, distinguishing a 401 from a 404 from a 429, and leveraging AI effectively without blind reliance.
Most support organizations remain structured around ticket queues, templated responses, handoff processes, and documented workaround libraries. We are constructing something different. Routine inquiries are increasingly managed by AI and L1 processes, which means human expertise is allocated to the toughest challenges.
AI is not replacing you in this role. It is the instrument you control, validate, question, and confirm. This position is not about copying AI-generated answers, making rapid guesses, awaiting direction, or escalating as soon as the issue becomes unfamiliar.
It is not suited for someone who specializes deeply in one product and hesitates when the next ticket involves a different technology stack.
It is about delivering the correct answer with the minimum number of interactions the problem permits: reproducing issues before proposing solutions, investigating across tickets, Slack threads, knowledge bases, lo
