Backend Engineer in Berlin

Flikk is an AI gaming app: AI-generated mobile games with AI features that turn users into co-creators of the games. Every one of them is a generation job with a cost, a queue, and a person waiting at the end of it.

You would own the services that orchestrate that: Go on Google Cloud and Kubernetes, scaling against demand that is spiky by nature. The problems worth solving here are latency, cost per generation, and what to do when a model is slow or simply wrong.

• Build and own the Go services behind generation: queueing, orchestration, retries, and delivery.
• Run it on GKE. You deploy it, you are on the hook for it, and you know what it costs.
• Treat cost per generation as a first-class metric, not something finance raises three months later.
• Design for models that are slow, expensive, and occasionally wrong, because they are all three.
• Use AI tooling properly in your own work (Claude Code or whatever you are fastest in) and hold a real view on where it helps and where it does not.
• Work directly with the frontend on the seam between a pending job and something that feels instant.

• Strong Go, and you know why the runtime is doing what it is doing.
• You have run production services on Google Cloud and Kubernetes, including the nights they broke.
• Fluent with AI coding tools (Claude Code or equivalent) on real work rather than demos.
• Latency and cost are things you measure, not things you feel.
• You have opinions about system design and can be talked out of them.

• Attractive VSOP options. If you create the growth, you should share in it.
• Short path from decision to production. No committee between you and the release.
• A profitable company, with a leadership team that has built and sold a similar product before.
• EGYM Wellpass: gyms, pools, and studios across Germany.
• On- and offsites, so team culture and fun don't fall by the wayside.

#J-18808-Ljbffr