Senior Manager, API Monetization Strategy

We need to output HTML fragment with sections: About the role? The posting has Position Overview (English) and Aperçu du Poste (French). The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. The posting includes Position Overview (English) and Aperçu du Poste (French). That could be considered "About the role". Then Responsibilities (English) and Responsabilités (French). Then Minimum Qualifications (English) and Qualifications Minimales (French). Also there is a Benefits section (English) with description and link. Also Salary transparency (Pay) with salary range. So we have Pay and Benefits sections. Also there is "Learn More About Autodesk" etc which is boilerplate? Might be considered generic marketing; but it's not boilerplate? It's about company culture; maybe we can include as "About Autodesk"? Not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should not add other headings. So we should map content to those. We have Position Overview -> About the role. Responsibilities -> Responsibilities. Minimum Qualifications -> Qualifications (maybe also Requirements? but we have Qualifications). Could also include Requirements but we have Qualifications. Benefits -> Benefits. Pay -> Salary transparency. Schedule: not present, so omit. Skills: not explicitly listed; we could infer from qualifications but better not to create unless explicit. So omit Skills. Requirements: we have Minimum Qualifications; could treat as Requirements but we already have Qualifications. The instruction says prefer few substantive sections over many thin ones. So we can combine Qualifications and Requirements into one Qualifications section. Or we could have Qualifications and Requirements separate if both present. But we have only qualifications. So we will output Qualifications. We need to preserve all substantive information. So we need to include the English and French text for each section? The posting includes both languages; we should preserve both. Likely we should include both English and French paragraphs under each heading. Not duplicate headings for each language. So under About the role we can include both English overview and French overview paragraphs. Similarly for Responsibilities: include English responsibilities bullet list and French responsibilities bullet list. Qualifications: include English minimum qualifications and French qualifications minimales. Benefits: include English benefits description and link; French? The French posting didn't include benefits; only English. So we just include English. Pay: include English salary transparency; French? Not present. So just English. We must not include boilerplate like "Learn More About Autodesk", "Equal Employment Opportunity", "Belonging", "In-Person Onboarding and Identity Verification", etc. Also remove duplicated lines like the job requisition ID appears twice; we should fold minor metadata into a short

or drop it. Probably drop it. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

English overview...

French overview...

Responsibilities

• ...
...

French responsibilities...

but French responsibilities are also bullet list; we could combine both languages in same list? Better to keep separate lists? Could do two

each preceded by language indicator? But we need to preserve all substantive info; we could include both English and French bullet lists under same heading. Could wrap each in

indicating language? Not required. Simpler: after English list, add a

French version:

