The kind of place we’re building
Bring what you know from outside your job title. We use it.
Software for the music business needs people who can read messy data, understand how a team actually works and spot a problem others walked past.
We try to build something useful, be decent to each other and keep an interest in life outside work.
Ask, then decide. Out loud and in writing.
Anyone can ask the question that changes the plan.
Most good decisions here started as a question, an example or an objection from someone on the team.
So we write things down, say what we don’t know yet and listen to the person closest to the problem.
Four habits. They show up in the product.
Our working principlesStart with the person.
Before debating a feature, find out what someone is trying to do and what information they’re missing. Start from a conversation, a workflow or a real example.
Make the thinking visible.
A sketch, a small prototype or a clear paragraph makes an idea concrete. Say what you believe, what you know and what you still need to find out. Share it early, while feedback can still change it.
Leave a clear handoff.
The next person shouldn’t have to reconstruct a decision. Name the owner, explain the tradeoff and say what happens next. The product works the same way: an empty state that says what to do, an error that says what happened.
Keep learning after release.
Watch how people use what we shipped, ask what confused them and notice what they work around. Change the decision when the evidence changes.
Music is the reason.
We build this because we love music, and we know how much work sits behind it.
Behind every release and show there are contracts, budgets, sales reports, flights and a lot of messages. We build for the people who handle that work, which listeners never see.
That is why small product details matter to us. A clear handoff gives a team time back. A good overview makes a busy week easier to plan.
Log off sometimes. The work gets better for it.
What you notice away from the screen, at a gig or on a walk, often ends up in the product.
Three teams. Pick the one that fits.
Engineering & AI
Handle messy source data without losing its meaning. Keep an artist’s records connected. Make a failed action recoverable. Decide where automation saves work and where someone needs to check the result.
Product & data
Sit with the person checking a report, confirming a show or planning the team’s week. Find out where they lose time, what they trust and which answer would change their next decision.
Marketing & community
Write about the product, talk with the people who use it and bring what you hear back to the team.
Before you apply
Common questions. Ask us anything else.
Do I need to have worked in music?
Each role describes the relevant experience. Connect your work to the problems on that page and tell us what draws you to music and mgmtOS. A portfolio or a short write-up of how you think is a good place to start.
What should I share when I apply?
A short introduction and a CV, profile or portfolio link. Point to work that helps us understand your contribution. Public examples are welcome; please keep confidential employer or client material private.
What about location and working arrangements?
Every role is remote worldwide and full-time. Role level and compensation are discussed directly during hiring. Ask about the things that matter to you before making a commitment.
What if my work does not fit one role?
Write to info@mgmtos.io. Tell us what you would like to contribute and share an example that makes your perspective concrete.
See the open roles.
Nine open roles across engineering, product and marketing. All remote, all full-time.