Maven AGI is an enterprise AI platform focused on transforming customer service through artificial general intelligence. The Technical Project Manager role is crucial for overseeing complex customer implementations, requiring a blend of technical understanding and project management skills to ensure successful execution and communication between customers and engineering teams.
Responsibilities:
- Owns execution end-to-end on strategic pilots. Not coordination, ownership. You'll track every open item across customer-facing trackers and internal tools (Linear, ClickUp, Notion), know what's blocked, know who needs to be chased down, and drive things to resolution without being asked. Tickets are clean, unambiguous, and mapped correctly. You don't wait for someone to flag a gap, you catch it first
- Understands the platform deeply enough to be useful, not just present. You know Maven's platform and how it interacts with external systems. You can debug a broken integration, read an API error and know where the problem lives, recognize when an intelligent field evaluation is causing a downstream cascade, and describe what's wrong clearly enough that an engineer can fix it immediately. You won't need hand-holding on the technical environment
- Translates between customer and engineering. You join working sessions with customers and come out with crisp, actionable documentation. You write the kind of meeting notes and tickets that engineers want to work from. You understand what customers are trying to accomplish, can spot when a request is misframed, and know when to push back internally versus when to escalate
- Tests relentlessly before go-live. You run test suites, document what broke and why, validate fixes, and track edge cases with rigor
- Runs the operational rhythm. Daily standups, go-live checklists, readiness reviews, metrics readouts — you own the structure that keeps a complex multi-team pilot from going sideways. You're the person who notices when the ClickUp tracker hasn't been updated and fixes it before the Monday client session, not after
Requirements:
- Owns execution end-to-end on strategic pilots
- Track every open item across customer-facing trackers and internal tools (Linear, ClickUp, Notion)
- Know what's blocked, know who needs to be chased down, and drive things to resolution without being asked
- Tickets are clean, unambiguous, and mapped correctly
- Understand the platform deeply enough to be useful
- Know Maven's platform and how it interacts with external systems
- Can debug a broken integration, read an API error and know where the problem lives
- Recognize when an intelligent field evaluation is causing a downstream cascade
- Describe what's wrong clearly enough that an engineer can fix it immediately
- Translate between customer and engineering
- Join working sessions with customers and come out with crisp, actionable documentation
- Write the kind of meeting notes and tickets that engineers want to work from
- Understand what customers are trying to accomplish
- Spot when a request is misframed
- Know when to push back internally versus when to escalate
- Test relentlessly before go-live
- Run test suites, document what broke and why, validate fixes, and track edge cases with rigor
- Run the operational rhythm
- Own the structure that keeps a complex multi-team pilot from going sideways
- Notice when the ClickUp tracker hasn't been updated and fix it before the Monday client session
- Organized to the point of being vocal about it
- Technically credible without being an engineer
- Comfortable sitting in rooms with enterprise stakeholders and with product engineers on the same day
- Does not need external motivation to chase someone down when something is stuck
- Gets things done