# Forward Deployed Engagement Manager at Nexus Cognitive

- Company: Nexus Cognitive
- What the company does: The composable, out-of-the-box data architecture that gives organizations complete freedom to build, adapt, and scale any data workload — from legacy databases to real-time AI pipelines — without vendor lock-in. Backed by Insight.
- Company website: https://www.nexuscognitive.com/
- Type: Startups
- Level: Senior
- Location: Atlanta HQ
- Work setup: Remote
- Posted: 2026-06-01
- Apply by: 2026-10-08
- Apply: https://jobs.ashbyhq.com/nexus-cognitive/80ee0246-fae1-4865-9a17-f3baddb0ef3e
- Page: https://www.1752.vc/careers/jobs/nexus-cognitive-forward-deployed-engagement-manager/

## About the role

You are the buck-stops-here owner for whether NX1 delivers: the rollout program, the solution architecture and roadmap commitments, the documentation surface, the customer health signal at the engineering level, the margin against the engagement, and the loop back into engineering when the platform needs to evolve.

## What they're looking for

- Own the bidirectional translation between the customer's business problem and NX1's engineering reality — surface the right requirements into the org, surface engineering trade-offs back to the customer, without distorting either side
- This is the craft of the role: customers don't hand you a requirements doc that's correct. You build it together, in conversation, by knowing what to ask and what to push back on
- Pull in Solution Architects when the work needs architecture depth, pull in FDEs / engineers when the work needs to be built
- Hold the line on technical commitments: what's in scope, what's a roadmap ask, what's a one-off custom build the engagement can't absorb
- Be the person who reads the architecture doc, asks the sharp question, and writes the one-page summary the customer's CTO actually reads — and the one-page brief the engineering team uses to scope the work
- Operationally rigorous. Strong track record of delivering against customer needs — not activity-shaped ("I ran the program") but outcome-shaped ("the customer got X and here's specifically how I made it land")

Tags: Customer Delivery and Operations