Principal Product Marketing Manager - Go-To-Market at Mindtickle · LumiJobs

Responsibilities

Mindtickle is moving from a market perception as a sales training and enablement platform to recognition as the AI-native revenue enablement platform, powered by ElevateOS. The product work is underway. The harder problem is market meaning: whether the market understands why any of this matters, why it matters now, and why Mindtickle is the company that should own it.
This is a company-level clarity role. You will work directly with the CEO, the co-founders, Product, Sales, Solution Consulting, Customer Success and Analyst Relations. It is also a hands-on role: you will personally write the positioning, the message architecture and the persona narratives that the rest of the company draws from.
Your measure of success is simple: does the market repeat it? Can Sales say it in one sentence without reading a slide? Do customers hear a business argument rather than AI buzzwording? Can analysts place Mindtickle in a category and describe how it differs? Does the demo make the positioning tangible? And do deals move, save and expand because of the story rather than in spite of it?
What you will own:
1 - The category narrative behind ElevateOS
Build and maintain the answer to why the world needs ElevateOS now. Ladder the portfolio of agentic capabilities into one category idea instead of a portfolio tour. Hold the line on the four questions the market will ask in sequence: why change, why now, why Mindtickle, why not the alternatives. The narrative you write is the one the company defends in front of analysts, boards, and CROs, so it has to survive scrutiny from people who are paid to be skeptical.
2- The message architecture, held as one source of truth
Codify master positioning, the differentiation argument, the claim set and the proof each claim rests on. Every downstream artefact draws from this document rather than from a fresh interpretation. You version it as the platform and the market move, you decide what enters and what is retired, and you are the person who says a piece of language is off-architecture. One message architecture feeding many artefacts is the mechanism that stops the company from producing many disconnected deliverables.
3- The buyer translation layer
Convert the platform story into a specific value story for each buyer: revenue leaders who own win rate, ramp time and forecast confidence; enablement leaders moving from programmatic enablement to always-on agentic enablement; frontline managers who need to coach with evidence rather than anecdotes; sellers who need guidance in the flow of work, before the call and during the deal; buyers who experience the engagement; and CIO and RevOps stakeholders who care about interoperability, governance, integrations and enterprise readiness. Each persona gets pain, trigger, value proposition, proof and objection handling. The bar is that an AE can take it into a live enterprise conversation without translating it first.
4- Buyer pain as the default language for every capability
Express each capability through the business problem it solves, the impact it creates and the evidence behind it. "Deal Guide gives sellers AI recommendations" fails the bar. "Deal Guide helps managers and sellers identify deal risk early by connecting Salesforce context, buyer questions, stakeholder gaps, competitive intelligence and win-loss patterns into one execution guide" passes it. Apply the same test to every claim: does the claim communicate differentiation, or does it prompt a follow-up question?

Principal Product Marketing Manager - Go-To-Market

Responsibilities

Qualification

Required

Company

Mindtickle