Dweve

Careers at Dweve | AI Engineering Jobs

Join our European AI team building binary neural networks, constraint-based reasoning and multi-agent frameworks. Roles in the Netherlands and Germany.

Dweve careers

Dweve’s careers page lists current engineering, research, builder and communications roles in the Netherlands and Germany. It describes a bootstrapped European AI team working on binary neural networks, constraint-based reasoning and multi-agent frameworks.

  • Vacancy status and role requirements belong to the individual role record and should be checked before applying.
  • The company page provides context on Dweve’s ownership, products and research; it is not a promise of a particular opening or response time.

Choose the audience that matches your question

The page contains three selectable readings of the same subject.

For consumers

Dweve is hiring engineers, researchers, builders and communicators in the Netherlands and Germany. The Careers page explains the work, locations and hiring process so a candidate can decide whether the team is a good fit before applying.

For businesses

The Dweve Careers route describes a bootstrapped European AI team working on binary neural networks, constraint-based reasoning and multi-agent frameworks. It lists current roles in the Netherlands and Germany and links the process to the company record.

For engineers

Dweve is hiring people to build binary neural networks, constraint-based reasoning and multi-agent frameworks. The Careers page is the source for current role descriptions, locations and application details; role status can change as positions are filled.

Market rate salary for the Netherlands or Germany. A meaningful option package, mainly profit options, in a bootstrapped company, with performance based growth.

Premium health insurance for you and your family. Mental health coverage, wellness support, and preventive care included.

A EUR 1,000 budget for a home office and ergonomic setup, plus the hardware and peripherals you need to do the work well.

Yours to spend on courses, conferences or books, chosen by you rather than approved line by line.

30 days paid vacation, plus the local public holidays where you live.

Mostly remote, with an office when it helps. Where you sit is not part of how the work is judged.

Bootstrapped, and small enough to see the whole of

A small team in Europe, and an honest hello

Engineers, researchers, builders and writers

A call about your background, the role, and your questions.

The founders and the people you would work with, so both sides can judge.

A CV and a short note on why you are interested. A person on the team reads it and answers.

The systems you have already built: what broke, what you chose, and what you would change now.

The answer, and a written offer if it is a yes.

No standup and no inbox rota. Most people take the hardest thing first, while the house is still quiet.

The team talks once, in the middle of the day, and then goes back to work.

Long stretches with the notifications off. Almost nothing here needs you inside the minute.

Whatever is unfinished is still there tomorrow, and tomorrow is soon enough.

There is no queue handing work out. The system is yours, and so is the call on what it needs next.

Sales, support and engineering sit in one short thread, so nothing gets translated twice.

Work is carried through to the point where somebody can use it, then read by the person who will maintain it.

The first block starts before the first message. Nobody schedules the start of your day.

Changes are read by the person who will carry them, not by a rota.

Code written in the first weeks ships and shapes the architecture rather than waiting in a branch.

the posting is the contract shape, not a teaser

Send a short note to [email protected] saying what you do and what you would want to own.

A CV and three or four sentences. There is no cover letter template to fill in.

A person reads it and replies within 48 hours, including when the answer is no.

We work hard when it matters and we stop when it does not.

Nobody counts hours or watches a status light.

The team is small enough that the person deciding is in the conversation.

Correctness is the standard, not a stretch goal.

every figure here is the figure in the offer

Primary hub for research and core engineering. Amsterdam workspace planned for 1 November 2026: The Stack, a new AI hub at Jacob Bontiusplaats 9; Arnhem until then. Remote flexibility either way.

Engineering and enterprise solutions, with occasional travel.

English across the team. Dutch is a strong plus, never a requirement.

We hire where you already are, inside these two countries.

Every application is read and answered by someone on the team.

Your application is stored in Dweve's Cloudflare hosted hiring system and used only for recruitment.

We decline in writing. We do not go quiet on you.

a filter narrows the board, it never hides a role

Write to [email protected], we still reply

nothing on this page changes after you apply

We are a small group of people in the Netherlands and Germany. We build software that helps with everyday work and can always show you how it reached an answer. Every job we have open is on this page, and the pay and the terms are on it too.

A bootstrapped European team building neurosymbolic systems. We hire in the Netherlands and Germany, and we publish the pay, the terms and the shape of the hiring process before you apply rather than at the offer stage.

One stack, silicon to model, and every layer of it is ours. The work is compilers, kernels, distributed systems and constraint reasoning, and the open foundations are public on GitHub. We hire in the Netherlands and Germany, and the whole posting is on the page before you apply.

Nobody here manages your calendar for you. You decide when the day starts, what order the work goes in, and when it has had enough of you for one day. What the team asks in return is that the work is finished properly, and that you say so early when it is not going well rather than at the end of the week.

This is a company you can hold the whole of in your head. You will see the problem, the code that answers it and the person it is for. The trade is that responsibility is not spread thinly: the work you take is yours to finish, and the feedback on it comes back straight rather than through a chain.

You own a system rather than a queue of tickets, which means you also own the decision about what it needs next. The team is small, so that decision costs one conversation. What is asked in return is depth: you should be able to explain the choice to whoever maintains it after you.

the moments are fixed, the hours around them are not

The package is itemised below, with the figure attached to each line. The one worth calling out here is research time: it sits inside working hours, and publishing what comes out of it is supported.

published before you apply, not explained afterwards

what happens in each, and how long it takes

There is no take home project and no sample task to fit around your evenings.

You do not need a cover letter template or a referral. Tell us what you have built and what you would want to own next. A person reads every application, including the ones we end up declining.

Filter by team or by country, open the one that fits, and read the whole description. Every job here says what the pay is, what the contract is and what the hiring steps are, before you send anything. Nothing is behind a login, and nothing is added to a job after you apply. If none of them fit you, write to us anyway.

Filter by discipline or by country. Every posting states its department, location, contract type and work model before you open it, and the full description lives on the role page. Pay and terms sit on the posting itself rather than arriving at the offer stage. All current roles are full time and hybrid, in the Netherlands or Germany.

Filter by discipline or by country. Each posting names the system the role owns, the people you would be sitting next to, and what you would be expected to change. The open foundations that work sits on are public on GitHub, so you can read the code before you read the posting. Read the whole thing before you decide it is not for you.

Each stage below says what it is for and how long it takes, and you are told that before it starts rather than after, so you can plan around it and hold us to it. The same five stages run for everyone: nothing is added for one person and skipped for another. Nothing in them is a puzzle set for the room. We talk about work you have already done, and the last conversation is with the people you would sit with.

Nothing is added for one candidate and skipped for another: the same five stages run for every role we post, and their lengths were set before the posting went out rather than while it runs, so you can put the whole process in a calendar before the first call. The discussion is about work you have already built rather than a puzzle written for the room, and the last stage is with the people you would sit with.

The stages below are the whole process, and each carries the length it is bounded to. Depth counts here: one system explained properly is worth more than a tour of ten. The discussion starts from what you have already built, what broke in it, and what you would change now, so the judgement is about systems rather than about puzzles written for a room you will never work in. The last conversation is with the people who would maintain the system beside you.

Every line of the package is written out below with the figure attached to it, because nobody should have to ask at the offer stage what a benefit actually amounts to.

The package is itemised below rather than described. We are bootstrapped, so the option package is written against the company we are actually building rather than against a funding round.