The role

Your job is to turn a signed deal into real, sustained usage on a program.

Flow is a system of record, which means the sale is the easy part. A requirements platform that half a team uses isn't half as valuable, it's worse than nothing, because now there are two sources of truth. So as one of our first Deployment Strategists, you'll sit at the intersection of sales, engineering, and the customer, and own deployment for a portfolio of accounts: migrating requirements out of legacy tools and spreadsheets, configuring Flow around how each customer's programs actually run, redesigning workflows with their systems engineers, training teams, and doing the change management that turns skeptics into daily users, including the engineers who didn't vote for the purchase. For integration-heavy work you'll partner with a software-focused engineer on our team; your center of gravity is the organizational side.

This is an ideal role for someone who started on hardware engineering programs and found they'd rather work across many customers than inside one. You'll help incredible hardware companies reinvent how they work, and because this function is being built right now, what you learn becomes the playbook future hires run on.
What you'll do

• Run deployments end to end: kickoff, migration, configuration, workflow redesign, training, and adoption
• Drive organizational change inside customer engineering orgs: find champions, work blockers, and make adoption stick after you leave the room
• Define what success looks like for each deployment, instrument adoption, diagnose stalls, and run get-well plans before renewal risk shows up
• Design each customer's Flow setup around their programs, and direct integration work with our software-focused deployment engineers
• Be the product team's eyes and ears in the field: what you see in deployments shapes what we build next
• Partner with the reps who own the commercial side of the book, and with AEs when deployments surface expansion
• Help build the deployment methodology: playbooks, implementation guides, and training materials for the team that comes after you

You should recognize yourself in most of this:

• You're consultative by instinct: you diagnose before you prescribe, and people trust you quickly, including skeptics
• You've made change stick in an organization at least once, and you can tell the story of how
• You can hold your own in a room of systems and hardware engineers, and translate between them and executives
• You run long, multi-team rollouts like a program: plan, milestones, stakeholders, crisp written status, no dropped threads
• You're comfortable with the technical surface: data migration, configuration, APIs at a working level
• You want the early-team experience: ambiguity, ownership, in person in SF

And across all three paths, one hard requirement: you've done real customer-facing work. You've owned relationships with customers, clients, or external partners professionally, whether in pre-sales, post-sales, deployment, consulting, or a customer-facing engineering role.