Experienced Professional

Scenario

Large public company with extensive information.

Target Employer For Full Workflow

ServiceNow

Synthetic User Profile Input

Name: Maya Chen

Location: Chicago, IL. Open to remote roles or hybrid roles in Chicago. Will travel up to 20%.

Current situation: Recently left a senior operations role at a B2B SaaS company after a reorganization. Looking for a role where she can improve customer-facing operations, knowledge systems, AI-enabled workflows, or post-sale process quality.

Experience:

• 12 years in B2B SaaS operations, customer success operations, and product operations.
• Most recent role: Senior Director, Customer Operations at a 900-person workflow software company serving enterprise IT and finance teams.
• Led a 14-person team covering support operations, knowledge management, customer escalation process, customer health reporting, and renewal-risk analysis.
• Built a cross-functional intake process for product feedback that reduced duplicate escalation tickets by 31% over two quarters.
• Led migration from Zendesk Guide and scattered Google Docs into a governed knowledge base with content ownership, freshness reviews, and analytics.
• Partnered with data science to build an early-warning churn model using product usage, ticket patterns, executive sponsor gaps, and NPS comments. The model was used by customer success managers but was not fully automated.
• Piloted AI-assisted support article drafting and internal answer suggestions. The pilot reduced first-draft article time but required strong human review because early outputs were overconfident.
• Managed Salesforce, Gainsight, Zendesk, Jira, Confluence, Looker, and Airtable-based workflows.
• Earlier roles included implementation project manager, customer success manager, and support operations lead.

Accomplishments:

• Improved support self-service rate from 28% to 43% in one year.
• Cut average time to publish support content from 18 days to 6 days.
• Reduced escalations caused by missing product documentation by 22%.
• Built renewal-risk dashboards used in weekly executive pipeline reviews.
• Presented twice at customer advisory board meetings on support transparency and roadmap feedback loops.

Education and credentials:

• BA in Economics.
• Pragmatic Institute product management certificate.
• Completed an AI governance short course focused on human-in-the-loop workflows.

Interests:

• Enterprise workflow automation.
• AI governance and controlled AI adoption.
• Customer knowledge systems.
• Customer success operations and retention.
• Turning messy internal processes into measurable workflows.

Constraints:

• Salary target: $170k+ base.
• Not interested in quota-carrying sales.
• Prefers companies with complex B2B products and meaningful customer operations problems.
• Does not want a role that is only internal project management with no customer impact.

1. Working Summary

Maya Chen is a senior B2B SaaS customer operations leader with strong evidence in support operations, knowledge governance, escalation reduction, renewal-risk workflows, customer-health reporting, and post-sale operating systems. Her most credible AI angle is practical, human-reviewed AI adoption in customer-facing workflows, not AI engineering or enterprise AI policy leadership.

2. Evidence Inventory

3. Demonstrated Capabilities

4. Probable Capabilities

• AI-ready knowledge operations: plausible from KB governance plus AI support pilot; missing proof at larger enterprise scale.
• Customer AI adoption operations: plausible from workflow, support, and governance experience; missing direct ownership of enterprise AI rollout.
• Product operations for customer feedback loops: plausible; missing deeper product roadmap ownership.

5. Knowledge and Interests

• Professional: B2B SaaS, customer operations, support operations, customer success operations, knowledge systems, renewal risk, escalations.
• Interest with evidence: AI governance in support workflows, controlled AI adoption, enterprise workflow automation.
• Interest without enough proof: enterprise AI strategy and technical AI product ownership.

6. Accomplishments and Useful Proof

• Improved support self-service from 28% to 43%.
• Cut content publishing time from 18 days to 6 days.
• Reduced documentation-related escalations by 22%.
• Reduced duplicate escalations by 31%.
• Built renewal-risk dashboards for executive reviews.

7. Constraints, Preferences, and Economic Reality

• Remote or Chicago hybrid; travel up to 20%.
• $170k+ base.
• No quota-carrying sales.
• Best economics are likely senior customer operations, customer success operations, product operations, or customer enablement roles at mid-market/enterprise B2B software companies.
• Smaller startups may value her skills but may not meet compensation or scope needs.

8. Best Three Lanes

1. Customer operations transformation: strongest evidence and seniority fit.
2. AI-ready knowledge/support governance: differentiated angle with measured support outcomes.
3. Customer success operations and renewal-risk systems: strong evidence but should avoid pure analytics positioning.

9. Bridge Roles or Next-Step Roles

