SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Flow is a systems engineering platform for hardware teams, backed by Sequoia, enabling companies like Rivian to manage requirements, interfaces, tests, and design decisions in a unified system.
As a Deployment Strategist, you will own end-to-end deployments for a portfolio of hardware engineering customers. Your mission is to transform signed deals into sustained, organization-wide adoption. Flow functions as a system of record—partial adoption creates competing sources of truth and diminishes value—so your work centers on driving real organizational change.
Key responsibilities include:
- Running full deployment cycles: kickoff, data migration from legacy tools and spreadsheets, platform configuration, workflow redesign, team training, and adoption management
- Driving organizational change within customer engineering teams: identifying champions, removing blockers, and ensuring adoption persists after you transition
- Defining success metrics for each deployment, instrumenting adoption tracking, diagnosing stalls, and executing recovery plans before renewal risk emerges
- Designing customer-specific Flow configurations aligned with their program structures and directing integration work with deployment engineers
- Serving as the product team's field intelligence: insights from deployments directly inform product roadmap decisions
- Collaborating with sales representatives and account executives to identify expansion opportunities surfaced during deployments
- Building deployment methodology: creating playbooks, implementation guides, and training materials that scale the function
You will work at the intersection of sales, engineering, and customer operations, translating between systems engineers, hardware teams, and executives. This is an early-stage function being built in real time, so your approach and learnings become the playbook for future hires.
Requirements:
- Proven ability to make organizational change stick; you can articulate a specific example
- Demonstrated consultative approach: you diagnose before prescribing and build trust quickly, including with skeptics
- Technical fluency: comfortable discussing data migration, configuration, APIs, and systems engineering at a working level
- Ability to manage complex, multi-team rollouts as programs: planning, milestones, stakeholder coordination, clear written status updates
- Professional experience in customer-facing roles: pre-sales, post-sales, deployment, consulting, or customer-facing engineering
- Ability to operate effectively in a room with systems and hardware engineers and translate their needs to executives
- Preference for early-stage environment: comfort with ambiguity, ownership, and in-person collaboration in San Francisco
- Background in hardware engineering programs is ideal; you've worked on the engineering side and prefer working across multiple customers
