AXOODREN Contact DE

CAREER.

We are looking for people who want to own a system. Not a ticket.

Here there is no layer between you and the business you build for. You sit with the people who will use the system, and you see whether it holds. That is harder than a slide. And it is why the work here means something.

We build the team step by step, with roles that fit the projects, not a headcount plan. Below is what the work looks like in four directions. If you recognise yourself in one of them, get in touch.

onboarding · what you ownFIRST WEEKSYOU OWNsit in on a customer callthe notes✓read a running systemone module✓ship a change with reviewthe change✓take a process end to endthe processno ticket without a system behind itYOURS

Who we are looking for.

Four directions, no job ads. What you bring matters more than the title you last had.

01 · Engineering

You build what runs afterwards.

Agents, interfaces, data flows, operations. You are on a system from the first line to production, with a direct line to the people who use it.

  • You want to know why a system decides what it decides
  • You have operated something before, not just built it
  • You would rather write a test than a slide

02 · Data & AI

You turn data into rules that hold.

Models, analysis, rulebooks with sources. You make sure a system only claims what it can prove, and that it blocks when the basis is missing.

  • You would rather check against real numbers than against assumptions
  • You can explain what a model does in the language of a business
  • You can bear uncertainty and name it

03 · Consulting

You sit with the client, not above them.

You trace the real process, not the org chart, and write down where it gets stuck. You help decide what gets built first, and you say when something is not worth it.

  • You have been on a shop floor, in a law firm or in a back office, not just in a meeting room
  • You can disagree with a managing director without losing them
  • You calculate with the client's numbers, not your own

04 · Working students

You learn on a real system.

No side project in the corner. You work on what is being built right now, with a person at your side who has time for questions.

  • You study something involving computer science, data or business
  • You want to see a result that someone uses
  • You ask before you guess

How a conversation goes.

No assessment, no riddles. Three steps in which both sides find out whether it fits.

01

You tell us what you have built.

Not the CV, but a thing you made that someone used. We ask what went wrong and what you would do differently today.

02

We work for an hour on something real.

An excerpt from a running project, anonymised. You see how we work, we see how you think. No whiteboard theatre.

03

We tell you what we see.

Honestly, in both directions, without weeks of silence. If it fits, we settle role, start and terms in the same conversation.

No title that fits? Tell us what you have built.

One link is enough: a project, a repository, a profile. We will get back to you, and not with a form.

FAQ.

Are there open positions right now?

We do not post job ads, we build the team along the projects. If one of the four directions fits you, get in touch. Whether and when there is a place, we tell you in the conversation, without a waiting loop.

Do I need experience with AI?

More important is that you want to understand systems and have built something before that someone used. Models and tools you learn here on real tasks. What you will not learn here is care, that you bring with you.

How does the application work?

You send a link to something you have built, or a few sentences about it. Then the three steps above: tell, work for an hour on something real, honest feedback. No cover letter, no assessment centre.

Where and how do you work?

Where the system is built: at the client's when it is about the process, and at the desk when it is about code and data. How that is split for you depends on the project and is part of the conversation.