• Head of Customer Operations.
• Director/Senior Director, Customer Success Operations.
• Director, Knowledge Operations or Customer Education Operations.
• Product Operations leader for post-sale/customer feedback systems.
• AI adoption operations role inside customer outcomes, support, or enablement.

10. Roles I Am Not Ready For Yet

• AI engineer or ML product lead.
• Enterprise AI governance policy owner.
• Quota-carrying sales leader.
• Pure data science leader.
• Technical ServiceNow/Salesforce solution architect unless platform requirements are operational rather than implementation-heavy.

11. Claims To Avoid Or Use Cautiously

12. Proof Assets To Gather

13. Unknowns and Follow-Up Questions

• Which prior customer segments did she serve?
• Does she want people leadership, operator leadership, or both?
• Does she have proof artifacts she can share without confidentiality issues?
• Is she open to consulting or implementation partner organizations?
• Which platform ecosystems does she want to avoid?

Reusable Artifact

Maya Chen is a senior B2B SaaS customer operations leader with demonstrated success in knowledge governance, support self-service, escalation reduction, renewal-risk workflows, and customer-facing operating systems. Her best lanes are customer operations transformation, AI-ready support/knowledge governance, and customer success operations. She should not position herself as an AI engineer, data scientist, or enterprise AI policy owner. Constraints: remote or Chicago hybrid, $170k+ base, no quota-carrying sales, complex B2B products preferred. Strong proof assets to prepare: KB governance case study, escalation process map, AI support pilot lessons, and renewal-risk dashboard examples.

Prioritized Sourced Employer List

Top 5 Sourced Employers To Research Next

1. ServiceNow: strongest current AI/workflow governance evidence.
2. Zendesk: closest support operations and AI support match.
3. Gainsight: strongest customer-success operations match.
4. Intercom: strong AI support operations angle.
5. Atlassian: plausible service/knowledge operations fit.

Do Not Pursue Yet

• Frontier AI labs unless a customer operations role is specifically sourced.
• ServiceNow/Zendesk/Salesforce implementation roles requiring deep technical platform certification.
• Any quota-carrying sales role.

Closer But Less Glamorous Alternatives

• Customer operations roles at mature B2B SaaS companies with AI support initiatives.
• Customer education or knowledge operations roles at enterprise implementation partners. Source named employers before adding them to the target list.

Targets To Source Before Considering

• Named ServiceNow implementation partners.
• Mid-market B2B SaaS companies with AI support pilots.

Patterns

Maya should prioritize complex B2B software companies where AI adoption creates knowledge-quality, support workflow, and customer operations governance problems. She should keep the pitch operational, not technical AI.

1. Source Ledger

2. Source Coverage Gaps

• Current openings were not exhaustively searched across all ServiceNow teams.
• No direct job posting was found for Maya's exact customer operations/knowledge governance lane in this run.
• Competitor context is only lightly covered.

These gaps mean the public evidence is strong enough to research and network narrowly, but not enough to assume a specific role exists.

3. What The Employer Does

ServiceNow is a large public enterprise software company positioning itself as an AI control tower for business reinvention. It sells workflow, data, AI, service management, CRM, employee service, security, and risk products to large enterprises.

4. Direction and Priorities

Verified company facts/claims:

• Q2 2026 subscription revenue was $3.877B, and ServiceNow said AI crossed $1B in annual contract value.
• ServiceNow is embedding AI, data connectivity, workflow execution, security, and governance across its product portfolio.
• AI Control Tower, Workflow Data Fabric, Action Fabric, Context Engine, and Autonomous Workforce are major 2026 priorities.

Reasonable inference:

• Customers will need help turning messy operations, data, policies, and knowledge into governed workflows before autonomous AI can work reliably.

5. Current Role and Hiring Signal Scan

• Relevant current signal found: Director, Product Management - Action Fabric, a senior product role for agentic AI platform architecture and execution. This is likely not Maya's role, but it confirms investment in agentic workflow infrastructure.
• Role families to scan next: customer outcomes, customer success operations, customer education, knowledge management, product operations, support operations, AI adoption, workflow transformation.
• Current opening status for Maya's exact lane: unknown.

6. Employment Path Types

• Full-time: plausible if a role exists in customer outcomes, operations, knowledge, product ops, or enablement.
• Partner/vendor: plausible through ServiceNow implementation or adoption partners.
• Contract/freelance: unknown and less likely for senior strategic scope.
• Informational only: justified now.

7. Market, Customer, or Local Context

Enterprise AI is moving from copilots toward governed agents and workflows. ServiceNow is explicitly selling governance, context, data, and action layers, which creates operational adoption problems for customers.

