Agency Development Manager

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We have overview (About the role) content. Responsibilities present. Qualifications present. Pay present (base pay range). Benefits? Not explicitly listed; there is mention "Certain roles may be eligible for benefits and other compensation." Not specific benefits; we should not create Benefits section unless posting actually states them. So skip Benefits. Schedule? Not mentioned. Skills? Not explicit separate; maybe we can include Skills if there is content, but not given. Could combine qualifications and requirements. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include. We have About the role (overview). Responsibilities. Qualifications (maybe combine Required and Preferred). Pay. Possibly Requirements? The qualifications section includes required and preferred; we could treat that as Qualifications. Could also have Requirements as separate but we don't have separate requirements list besides qualifications. Might combine. We'll include About the role, Responsibilities, Qualifications, Pay. Ensure we preserve all substantive information; do not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID etc. Must remove boilerplate like EEO etc. Also remove duplicated lines (the repeated inclusion about inclusive work environment appears three times; we should keep only one instance). Also remove navigation/legal/EEO etc. Also remove application instructions (position will be open for minimum of 5 days etc). Also remove link to benefits? We can keep mention of benefits? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The line "Certain roles may be eligible for benefits and other compensation." is not boilerplate? It's generic but maybe considered boilerplate; but it's about benefits. Since we are not creating Benefits section, we could keep it as a paragraph under About the role? But it's generic; maybe better to drop as it's not specific. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. That line is not substantive specific benefit; it's generic. Could be considered boilerplate; safer to drop. Also the line "Find additional benefits and pay information here: https://..." is application instruction? It's a link; could be considered boilerplate; drop. Also the line about position open for minimum of 5 days etc is application instruction; drop. Also EEO statement drop. Also the request for accommodations drop. Now we need to format content. About the role: Should include overview paragraphs after removing duplicates. Let's craft a concise but preserve all substantive information. Need to keep all details: Microsoft Advertising empowers largest advertisers, values, inclusive work environment repeated (keep once). Global Agency Development team sits at intersection... Within Global Emerging & Independent Agency team, you will help shape how Microsoft partners with fast-growing segment... etc. Need to keep all details: The Emerging & Independent Agency business is a significant growth engine... managed independents delivering 89% of team’s Search growth in FY26. As an Agency Development Manager, you will be core member of North America Emerging & Independent Agency team, partnering closely with Agency Directors to translate strategic agency relationships into measurable advertiser growth. Build trusted relationships with agency practitioners and leaders, develop deep understanding of client portfolios, connect agency opportunities with right Microsoft sales, product, technical, marketing, learning resources. Help move agency partnerships from strategy into execution. This includes analyzing agency and advertiser performance to identify growth opportunities, activating scaled and account-specific education programs, driving product adoption, supporting commercial and joint technical initiatives, creating solid feedback loops between agencies and Microsoft account teams. Help ensure insights gathered at agency level translate into actionable client opportunities and that Microsoft’s agency investments drive measurable advertiser outcomes. This opportunity will allow you to develop deep knowledge of digital advertising ecosystem, strengthen strategic selling and business acumen, build expertise in orchestrating complex partnerships across sales, product, marketing, and technical teams. Also gain experience connecting commercial agreements, technical innovation, agency enablement, and advertiser activation into integrated growth strategy. Microsoft’s mission... values... Starting January 26, 2026, Microsoft AI (MAI) employees who live within a 50-mile commute of a designated Microsoft office in the U.S. or 25-mile commute of a non-U.S., country-specific location are expected to work from the office at least three days per week. This expectation is subject to local law and may vary by jurisdiction. We need to keep that schedule info? It's about work expectation; could be considered Schedule section. The instruction: include a section ONLY when posting has real, specific content for it. This is specific content about expected office days. So we could create a Schedule section with that content. However we also have Pay section. So we could have About the role, Responsibilities, Qualifications, Pay, Schedule. But we must not create sections with filler text. The schedule content is specific; we can include. But we also have Benefits? Not specific; skip. Skills? Not explicit; skip. Requirements? Could be covered by Qualifications; but we could also have Requirements section with same content? Better to avoid duplication. We'll have Qualifications (including required and preferred). We'll not have separate Requirements. Now we need to use

