Deployment Lead

1.      Engagements – the core. Run what we sign as the engagement lead: scope with the stakeholders who own the systems, direct our engineers, make the calls that keep it moving, and own it through go-live. On day one that looks like: we just signed a post-M&A migration at a portfolio company – go lead it with two engineers.

2.      Relationships – the work creates the next work. The person who ran the last engagement is the most credible person in the next room. You'll sit in the sponsor conversations, present the readouts, and turn one portco into three. There's no quota, and the commission is upside on anything you bring in yourself.

3.      The practice – over time. Every engagement shares common pieces, and we haven't productized them yet; that becomes yours to own, along with hiring engagement leads under you as customers stack up.

You have 3–5 years of experience at McKinsey, Bain or BCG, or on a private equity value-creation team – the ideal path is a few years of consulting and then a stretch inside PE – or you ran a function in a portfolio company when the data was a mess.

●     You can run an engagement, and you want to: an ambiguous scope, a demanding customer, and engineers who need clear decisions.

●     You're operationally excellent. The deck is right, the model ties, and the client hears back the same day.

●     You use AI aggressively, or you want to learn fast – real 80/20 judgment over polish.

●     You want the upside, and you've seen what the path to partner looks like. You'd rather own something.