Forward Deployed Strategist

Harrier builds software inside our customers' businesses. We pick an industry, learn it deeply, and put a two-person team on the ground: a Forward Deployed Engineer and you. You stay until the software reflects how the place actually works, across Salesforce, data, AI, and whatever else the stack runs on. The model is the one Palantir is known for. The unit You and an FDE run the account together. You lead on the why and the what: which problem is worth solving, what the solution must achieve, whether anyone will actually use it. The engineer leads on the how: architecture, code, what's just now possible with Salesforce, plus a native data (e.g. Redshift, Fivetran, dbt) & AI stack (e.g. Neo4j, LangChain, Bedrock). The line between you is blurry, on purpose. You design the solution together at the whiteboard before anyone writes code, because what's cheap to build and what's a six-month rabbit hole changes which problem is even the right one. You get your hands dirty too: read the org, sketch the flow, stand up the rough version yourself. An engineer alone builds something clean nobody adopts. A strategist alone produces a sharp plan that never runs. The pair is the point. What you'll do Find the real problem. Embed on-site and surface how the organization actually works: the decisions made off the record, the data nobody touches for political reasons, the workaround that's quietly held the place together for years. Reframe the request. A customer asks to "redesign the account page." You discover renewals are slipping because risk reaches the account too late, and you say so. Cut scope ruthlessly. Define the smallest first build that proves value, tied to an outcome the customer can measure. Win the room, then the rollout. Convince a skeptical VP and the frontline that lives with the change, often in one meeting. Carry it through launch, where the politics that stall adoption actually surface. Compound what you learn. Patterns from one industry client become the playbook the next engagement starts from. Who you are You've done the work. You've run or built this function inside a legal, tech, or healthcare company. You know how it really happens, where it breaks, what people will and won't adopt. You hold a point of view and defend it. When a customer asks for the wrong thing, you tell them and keep the relationship. You optimize for what moves the needle, not for keeping the room comfortable. You're technical enough to build with the engineer. You read a Salesforce org, design alongside one without being one, and would rather stand up a working version than write a spec about it. You're commercial. You can tell which problem is worth real money and which is busywork, and you steer toward the first. You're at home without a brief. The part the customer can't specify is the part you're here for. What we value 5+ years of experience in either a strategic, technical customer-facing role such as Deployment Strategist, Account Management, or Management Consulting with enterprise clients. Or as an industry operator (eg. Head of Legal Operations or Director of RevOps). Ability to travel to meet the client on-site. Typically once or twice per year, per client. Fluency in Salesforce and the adjacent tools your industry runs on. Experience with programming, scripting or statistical packages (e.g. Python, SQL). #J-18808-Ljbffr