Senior Staff Deployment Strategist, Operations
💰 $170,000 – $225,000/yr
At a glance
- Who can apply
- United States
- Work arrangement
- On-site · Remote
- Employment type
- Full-time
- Seniority
- Senior
- Salary
- $170,000 – $225,000/yr · published by the employer
- ✓ Open to early-career candidates
Checked against the employer's source on October 14, 2026. Details come from the employer's posting; confirm them on the application page.
Advertisement
Job Description
About ALSO.
We’re ALSO, an electric mobility company originally conceived as a part of Rivian. We’re a passionate team of builders, dreamers, doers and innovators, focused on creating entirely new (not to mention, innovative and delightful) vertically integrated, small EVs designed to meet the global mobility challenges of today and tomorrow. Our mission is to inspire everyone to ride ALSO—replacing many local car, truck and SUV miles with ones on vehicles that are more affordable, more enjoyable and 10-50x more efficient.
ALSO is becoming a manufacturer, with serialized vehicles moving from production lines to customers. The systems to manage that transition largely don’t exist yet.
You’ll build ALSO’s operating system for making and moving vehicles—from CM production to the customer’s door—creating a single source of truth for planning, quality, inventory, delivery, and decision-making. Today, much of this runs on spreadsheets and tribal knowledge; you’ll turn it into scalable systems and close the loop so decisions happen within them.
As the Senior Staff Deployment Strategist, Operations, you’ll help take ALSO from startup to a mature, class-leading operator. You’ll report to our Director of Enterprise Data and work closely with supply chain, manufacturing, quality, finance, and commercial teams. There are no direct reports today; you’ll lead through architecture, code, and influence.
What You Will Do
Build end-to-end visibility from factory to customer: WIP, first-pass yield, as-built genealogy from module to vehicle, inventory down to supplier-held stock, and shipment status.
Build the planning engine across both supply chains, what we buy from our CMs and what we assemble ourselves: material planning at SKU-by-day, available-to-promise, and the build and fulfillment queues.
Run the supplier loop: PO confirmations, promise dates, RFQs, design changes, the forecast we release to tiers 1 through 3, and component pricing with effectivity.
Run the physical moves: booking, importation and track-and-trace from CM to 3PL to customer, plus the visibility feed out of our CMs’ own systems.
Close the quality loop: incoming and inline quality, deviations and trends, warranty tracing, and a defect traced to a supplier chargeback that lands in the financial system.
Settle buy-versus-build by shipping: stand up a thin, disposable app for quality, transport and warehouse visibility, run the process instrumented, and let evidence pick the platform we buy later.
Engineer the process before you automate it: instrument how the work actually runs, including the exceptions nobody wrote down, delete the steps that exist only because two systems could not talk, then automate what survives. Paving the cowpath faster is not the job.
Ship with coding agents in days rather than quarters.
Embed with the team that owns a process, automate it with them, and leave them able to change it themselves. Success is the owner shipping their own improvements, not filing tickets for you.