Associate Director, Contract Proposal Management - US GTM

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (EEO, legal, etc). Must not include placeholder sections like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Pay And Benefits section with salary ranges and benefits info. So we can include Pay and Benefits sections? The instruction: "Prefer a few substantive sections over many thin ones." Could combine Pay and Benefits into one section? But they said use headings for sections like Benefits, Pay, Schedule. We can include both Pay and Benefits headings if they have content. The posting includes "Pay And Benefits" heading with compensation range and benefits description. So we can split into Pay and Benefits sections. Also there is schedule? Not mentioned. So no Schedule section. We need sections: About the role (maybe from "The Role" paragraph). Responsibilities (list of duties). Requirements (maybe "Required Skills And Experience"). Qualifications? Could combine with Requirements? They said use headings for Qualifications as well. Could have Requirements and Qualifications separate if content distinct. The posting has "Required Skills And Experience" and "Preferred Skills And Experience". Could treat Required as Requirements, Preferred as Skills? Or Skills section for both? Let's map: - About the role: The paragraph starting "As a Contract Proposal Management Professional at Kyndryl, you will immerse yourself..." That's description of role. Could be About the role. - Responsibilities: The list of duties from that paragraph (gather documents, conduct credit checks, manage bid budgets, etc). Could be a

. - Requirements: Required Skills And Experience bullet list (though it's paragraph). Could be
. - Skills: Preferred Skills And Experience maybe. - Benefits: Benefits description (medical, dental, etc) plus bonus program. - Pay: Compensation range details. We must not include boilerplate like "Who We Are", "Your Future at Kyndryl", "Who You Are", "Being You", "What You Can Expect", "Get Referred!" etc. Those are likely fluff but may contain substantive info? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Who We Are" maybe not boilerplate but could be considered generic. However they said preserve ALL substantive information; do NOT invent or summarize away detail. The "Who We Are" is about company mission; could be considered substantive? But they said prefer a few substantive sections over many thin ones. Might include as About the company? But headings list does not include About the company; only About the role. So we likely omit "Who We Are". Similarly "Your Future at Kyndryl" maybe not needed. "Who You Are" maybe traits; could be part of Requirements or Skills? Might be considered soft skills. Could include under Skills or Requirements. But we need to decide. We need to preserve ALL substantive information. If we omit "Who We Are" we lose that info. But maybe it's considered boilerplate? It's a generic mission statement; could be considered boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It didn't say remove generic marketing fluff. But they said prefer a few substantive sections over many thin ones. Might still include as a section like "About Kyndryl" but not in allowed headings. Since only allowed headings are those listed, we should not create other headings. So we must fit that info into existing sections or drop it. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." It doesn't forbid other headings besides those listed, but they gave a list of headings to use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use only those headings. So we must map content into those. Thus we need to decide where to put "Who We Are" etc. Could fold into About the role? Not appropriate. Could be omitted as minor metadata? It's not metadata; it's about company. Might be considered boilerplate? I'd argue it's generic fluff that can be omitted per "prefer a few substantive sections". The instruction: "Prefer a few substantive sections over many thin ones." So we can drop less substantive fluff. Thus we will include sections: About the role (from The Role paragraph), Responsibilities (list of duties), Requirements (Required Skills And Experience), Skills (Preferred Skills And Experience), Pay (compensation range), Benefits (benefits description, bonus program). No Schedule. We must not include placeholder text like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. About the role: The paragraph starting "As a Contract Proposal Management Professional at Kyndryl, you will immerse yourself in the world of bid coordination and management." Continue until maybe before "Your Future at Kyndryl". Let's capture that paragraph fully. Original text: "The Role As a Contract Proposal Management Professional at Kyndryl, you will immerse yourself in the world of bid coordination and management. From the inception of a bid, you will orchestrate the efforts of the bid team. You will gather and organize mandatory documents from various parties, ensuring everything is meticulously stored in the designated tools. In collaboration with the Seller, you will conduct credit checks and validate customer information. Your role will involve managing bid budgets meticulously, including opening account IDs, tracking budget usage, and sending out weekly budget reports. You'll ensure that the Seller and team are always aware of the budget status, raising alerts if expenditures exceed a high percentage of the budget. You'll be crucial in ensuring process compliance and attending crucial release calls throughout the bid stages. Supporting the Seller, you will help manage the project plan, including setting milestones, planning deliverables, and tracking assignments. Your coordination skills will extend to engaging resources and aligned functions within and outside the Q2C organization. Your responsibilities will also encompass collecting mandatory approvals for price, credit, terms and conditions, legal, and risk assessments. You'll assist with compliance tests, SOX tests, and audits, ensuring the validity of process documentation. Your expertise in process consultancy and artifact management will be critical. Finally, you'll prepare mandatory documents and facilitate a smooth handover for contract registration, ensuring every detail is in place for successful bid completion. Your role is pivotal in navigating the complexities of proposal management, making each project a success from start to finish." That's the role description. We can put that in

under

About the role

. Responsibilities: Could be a list of duties extracted from that paragraph. But we already have the paragraph describing responsibilities. To avoid duplication, we could keep the paragraph as About the role and then Responsibilities as a list summarizing duties. However that would duplicate content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put the paragraph in About the role and also list responsibilities, we are duplicating but not losing info. Might be okay but could be considered thin sections. Better to have About the role as a brief overview and Responsibilities as detailed list. But we need to ensure we don't lose any detail. We could split: About the role short summary (first sentence) and then Responsibilities list with all duties. However the instruction says do not repeat the job title as a heading; not about repeating content. It's okay to have overlapping content as long as we preserve all info. But we risk being considered thin sections if we split too much. However we can keep About the role as the paragraph and Responsibilities as a list derived from same paragraph but that would be duplication. Might be acceptable but maybe they'd prefer not to duplicate. Let's think: The instruction: "Prefer a few substantive sections over many thin ones." Having both About the role and Responsibilities with overlapping content could be considered thin. Maybe we should combine: Use About the role for overview and Responsibilities for list, but ensure each has substantive unique content. We could make About the role a short summary (first two sentences) and Responsibilities a detailed list covering all duties. That way we preserve all info without much duplication. Let's craft: About the role: "As a Contract Proposal Management Professional at Kyndryl, you will immerse yourself in the world of bid coordination and management, orchestrating bid team efforts from inception to completion." That's a summary. Responsibilities: list items: - Orchestrate the efforts of the bid team from inception of a bid. - Gather and organize mandatory documents from various parties, ensuring meticulous storage in designated tools. - In collaboration with the Seller, conduct credit checks and validate customer information. - Manage bid budgets meticulously: opening account IDs, tracking budget usage, sending weekly budget reports. - Ensure Seller and team are aware of budget status, raising alerts if expenditures exceed a high percentage of the budget. - Ensure process compliance and attend crucial release calls throughout bid stages. - Support the Seller in managing the project plan: setting milestones, planning deliverables, tracking assignments. - Engage resources and aligned functions within and outside the Q2C organization. - Collect mandatory approvals for price, credit, terms and conditions, legal, and risk assessments. - Assist with compliance tests, SOX tests, and audits, ensuring validity of process documentation. - Prepare mandatory documents and facilitate smooth handover for contract registration, ensuring every detail is in place for successful bid completion. That covers all. Now Requirements: Required Skills And Experience paragraph: "Required Skills And Experience 3+ years of experience in a business setting with exposure to business controls and risk managementExperience in Go To Market (GTM) proposals / Large Deal Design3+ years of experience working with vendorsDemonstrated business writing skillsExperience driving a project to completion" It seems missing punctuation; we need to parse into list items: - 3+ years of experience in a business setting with exposure to business controls and risk management - Experience in Go To Market (GTM) proposals / Large Deal Design - 3+ years of experience working with vendors - Demonstrated business writing skills - Experience driving a project to completion We'll output as
• . Skills: Preferred Skills And Experience: "Preferred Skills And Experience Have a growth mindsetDemonstrated leadership, time management, and problem-solving skills" List: - Have a growth mindset - Demonstrated leadership, time management, and problem-solving skills Now Pay: The compensation range details. Paragraph: "Pay And Benefits The compensation range for the position in the U.S. is - $124,920 to $237,480 based on a full-time schedule. Your actual compensation may vary depending on your geography, job-related skills and experience. For part-time roles, the compensation will be adjusted appropriately. The pay or salary range will not be below any applicable state, city or local minimum wage requirement. There is a different applicable compensation range for the following work locations: California (San Francisco Bay Area): $149,880 to $284,880 California (All Other): $137,400 to $261,120 Colorado: $124,920 to $237,480 Massachusetts/ Virginia: $124,920 to $261,120 New York City: $149,880 to $284,880 Washington: $137,400 to $261,120 Washington DC: $137,400 to $261,120 This position will be eligible for Kyndryl’s discretionary annual bonus program, based