• for any list of duties/requirements/benefits. Responsibilities is a list of duties; we should format as
  • each responsibility bullet. The responsibilities paragraph currently is a long sentence with multiple duties separated by periods. We need to split into list items preserving all detail. We must not invent or summarize away detail; we need to keep each duty as separate bullet but ensure we don't lose any detail. Let's extract duties from responsibilities paragraph: "Drive agency path-to-growth planning: Partner with Agency Directors, Account Executives, Specialists, and sales teams to develop and execute agency-level growth plans that identify priority advertisers, growth and recovery opportunities, seasonal moments, product whitespace, and the actions required to accelerate revenue across the agency portfolio." "Translate strategy into full-funnel activation: Serve as a Microsoft Advertising product and solutions expert, helping agencies understand and activate Microsoft’s full-funnel value proposition across Search, Performance Max, Audience Ads, and incubation solutions. Translate global strategies into compelling, actionable narratives that can be delivered in market and tailored to agency and advertiser needs." "Build for scale: Identify repeatable growth motions across agencies and advertiser portfolios, package winning strategies, insights, product plays, and best practices into scalable solutions, and equip Microsoft sales teams and agency practitioners to replicate them across similar clients. Think beyond one account or meeting to create programs that can drive impact across dozens of advertisers." "Lead scaled education and agency programs: Develop and execute scaled agency enablement programs, workshops, roadshows, and learning experiences that move agencies from awareness to action. Partner across Sales, Marketing, Learning & Development, Product, and other cross-functional teams to identify priority audiences, deliver relevant content, and connect education to advertiser follow-up, product adoption, pipeline, and revenue opportunities. The Emerging & Independent team has already used this model to scale holiday education globally and connect agency sessions to account-level sales follow-up." "Orchestrate sales teams around agency opportunity: Develop a deep understanding of agency client portfolios, business drivers, seasonality, and areas of opportunity, then connect those insights to Microsoft client teams. Create scalable approaches that help sales teams prioritize the right accounts, overcome common blockers, and accelerate adoption rather than solving the same challenge account by account." "Drive disciplined commercial execution: Support Agency Directors in commercial deals, Joint Technical Plans, and strategic agency initiatives by translating agency commitments into account-level execution. Maintain solid pipeline and opportunity hygiene, monitor progress against growth plans, identify risks early, and establish clear accountability across Microsoft and agency teams." "Turn insight into repeatable growth motions: Analyze agency and advertiser performance to identify patterns across growers, decliners, product adoption, and client segments. Use those insights to develop scalable interventions, including recovery plans, product adoption motions, seasonal plays, and advertiser activation strategies, and measure whether those programs are producing meaningful business outcomes." "Operate cross-functionally with high ownership: Work across Agency Development, Sales, Product, Marketing, Technical, Measurement, and Learning teams to bring the right Microsoft resources to agency opportunities. Simplify complexity for agencies and sellers, maintain momentum across multiple workstreams, and build repeatable operating models that allow successful ideas to scale globally." We need to keep each as separate
  • . Ensure we don't lose any detail like punctuation. Now Qualifications: We have Required Qualifications and Preferred Qualifications. We need to preserve all detail. Could format as
    • for each bullet? But they are not bullet list originally; they are statements with OR conditions. We could keep as paragraphs (

      ) but instruction says use

      • for any list of duties/requirements/benefits. Qualifications is a list of requirements; we could treat as list. However the content includes OR statements; we could break each OR line into separate
      • . But we must preserve the OR logic; splitting might change meaning. Better to keep as

        preserving the exact text. The instruction: Use

        • for any list of duties/requirements/benefits. It says "any list". If we keep as paragraph, it's not a list; but it's still a set of requirements. Might be safer to use

          for qualifications prose. However they said use

          • for any list of duties/requirements/benefits. So if we treat qualifications as a list, we should use
            • . But the original is not a list; it's a set of options with OR. Converting to list might misrepresent. However we could keep as

              and still comply? The instruction is a rule; we should follow it. But maybe they expect that if there is a list (like bullet points) we use

              • . If it's not a list, we can use

                . The qualifications section is not presented as a list; it's a block of text with OR. So using

                is fine. Similarly for Preferred Qualifications we could also use

                . Pay: we have specific base pay range info. Could be

                . Schedule: we have the expectation about office days. Could be

                . Now About the role: we need to produce prose (

                ) maybe multiple paragraphs. We'll combine into one or multiple

                but ensure we don't lose any detail. We'll keep as maybe two paragraphs: first about mission/values and team description; second about role specifics and growth engine etc. But we must preserve all details; splitting is okay as long as we don't omit or add. We must remove duplicated lines about inclusive work environment (three times). Keep one. Now let's craft HTML. Structure:

                About the role

                ...

                Responsibilities

                • ...
                ...

                Qualifications

                Required Qualifications: ...

                Preferred Qualifications: ...

                Pay

                ...

                Schedule

                ...

                Check that we didn't include Benefits or Skills sections. Now ensure we removed boilerplate: EEO, application instructions, link, etc. Now write the content. About the role content: Let's compose: "Microsoft Advertising (MSA) empowers the largest advertisers around the world to reach their maximum potential through digital advertising solutions on the Microsoft Advertising platform. In alignment with our Microsoft values, we are committed to cultivating an inclusive work environment for all employees to positively impact our culture every day. Microsoft Advertising’s Global Agency Development team sits at the intersection of some of the industry’s most innovative agencies, advertisers, technologies, and emerging advertising solutions.