Strategic Client Leader
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The posting has "Overview" then "Responsibilities", "Qualifications". Also there is a pay range and mention of benefits. Also mention flexible work up to 50% at home (Schedule?). Also mention "Other Qualifications: This position is not eligible for visa sponsorship..." That's a qualification.
We need to preserve all substantive information, remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must remove the EEO paragraph, the accommodation line, the "This position will be open for a minimum of 5 days..." maybe that's application instruction? It's about posting duration; maybe considered application instruction? Probably remove. Also remove "Find additional benefits and pay information here: https://careers.microsoft.com/us/en/us-corporate-pay" maybe that's a link; but it's about benefits and pay info; we might keep pay info but remove the link? The instruction: remove application instructions. That line is a link to benefits and pay info; maybe considered application instruction? It's not exactly instruction to apply, but it's a reference. Safer to remove it? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The link is not exactly application instruction but could be considered navigation? Might be safe to keep? However they said "Find additional benefits and pay information here:" that's a pointer; could be considered navigation. I'd remove it to be safe.
We need to include sections only when posting has real, specific content. So we need sections: Overview (maybe as About the role? but they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Overview could be considered About the role. So we can use About the role
for the overview paragraph.
Responsibilities: we have a block starting with "Responsibilities Responsibilities". We'll extract the responsibilities sentences.
Qualifications: we have Required Qualifications, Other Qualifications, Preferred Qualifications. We'll combine into Qualifications section.
Pay: we have pay range info. So we need a Pay
with the range.
Schedule: mention flexible work up to 50% at home. That's schedule info. So Schedule
with that.
Benefits: there is mention "Certain roles may be eligible for benefits and other compensation." That's vague; not specific. The instruction: never create Benefits section unless posting actually states them. It states "Certain roles may be eligible for benefits and other compensation." That's not specific benefit details. Might be considered not specific enough. Probably we should not create Benefits section because no concrete benefits listed. So skip Benefits.
Skills: not explicitly listed; we could infer but not present. So skip.
Requirements: maybe same as Qualifications; but we have Qualifications section. Could also have Requirements separate but we can combine.
We must not repeat job title as heading. Not needed.
We must preserve all substantive information: need to include all details from overview, responsibilities, qualifications (required, other, preferred), pay, schedule.
We must not invent or summarize away detail. So we need to keep the exact sentences? We can keep them as prose in
About the role
for the overview paragraph. Responsibilities: we have a block starting with "Responsibilities Responsibilities". We'll extract the responsibilities sentences. Qualifications: we have Required Qualifications, Other Qualifications, Preferred Qualifications. We'll combine into Qualifications section. Pay: we have pay range info. So we need aPay
with the range. Schedule: mention flexible work up to 50% at home. That's schedule info. SoSchedule
with that. Benefits: there is mention "Certain roles may be eligible for benefits and other compensation." That's vague; not specific. The instruction: never create Benefits section unless posting actually states them. It states "Certain roles may be eligible for benefits and other compensation." That's not specific benefit details. Might be considered not specific enough. Probably we should not create Benefits section because no concrete benefits listed. So skip Benefits. Skills: not explicitly listed; we could infer but not present. So skip. Requirements: maybe same as Qualifications; but we have Qualifications section. Could also have Requirements separate but we can combine. We must not repeat job title as heading. Not needed. We must preserve all substantive information: need to include all details from overview, responsibilities, qualifications (required, other, preferred), pay, schedule. We must not invent or summarize away detail. So we need to keep the exact sentences? We can keep them as prose inor list items in
- . For responsibilities, we should use
- for any list of duties/requirements/benefits. The responsibilities are a list of duties; we can put each as
- . Similarly qualifications: we can list each requirement as
- . However the qualifications are somewhat complex with OR statements; we need to preserve the detail. Could break into bullet points: each qualification line.
We must not create placeholder text.
Let's extract overview text:
"Overview Do you want the opportunity to drive transformation with one of the world’s most influential Ag Science companies? You’ll be dedicated to a single, highly strategic cusotmer—partnering closely with leadership and engineering teams to shape long‑term, enterprise‑wide transformation. In this role, you’ll focus on accelerating impact across intelligent operations, R&D, connected and autonomous systems, applied AI, and next‑generation employee and customer experiences, delivered at truly global scale. As a Strategic Client Leader, you will have the opportunity to drive Transformation in partnership with this Strategic customer with a focus on AI, Copilot and Security, to achieve both Microsoft and customer business outcomes. Leveraging your large, multi-functional team across the breadth of the Microsoft solutions portfolio, engage at the most senior levels of your customer and bring industry-relevant solutions to help the customer adopt and embrace digital technologies. With a proven history of driving growth in market share, achieving sales targets, customer obsession, and partner collaboration, this role will give the opportunity to leverage your extensive customer network and sales experience to execute against your customer’s account plan. This role is flexible in that you can work e.g., up to 50% at home. Microsoft’s mission is to empower every person and every organization on the planet to achieve more. As employees we come together with a growth mindset, innovate to empower others, and collaborate to realize our shared goals. Each day we build on our values of respect, integrity, and accountability to create a culture of inclusion where everyone can thrive at work and beyond."
We need to keep all that. Might be long; we can put in
. Now responsibilities: The block after "Responsibilities Responsibilities". Let's extract sentences: "You will deliver business growth through leading and empowering account teams. Lead execution of Go to Market (GTM) to achieve customer business outcomes across the entire customer lifecycle. You will accelerate customer satisfaction and model executive engagements with business decision makers and C-Level executives. You will win against competition by establishing Microsoft as market leader, maximizing Customer spend, achieving targets (billed revenue, consumption, and adoption). You will lead partnership across the organization to achieve business value for customers and business results for Microsoft. You will cultivate relationships and use Microsoft sales strategies throughout multiple levels of the customer's organization (e.g., executives, business, and technical decision makers) to establish strong alignment on long-term goals and secure buy-in and execution. You will use business cases to develop and present compelling value proposition presentations and specialized business plans for customers that showcase Microsoft's products and solutions, generate business and upsells, and generate new opportunities." Note there is duplication of "Responsibilities". We'll ignore duplicate heading. Now qualifications: Required Qualifications block: "Required Qualifications: Bachelor's Degree AND 10+ years experience working in an industry (e.g., financial services, retail, manufacturing, healthcare, energy, government, education, technology) and/or driving digital transformation OR Master's Degree AND 9+ years experience working in an industry (e.g., financial services, retail, manufacturing, healthcare, energy, government, education, technology) and/or driving digital transformation OR 13+ years experience in working in an industry (e.g., financial services, retail, manufacturing, healthcare, energy, government, education, technology) and/or driving digital transformation OR equivalent experience. 6+ years experience making recommendations to and/or collaborating with mid-to-senior level executives. 8+ years experience closing large, complex agreements/deals." Other Qualifications: "Other Qualifications: This position is not eligible for visa sponsorship. Candidates must have authorization to work in the United States that does not now or in the future require employer sponsorship." Preferred Qualifications: "Preferred Qualifications Bachelor's Degree AND 13+ years experience working in an industry (e.g., financial services, retail, manufacturing, healthcare, energy, government, education, technology) and/or driving digital transformation OR Master's Degree AND 11+ years experience working in an industry (e.g., financial services, retail, manufacturing, healthcare, energy, government, education, technology) and/or driving digital transformation OR equivalent experience." We need to preserve all that. Could list each as
- . Might be long but okay.
Pay: "Strategic Account Management IC5 - The typical base pay range for this role across the U.S. is USD $133,000 - $222,700 per year. There is a different range applicable to specific work locations, within the San Francisco Bay area and New York City metropolitan area, and the base pay range for this role in those locations is USD $170,300 - $239,800 per year. Certain roles may be eligible for benefits and other compensation."
We should keep that as prose in
under Pay heading. Schedule: "This role is flexible in that you can work e.g., up to 50% at home." Already mentioned in overview but we can still include schedule section with that sentence. However we must not duplicate content? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines: we should remove duplicated lines. The sentence appears in overview already. If we include it again in Schedule, that's duplication. We should avoid duplication. So we should not repeat that sentence; we can either keep it only in overview and not have a Schedule section, or we can keep schedule section but remove from overview? The overview includes that sentence; we could keep it there and not have schedule section. But the instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The schedule content exists (flexible up to 50% at home). It's already in overview; we could still have a schedule section but we would be duplicating. Better to not duplicate; we can either keep overview and not have schedule section, or we could move that sentence to schedule and remove from overview. Which is better? The overview currently contains many details; removing that sentence might lose some info but we could still keep schedule section with that sentence. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid moving content; we just need to preserve it somewhere. Duplication is to be removed. So we should avoid having the same sentence twice. So we can either keep it in overview and not have schedule section, or keep it in schedule and remove from overview. Which is more appropriate? The overview is a general description; schedule is a specific aspect. I'd keep schedule section with that sentence and remove it from overview to avoid duplication. However the overview also contains many other details; removing that sentence may be okay as long as we preserve it elsewhere. Let's do that: remove the flexible work sentence from overview, and put it under Schedule. Now benefits: we have "Certain roles may be eligible for benefits and other compensation." That's vague; we might not create Benefits section. But we already mentioned benefits in pay section; we could keep that line there. It's already in pay paragraph. So we keep it there. Now we need to ensure we removed boilerplate: EEO paragraph, accommodation line, "This position will be open for a minimum of 5 days..." etc. Also remove the link line. Now produce HTML fragment:
About the role
Overview text without the flexible work sentence.
Responsibilities
- ... ...
Qualifications
- Required Qualifications: ...
- 6+ years experience making recommendations to and/or collaborating with mid-to-senior level executives.
- 8+ years experience closing large, complex agreements/deals.
- Other Qualifications: This position is not eligible for visa sponsorship. Candidates must have authorization to work in the United States that does not now or in the future require employer sponsorship.
- Preferred Qualifications: Bachelor's Degree AND 13+ years experience ... OR Master's Degree AND 11+ years experience ... OR equivalent experience.
- containing the whole block.
Alternatively we could split into multiple