then French list. But we need to avoid filler. Ensure we don't add extra headings. Let's extract the exact text. Position Overview English: "Position Overview As Senior Manager, API Monetization Strategy, you will partner with internal stakeholders to scope, build, and drive the business models and monetization programs around Autodesk APIs. To be successful in this role, you’ll need to be highly collaborative and organized. You will work directly with multiple teams across Autodesk to understand goals, constraints, business needs, and to identify creative solutions to monetize and scale API monetization. You will apply learnings from these engagements to the planning and execution of programs that form the foundation of future Autodesk revenue streams. While you won’t need to be the expert, you will look under the hood and understand systems implications of new models to help translate ideas into needed technical capabilities. And, you will do all of this with an ownership mentality around the business streams you want to bring to market. With over $6.5 billion in revenue and more than 15,000 global employees, Autodesk has established itself as the global leader in design and make technology for software and services that offer customers better outcomes through automation and insights. If you've ever driven a high-performance car, admired a towering skyscraper, used a smartphone, or watched a great film, chances are you've experienced what millions of Autodesk customers are doing with our software. At Autodesk, we look to hire innovators who reimagine possible, those with diverse backgrounds who elevate our thinking, and leaders who shape the world and our future." French overview: "Position Overview As Senior Manager, API Monetization Strategy, you will partner with internal stakeholders to scope, build, and drive the business models and monetization programs around Autodesk APIs. To be successful in this role, you’ll need to be highly collaborative and organized. You will work directly with multiple teams across Autodesk to understand goals, constraints, business needs, and to identify creative solutions to monetize and scale API monetization. You will apply learnings from these engagements to the planning and execution of programs that form the foundation of future Autodesk revenue streams. While you won’t need to be the expert, you will look under the hood and understand systems implications of new models to help translate ideas into needed technical capabilities. And, you will do all of this with an ownership mentality around the business streams you want to bring to market. With over $6.5 billion in revenue and more than 15,000 global employees, Autodesk has established itself as the global leader in design and make technology for software and services that offer customers better outcomes through automation and insights. If you've ever driven a high-performance car, admired a towering skyscraper, used a smartphone, or watched a great film, chances are you've experienced what millions of Autodesk customers are doing with our software. At Autodesk, we look to hire innovators who reimagine possible, those with diverse backgrounds who elevate our thinking, and leaders who shape the world and our future." Wait the French overview appears to be same as English? Actually the French posting after "Aperçu du Poste" includes same content but in French? Let's look: The French text after "Aperçu du Poste" is: "En tant que responsable de programme senior manager, Modèles économiques des API, vous travaillerez en collaboration avec les parties prenantes internes afin de définir, de mettre en place et de piloter les modèles économiques et les programmes de monétisation liés aux API d'Autodesk. Pour réussir dans ce poste, vous devrez faire preuve d'un grand esprit de collaboration et d'une excellente organisation. Vous travaillerez directement avec plusieurs équipes au sein d'Autodesk afin de comprendre les objectifs, les contraintes et les besoins commerciaux, et d'identifier des solutions créatives pour monétiser et développer la monétisation des API. Vous mettrez à profit les enseignements tirés de ces missions pour planifier et mettre en œuvre des programmes qui constitueront le fondement des futures sources de revenus d’Autodesk. Bien que vous n’ayez pas besoin d’être un expert, vous devrez analyser les rouages du système et comprendre les implications des nouveaux modèles sur les systèmes afin de contribuer à traduire les idées en capacités techniques nécessaires. Et vous accomplirez tout cela en adoptant une attitude responsable vis-à-vis des flux commerciaux que vous souhaitez commercialiser. Avec plus de 6,5 milliards de dollars de chiffre d’affaires et plus de 15 000 employés à travers le monde, Autodesk s’est imposé comme le leader mondial des technologies de conception et de fabrication pour les logiciels et les services qui offrent aux clients de meilleurs résultats grâce à l’automatisation et à l’analyse de données. Si vous avez déjà conduit une voiture de haute performance, admiré un gratte-ciel imposant, utilisé un smartphone ou regardé un excellent film, il y a de fortes chances que vous ayez fait l’expérience de ce que des millions de clients d’Autodesk réalisent grâce à nos logiciels. Chez Autodesk, nous recherchons des innovateurs qui repensent le possible, des personnes aux parcours variés qui enrichissent notre réflexion, et des leaders qui façonnent le monde et notre avenir." So we need to include that French paragraph. Responsibilities English list: "Own defining and prioritizing business requirements and policies for our API monetization model and track execution by internal partners Drive communication and workflows across teams and cross-functional partners, serving as a key integration point with other teams for projects / programs Organize and focus project team time and effectiveness Anticipate organizational needs and pursue proactive solutions Act as a thought leader on API monetization and the evolution into MCP Server monetization - from day-to-day discussions to long-term strategy and planning Execute and move the project forward, including project tracking and providing updates across the organization" French responsibilities list: "Définir et hiérarchiser les exigences et les politiques commerciales relatives à notre modèle de monétisation des API, et suivre leur mise en œuvre par les partenaires internes Faciliter la communication et les flux de travail entre les équipes et les partenaires interfonctionnels, en servant de point d'intégration clé avec les autres équipes pour les projets / programmes Organiser et optimiser le temps et l’efficacité de l’équipe de projet Anticiper les besoins de l’organisation et rechercher des solutions proactives Agir en tant que leader d’opinion sur la monétisation des API et l’évolution vers la monétisation de MCP Server – des discussions quotidiennes à la stratégie et à la planification à long terme Mettre en œuvre et faire avancer le projet, y compris le suivi du projet et la communication de mises à jour à l’ensemble de l’organisation" Qualifications English: "Minimum Qualifications At least 10 years of experience in similar roles Specific experience in Strategy or Go-to-Market an API-centric business Expertise in driving technical, cross-functional programs with the ability to understand and articulate both the 30,000 foot business strategy of the program and the granular details of buildout Excellent communication skills. Core strengths around written and verbal communication as well as data analysis and technical understanding Capable of making business recommendations and action plans based on data analysis Display an intense focus on achieving both short- and long-term goals Self-starter and adaptable. You’re energized and able to thrive in a fast-paced environment Excellent collaborator. You love working with others to make things happen" French qualifications: "Qualifications Minimales 10 ans d’expérience dans des fonctions similaires Expérience spécifique en stratégie ou en mise sur le marché