8. Challenges and Risks

• Customers may not trust autonomous AI without controls, auditability, and ownership.
• AI workflows depend on accurate knowledge, data lineage, and process definitions.
• Cross-functional ownership may be hard across IT, risk, security, customer operations, and business teams.
• Maya may be competing against candidates with direct ServiceNow ecosystem experience.

9. Opportunities

Hypotheses:

• Customer enablement around AI readiness and governed workflow adoption.
• Knowledge/content governance for AI-assisted support and service workflows.
• Customer operations playbooks for moving from pilots to measurable adoption.
• Feedback loops connecting support, product, renewal risk, and AI adoption signals.

10. People, Teams, and Functions To Understand

• Customer outcomes/customer success operations.
• Knowledge management, customer education, and support operations.
• Product operations for AI Control Tower, Action Fabric, Workflow Data Fabric, and Autonomous Workforce.
• AI governance or risk/compliance product teams.
• ServiceNow partner ecosystem.

11. Ecosystem Signals

ServiceNow announcements mention partnerships with NVIDIA, Microsoft, AWS, Anthropic, Google Cloud, and others. Knowledge 2026 is a major event context. These are research paths, not assumed relationships.

12. Is The Public Evidence Enough To Act?

Only lightly. The evidence supports targeted research and learning conversations. It does not justify broad outreach or assuming ServiceNow has a job shaped around Maya.

13. Unanswered Questions

• Which team owns customer readiness for AI Control Tower and Autonomous Workforce?
• Are knowledge governance or AI adoption operations roles currently open?
• How important is direct ServiceNow implementation experience?
• Are relevant roles remote or Chicago-compatible?

14. Research Summary For Next Prompt

ServiceNow has strong current evidence around governed AI, agentic workflows, Workflow Data Fabric, AI Control Tower, and Autonomous Workforce. Maya's credible overlap is customer operations and knowledge governance for enterprise AI adoption. Hiring evidence for the exact lane is unverified, so the next step should be a narrow overlap analysis and role-signal validation, not broad outreach.

1. Bottom-Line Assessment

Possible strong fit. Fit type: narrow immediate research fit, employment path unverified.

Maya's customer operations and knowledge governance experience maps well to ServiceNow's governed AI/workflow direction. The missing piece is whether a current team or role values her operator profile without requiring deep ServiceNow implementation or technical AI product ownership.

2. Fit Breakdown

3. Primary Lane, Secondary Lane, Reject Lane

• Primary lane: customer operations / customer outcomes for governed AI adoption.
• Secondary lane: knowledge governance or customer education operations for AI-enabled workflows.
• Reject lane: AI engineering, solution architecture, quota-carrying sales, enterprise AI policy owner.

4. Prioritized Overlap Hypotheses

5. Best Value Proposition Candidates

• "I help enterprise SaaS teams turn messy customer-facing workflows into governed, measurable operating systems."
• "I bring customer operations and knowledge governance experience to the point where enterprise AI needs controlled adoption."
• "I can help AI-enabled support and customer success teams improve knowledge quality, escalation reduction, and human review."

6. Positioning To Avoid

• "AI governance executive."
• "ServiceNow solution architect."
• "AI product strategist."
• "Data science leader."

7. Minimum Proof Needed Before Acting

• KB governance case study.
• AI support pilot lesson learned.
• Escalation reduction process map.
• Renewal-risk dashboard example.
• List of ServiceNow roles/team names matching the lane.

8. Gaps and Risks

• Direct ServiceNow platform experience absent.
• Exact role availability unknown.
• Salary target requires senior scope.
• Customer operations roles may be hub-specific.

9. Validation Questions

• Who owns customer adoption readiness for AI Control Tower?
• Are there teams focused on knowledge readiness for AI workflows?
• Does ServiceNow hire customer operations leaders from adjacent B2B SaaS?
• What proof matters more: metrics, platform familiarity, or customer-facing programs?

10. Effort Budget and Parallel Targets

Active target, not sole primary target. Spend meaningful research time, but run parallel searches at Zendesk, Gainsight, Intercom, and ServiceNow implementation partners.

If no matching role evidence or useful response appears after one week of focused research, reduce ServiceNow to watchlist and shift effort to better-validated customer operations roles.

11. Move To Application Trigger

Increase effort or apply only when Maya finds a role or conversation confirming a team need in customer outcomes, knowledge governance, customer education, customer operations, or product operations tied to governed AI adoption.

12. Recommended Decision

