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

three houses, one household.

three offices that mostly run themselves, and a small exec team for the few things that don't stay local.

how we organize

there is no ticket-pusher middle layer. partners claim work, form teams, and use retros to surface gaps. leads and PMs coordinate; they do not turn the organization into a reporting ladder.

choose your work
partners pick up tickets, join projects, and form teams around what they care about. if nobody's on it yet, you start it.
facilitation, not management
PMs and leads coordinate work, unblock teams, and keep process moving. project owners make the calls.
autonomous offices
denver, amsterdam, and zurich keep their own budgets and make their own calls. nobody asks permission to keep the lights on.
process not power
decisions go through a written process anyone can read. it's the same on a good day and a bad one, and authority doesn't let you skip it.

offices

three offices. denver is headquarters and the largest presence, amsterdam is the secondary office, and zurich is a satellite.

headquarters
where most of mutuol lives. home to the executive team, core ops, and relocation support.
secondary office
core technology and partner engineering. the european timezone anchor for the rest of the org.
satellite office
mostly remote partners, with space to host when someone's in town.

the executive team

there's a small executive team for the decisions that actually cross offices: big budgets, governance, ties. everything else stays local.

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 sign-off.

when consensus fails:
if local consensus can't settle something, the exec team breaks the tie. it's meant to be rare; most things resolve in retros or just by talking.

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.