about careers work policy organization economics amsterdam zurich hr@mutuol.com

no middle management.

mutuol has an executive team that sets direction, but day-to-day work is self-organized. partners choose what to work on and coordinate through process, not hierarchy.

how we organize

no middle management. no one assigns you work. you pick what you want to do and you do it. if something's not getting done, that shows up in retros.

choose your work
partners pick up tickets, join projects, and form teams based on interest and capacity. you're not assigned work. you claim it.
no middle management
PMs occasionally herd efforts down productive paths, but project owners make the calls.
autonomous offices
each location (amsterdam, zurich, denver) operates semi-autonomously with local decision-making and budget authority.
process not power
there's a process. everyone uses it. that's the whole governance model.

offices

mutuol has three offices. they're different sizes and do different things. amsterdam is headquarters with the largest presence. the other offices operate with local autonomy but coordinate with HQ on shared infrastructure and strategy.

headquarters
where most of mutuol lives. home to the executive team, core ops, and relocation support.
satellite office
second EU presence. devops-focused with mostly remote workers and space available for hosting.
satellite office
being wound down due to conditions in america.

the executive team

mutuol has an executive team, and they have the final say on cross-cutting decisions. they handle cross-office coordination, budget oversight, and governance. day-to-day operations run locally and self-directed.

executive responsibilities:

teams

work happens in teams. you can be on more than one. they're not departments with org charts, just groups of people working on the same stuff. explore open positions across these teams →

technology
partner engineering
technology
partner reliability
economics
finance & treasury
economics
financial controller
domestic
domestic infrastructure
domestic
vehicles & transport
media
media platform
people
people & feelings
people
partner lifecycle

how decisions get made

without a management hierarchy, mutuol relies on process and consensus to make decisions. this isn't perfect, but it's documented and it works.

for day-to-day decisions:
consensus within the team or office affected. if you're doing work that mostly impacts your local context, you decide. retros catch it when a local decision affects someone else.

for cross-team or cross-office decisions:
lazy consensus: propose the change, give reasonable time for objection, and proceed unless someone raises a block. objections require justification and an alternative proposal.

for organizational changes:
RFC-style proposals with documented discussion periods. major changes (budgeting, governance, partner policies) go through the exec team for review and alignment.

when consensus fails:
escalations route to the exec team as a tie-breaking mechanism. this is meant to be rare. most decisions resolve at the local level through retros and direct communication.

inter-office coordination

offices run independently but need to not drift apart. here's how we do that. for details on work arrangements, see our work policy.