Research more and pursue only matching roles or learning conversations. Do not broadly apply yet.

13. Artifact For Approach Planning

Maya has a credible ServiceNow thesis around customer operations and knowledge governance for governed AI adoption. Fit is promising but role evidence is incomplete. Approach should use proof assets, narrow team research, and learning conversations with customer outcomes, product ops, knowledge, and enablement functions.

1. Approach Intensity

Targeted research and learning conversations. Do not start with broad outreach or public posting because direct role evidence is still incomplete.

2. Approach Thesis

ServiceNow's governed AI/workflow direction may need customer operations leaders who understand knowledge quality, support workflows, escalation loops, and human-reviewed AI adoption. Maya can credibly test that thesis, but she should not assume the role exists.

3. Most Relevant Problems Or Opportunities

1. Customer readiness for governed AI workflows.
2. AI-ready knowledge/content governance.
3. Escalation and renewal-risk feedback loops connected to AI adoption.

4. Research Targets

• Customer outcomes/customer success operations.
• Knowledge management/customer education.
• Product operations for AI Control Tower, Workflow Data Fabric, Action Fabric, Autonomous Workforce.
• ServiceNow partner ecosystem.
• Current ServiceNow role postings using the V3 keywords.

5. Message Targets

• 2 to 3 non-executive people in customer outcomes, knowledge/customer education, or product operations, only after Maya has proof assets and role/team language.

6. Do-Not-Contact-Yet Targets

• CEO/C-suite.
• Customers named in press releases.
• Product leaders owning deeply technical AI platform work unless Maya has a specific role-relevant question.
• Partners she does not actually know.

7. Ecosystem Paths To Check

Check against real network only:

• Former customers/vendors using ServiceNow, Zendesk, Gainsight, Salesforce, or Atlassian.
• Chicago SaaS customer success leaders.
• Knowledge 2026 speakers/attendees.
• ServiceNow implementation partners.
• Alumni and former colleagues.

8. Recommended Engagement Plan

1. Build proof packet: KB governance, escalation map, AI support pilot, renewal-risk dashboard.
2. Run a role scan using specific keywords and save only roles matching customer operations, customer outcomes, knowledge, enablement, or product ops.
3. Research 10 people/functions; message at most 2 or 3.
4. Apply only if a role matches the primary or secondary lane.

9. First Message Goal

Learning and validation: identify whether a real team owns customer readiness or knowledge governance for governed AI workflows.

10. Message Angles

• "I have been studying ServiceNow's AI Control Tower and Autonomous Workforce direction. My background is customer operations and knowledge governance, especially support self-service and human-reviewed AI support workflows. I am trying to understand which teams own customer readiness for these workflows."
• "I led support knowledge governance and escalation reduction work in enterprise SaaS. I would value advice on whether ServiceNow has roles where that operating background matters."

11. Public Post Guidance

Do not post publicly yet. A public post may make sense only after Maya has a concrete artifact or insight about enterprise AI adoption and can write it as useful analysis rather than a hiring plea.

12. Evidence To Gather Before Contact

• Sanitized metrics.
• Process maps.
• AI support pilot lessons.
• Role/team list.
• A concise "what I am trying to validate" note.
• Do not use confidential employer, customer, or proprietary data in any proof packet or outreach material.

13. Compensation and Boundary Notes

Senior compensation target means Maya should avoid unpaid advisory labor and vague "pick your brain" loops that do not move toward role clarity. Consulting or partner paths should be evaluated against travel and compensation.

14. Fallback Targets

• Sourced fallback employers from Prompt 2: Zendesk, Gainsight, Intercom, Atlassian.
• ServiceNow implementation/adoption partners; source specific partner names before outreach.
• Mature B2B SaaS companies with AI support or customer education operations roles.

15. One-Week Action Plan

Day 1: Build proof packet outline. Day 2: Search current roles and team language. Day 3: Identify research targets and network overlap. Day 4: Prepare two learning messages. Day 5: Send up to two messages. Day 6: Tailor application only if a role fits. Day 7: Update company brief and decide continue/deprioritize.

16. Stop Conditions

• Roles require deep ServiceNow implementation or AI engineering.
• No evidence appears for customer operations/knowledge/adoption roles.
• Location or travel conflicts.
• Conversations indicate the problem is owned by technical teams that do not hire operators.

17. Reusable Plan Summary

Approach ServiceNow through targeted research around customer operations and knowledge governance for governed AI adoption. Build proof first, message sparingly, avoid public posting for now, and run fallback targets in parallel.