Why this role exists now

We are currently migrating our entire Salesforce system. Not as a maintenance project, but because our commercial teams have been reorganized into four verticals and the old system no longer supports this structure.

This means that you won't be joining a finished system where you simply process tickets. You'll be joining at the stage where decisions are being made. Data model, automation, permissions – much of this will be built over the next few months, and you'll be helping to build it.

And there's a second layer. Salesforce is the foundation for an AI layer we're currently developing. AI agents are only as good as the data structure they're based on. Without clean objects, hierarchies, and fields, every agent delivers unreliable results. You'll build precisely this structure—the foundation upon which everything else is built. We'll decide together where the platform's strategic direction will go. You'll be responsible for how this is implemented cleanly and reliably within the system.

This role is intentionally hybrid in Berlin. Not as a matter of principle, but because the work demands it: You sit alongside the people you're building for. An account manager can show you on screen in two minutes where the process breaks down – no ticket or call required. The best CRM solutions arise from observing work, not from requirements documents. That's why we expect you to be available at least 3 days a week (4 days during the probationary period), not as a compromise, but as an integral part of what makes the role successful.

Your first six months

Months 1-2: You're deep into the migration. Hardening the sandbox, processing UAT feedback, fixing bugs. You learn our processes by building and improving them within the system.
Months 2–4: You'll take over your own workstreams along our processes – not individual tickets, but entire workflows. Your first flows will go live, relieving our account managers of manual work.
Months 4–6: You know the system better than anyone else in the company and become the person who says what works and what doesn't. You begin to systematically make the database AI-compatible – and contribute your own suggestions on where Agentforce or another layer has real leverage.

What you will be responsible for with us

The system. Data model, objects, fields, record types, validation rules, permission sets, layouts. You keep it consistent while four verticals pull on it simultaneously. With us, there's no system integrator doing that for you – you are the person in the system.

Processes, not clicks. You observe how an account manager actually works, and then build from there. Not what's written in the ticket, but what solves the problem.

The data foundation for AI. Data hygiene isn't just a reporting topic for us, but a prerequisite for reliable agent performance. You'll establish hierarchies and standards that can withstand an AI quality check.

A direct line to the business. Our sales and account management teams come to you with their problems. You translate frustration into concrete improvements – and in doing so, get to know a business where thousands of shifts are filled every week.

What you bring

Real depth as an admin. Several years of hands-on experience, not just dabbling. Data models, flows, permission sets, validation rules, and page layouts are your daily reality, not just theory.
Action bias. You solve problems instead of writing concepts about them. Your preferred response to a requirement is a working solution, not a workshop.
Genuine interest in AI within the platform. You follow what Salesforce is doing with Agentforce and Data Cloud and have your own opinion on it – even a critical one. Practical experience is a strong plus, curiosity is essential.
German and English at C1 level. Our commercial teams work in German, the company in English. You need both.
A plus, but not a must: Apex and LWC, Salesforce certifications (Administrator, Advanced Administrator, Platform App Builder, Sharing & Visibility Designer), experience with multi-level account hierarchies.

This role is not for you if…

You want to design architecture, but not build it yourself within the system.
If you are looking for a well-established system with clear processes – we are in the middle of a restructuring, and much is unfinished.
You consider AI to be hype and data hygiene an end in itself.
If you primarily want to work remotely: This role thrives on your physical presence with the teams.
If you need a setup with a delivery team, architecture board and a clear requirements chain – with us, the requests come directly to you from the teams.

Responsibilities