Deployment Strategist, Istari

• There is no fixed path into this role and no single background that produces a great Deployment Strategist. We are looking for people who would rather own the result than the process, and the more ownership you take, the more you will be given
• We hire for judgment, curiosity, and a bias toward action more than for a specific degree or years of experience. That said, people who do well in this role tend to share a few things:
• A track record of owning an outcome with no formal authority over the people delivering it, and finding that energizing rather than alarming
• Insider fluency in the following customer domain… the kind that comes from having lived it, along with a clear view of what is broken in how that world works today
• Domain: allied military aircraft development — multinational teams, disconnected MBSE and PLM toolchains, and engineering data that must clear companies, suppliers, and export regimes before a design can close
• Technical conversancy across modeling and simulation, MBSE, digital threads, software development, and/or agentic design: enough to interrogate an engineering claim and be credible doing it, not necessarily enough to build it yourself
• Product sense, because this role sits closer to product management than to project management: knowing what to build next and what not to build at all, and telling the difference between a request that serves one user and a capability that belongs in the platform
• The range to brief a program executive in the morning and pair with an engineer in the afternoon
• An instinct for reading rooms and organizational dynamics, because adoption is won in the customer's org chart as much as in the software
• Comfort operating with incomplete information and shifting requirements, and the initiative to define next steps without being told

Desirable

• A Deployment Strategist at Istari is the single accountable owner of a customer program's outcome
• You will embed with a small team of forward deployed engineers on one flagship program, or a small set of lighter engagements, and you will decide what matters: which problems the team attacks and in what order, what each demonstration, technical interchange, or test event has to prove, and how the deployment becomes something the customer cannot imagine operating without. Some days that means a working session with a prime's chief engineer
• Other days it means briefing a program executive on why a digital thread changes their schedule risk, or reading the room after a review board and knowing exactly which conversation needs to happen next
• You will have support from a shared Program Operations team that helps to assemble reports, format deliverables, and work the submission machinery behind you – but you answer for all of it. Your hours go to the outcome and to what the program becomes next, not to the tracker
• You are not the primary builder here; we hire Forward Deployed Engineers for that, and your job is never to stand between them and the customer. You do need enough technical range that engineers trust your judgment and customers trust your answers
• Own the outcome of a program end to end: define what success means, choose the problems worth solving and the order to solve them in, and set what each milestone has to prove
• Embed with government and industry customers to understand their mission, their constraints, and their politics, and build relationships from end users to program executives that make a deployment durable
• Set direction and priorities for a small Forward Deployed Engineering team without intermediating between engineers and users, and protect their time from everything that is not the work
• Own the growth thesis: option years, follow-ons, and expansions grow out of delivered outcomes, and they are your responsibility to shape from inside the relationship
• Feed what you learn in the field back into product and engineering, so the platform gets better for every customer, not just the one in front of you
• Work day-to-day at or travel to customer sites, test events, hackathons, and program milestones as needed. Travel is typically domestic, though some customer engagements require international travel. Travel is typically domestic, though some customer engagements require international travel