The opportunity
Secure Every Identity, from AI to Human Identity is the key to unlocking the potential of AI. Okta secures AI by building the trusted, neutral infrastructure that enables organizations to safely embrace this new era.
What you'll do
Messaging and positioning: Apply the Technical narrative consistently across every asset you build or maintain, and flag where content has drifted from what the product actually does.
Buyer, persona, and market insight: Capture what you hear from TAMs, CSMs, FDEs, SEs, and customer calls, and turn it into concrete updates to content and the BMM.
Competitive and category intelligence: Track roadmap changes, competitor feature releases, and protocol developments (MCP, Cross App Access, agent auth patterns), and summarize what they mean for our technical content.
Go-to-market planning and launch execution: Get technical assets, guides, and BMM entries updated and ready when features move from roadmap to Beta, EA, and GA.
Sales enablement and field readiness: Maintain the guides, demo catalog, and reference material that SEs, TAMs, and CSMs rely on, and track whether they actually use it.
Customer-facing content and asset ownership: Own accuracy and freshness for your assigned assets end to end, starting with the BMM, and retire what's outdated.
What they're looking for
- Cross-functional influence: Work with product, engineering, Customer Success, and Professional Services to collect the inputs you need without formal authority over any of them.
- Roadmap, pricing, and packaging input: Bring recurring field and customer feedback (product gaps, feature requests, deployment friction) to the Technical lead with the evidence behind it.
- The Blueprint Maturity Model technical content. Keep each stage and: capability current: the customer value, the Okta feature that delivers it, and the guide that implements it. Add new capabilities as they ship, move "to be released" items into active stages as they reach Beta, EA, or GA, and keep stage criteria aligned with how customers actually progress.
- The BMM's associated content and templates. Keep the TAM Technical Project: Plan, Customer Overview, Status Overview, and Actions & Deliverables templates consistent with the model. That means matching numbering, accurate task lists, and correct ownership (RACI) across CSM, TAM, PS, and FDE.