Forward Deployed Engagement Manager

About Nexus

We’re the converged data platform for the AI era—composable by design, built on an open‑source foundation, and AI‑native from the ground up. One identity, one governance envelope, one operational layer across every mainframe, data lake, warehouse, and streaming system in the business. For the first time, enterprises can bring their existing stack along instead of rebuilding it—and still give AI agents full context across the estate.

Our platform processes credit risk data for 90%+ of US small businesses (40M+ customers) every month, delivers intent signals for 300M+ subscribers monthly for Africa’s largest telco, and powers the data and AI layer for a top‑3 US bank. We’re 100+ people across the US and India, headquartered in Atlanta, and we triple revenue year over year.

The person who owns whether NX1 delivers for a customer—from the moment they sign on. This is the delivery and technical operations owner at a portfolio of NX1’s strategic accounts, not a project manager or CSM. The role involves translating the customer’s business problem into tangible requirements for our platform, designing the engagement around that solution, and driving it to landing so the customer is winning.

Everything else—program mechanics, executive presence, margin, documentation—is in service of that solution landing.

• Manage a portfolio of 2–4 strategic NX1 accounts, each generating USD 5–10 million in delivery / managed services revenue
• Own gross‑margin management for the portfolio: cost‑to‑serve per account, scope discipline, hero‑engineer attrition risk, and non‑generalizable custom work
• Drive the P&L for those accounts, surface risk before it appears on dashboards, and manage margin alongside deliverables
• Maintain executive relationships so the VP of Data / CDO / CTO knows you by name and sees you as a peer, not a vendor
• Shape renewal and expansion strategy in partnership with the CRO; you set the conditions under which the customer grows, without carrying quota

• Stand up the delivery program on day 1 of a new engagement, creating roadmaps, milestones, dependencies, governance, and communication cadence
• Run the weekly operating rhythm—internal stand‑ups, customer syncs, executive readouts, and escalation reviews—and build artifacts that keep teams grounded in reality, not theater
• Own the documentation surface for each engagement, including program plans, decision logs, RAID registers, executive status, runbooks, and the customer‑facing roadmap view
• Design how Linear and Notion are used for your portfolio rather than inheriting a template others built

• Serve as the bidirectional translator between the customer’s business problem and NX1’s engineering reality, surfacing the right requirements and engineering trade‑offs without distortion
• Build requirements together with the customer in conversation, with the depth provided by Solution Architects and FDEs when needed
• Hold the line on technical commitments—distinguishing scope, roadmap asks, and one‑off custom builds that engagements cannot absorb
• Create concise one‑page summaries for the customer’s CTO and the engineering team, distilling architecture documents and key insights

• Define what “winning” looks like for each customer in writing within the first 60 days of an engagement and instrument it
• Build a customer‑health signal that detects problems 60 days before they become escalations, using usage trajectory, executive sentiment, milestone slippage, support ticket patterns, and roadmap dependency drift
• Run quarterly business reviews that the customer’s executive team deems the most useful meeting of the quarter
• Translate customer pain back into product roadmap input and close the loop when it lands

• Partner with the CRO on expansion conversations, combining technical credibility with commercial framing
• Hold the cost‑to‑serve number for engagements, distinguishing managed‑service scope, paid one‑offs, and roadmap asks
• Spot early churn signals and elevate them before they…