Founder's Office — Platform Builder

About MoveInSync

We move over a million people to work every day. 400+ enterprise customers across 30+ countries use our platform to run their employee commute — routing, scheduling, safety, and the day-to-day work of getting people to the office and home again. A 300+ strong tech team powers an all-in-one, AI-led commute platform.

We're not only a software company. We also run the transport itself, through our own driver-partner fleet and a network of operators. That makes us a genuinely full-stack operation — and it's why this role exists.

What this role actually is

This is a new kind of seat, so it's worth being plain about it.

You're paired with one leader who runs a major function at MoveInSync, and you work in the open with the co-founders throughout. Your job is to make that function — and the company around it — run better. You do that in two ways: by helping shape what should happen, and then by building the thing that makes it happen.

Not by writing recommendations and handing them over. Not by running a project plan. You'll sit close enough to the work to see what's genuinely broken, agree with the leader on what "good" looks like, and then build the thing that fixes it. AI tooling is how we get from idea to working software in days — you'll use it heavily, and if you haven't yet, you'll pick it up quickly.

You don't need to be a software engineer. You do need to be someone who builds. If your instinct on seeing a broken process is "I could make something that fixes this" — and you've actually done it before — keep reading.

Why we're hiring for this

At the scale we operate at today, the old ways of working don't hold up. Until recently there was no realistic fix — it would have meant a multi-year queue of internal tooling we never had bandwidth for. AI removed that constraint.

What's left is the harder part. Someone has to work out what each function is actually responsible for, get it written down clearly enough that a system can check it, and then build the system. That's this role.

The founders treat this as the most important work happening in the company today, which is why it sits in the founder's office and not in a queue somewhere.

What you'll actually do

Learn how your function really works. Not the org-chart version — the real one. Who owns what. Where work gets stuck. Which handoffs break, and why. A lot of this isn't written down anywhere, and some of it isn't in anyone's head. Finding that out is your first job.

Work with your leader on what "good" looks like. This means asking a very senior person to be more precise than they're used to being, and calling out inefficiencies in how their team works. It's the hardest part of the job and the most important.

Build the tools. Design and ship internal tools that let your function see what needs attention, act on it, and pass work to other teams cleanly. Build fast, put them in front of real users, iterate. When something proves itself and becomes critical, an engineer joins you to make it production-grade.

Make the tools talk to each other. You're not building a tool — you're building a network of interconnected interfaces that cross functional boundaries and make service delivery efficient and scalable. The operating system for the entire MoveInSync org.

Prove it worked. Decide what "better" means before you build — hours saved, errors reduced, time to resolve — and show the number moved. A tool nobody uses is not a finished project.

Work directly with founders and senior leaders. You'll review what you're building with the co-founders, argue for what should exist, and have a front-row seat to how functional leaders make decisions. You're in the room because of what you ship, not to take notes in it.

Spot organizational gaps before they become bottlenecks — process, structure, talent — and propose what to do about them.

What we're looking for

• 3–5 years of work where you owned something and delivered it — product, operations, engineering, consulting, or a startup where you did a bit of everything.

• Direct exposure to the co-founders

• You build, not just advise. Your instinct on seeing a broken process is to make something that fixes it, and you've done that before — a tool, an automation, a workflow, a scrappy internal system. The tools we use to build are changing fast; we care that you'll get your hands dirty and figure them out, not which ones you already know.

• You notice things other people have stopped noticing. The workaround everyone's used to. The report nobody reads. The approval that exists for a reason no one remembers.

• You can disagree with someone senior and stay in the room. You'll tell a function head their process doesn't work. We'll ask you about a time you've done that, and what happened afterwards.

• You're comfortable with ambiguity. You build structure from scratch rather than following a playbook.

• You articulate well. Most of your influence will travel as writing. Clarity of thought and structure, so complexity lands as something crisp and actionable.

• You're a problem solver. You break a problem into solvable parts and bring them back together into impact.

• High ownership and a bias for execution. This role is measured on outcomes, not activity.

What this is not

It's not a rotation or a stepping stone to a general management role. It's not a strategy, analysis or chief-of-staff seat — you won't be writing board narratives, investor material or briefing notes, and you won't be managing someone else's calendar or follow-ups. And nobody will hand you requirements; working out what should exist is most of the job.

Where this goes

Direct, unfiltered exposure to how a company scales, and a seat at the table for the biggest decisions we'll make over the next 18 months.

The tools you build become the layer our operations actually run on. That's the long game: MoveInSync moving from selling software to running a full-stack operation on a platform we built ourselves.

As what you've built matures, you move from building it to owning it as a product, with engineering behind you. This is a long-term seat, and the people who do it well end up leading the platform and product work this company runs on.

How to apply:

Optional, but strongly recommended — and the thing most likely to get you an interview

• Something you've built. A tool, an automation, a workflow — anything real, however small. A link, a repo, a screen recording, all fine.
• A short note (half a page is plenty) about an inefficiency you spotted somewhere you've worked: what you did about it, and what got in the way.

The CV tells us where you've been. These tell us how you think, and we read every one of them.