Shipping inside someone else's organisation: competing stakeholders, being the only engineer, and handing over what you built.
4 questions in Forward Deployed Engineering.
The rounds look familiar but the scoring moves: a forward deployed engineer loop grades what you notice in messy data, whether you narrow a vague problem before building, whether your design fits a customer's operating capacity, and whether you can explain and push back in front of non-engineers.
Treat reluctance as a rational response to inheriting on-call burden rather than as resistance to change: find out what it costs them, transfer ownership through work they do themselves while you are still there, and get the acceptance recorded by whoever committed their capacity.
It moves the constraint from what you can build to what they can maintain: choose the stack their team already runs, cap the number of new concepts you introduce, and treat every clever abstraction as a maintenance debt they will pay after you are gone.
Stop negotiating between opinions and get the disagreement written down as two named decisions with their consequences, then push it to whoever owns the budget; as an outsider your leverage is that you can make the conflict visible without being a party to it.