Contract Specialist

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About the role (present). Responsibilities: bullet list under "As a Contract Specialist, you will…". Requirements: maybe "What is required is strong project management instinct..." but also "Our ideal candidate…" includes qualifications. There's also "What we offer…" which includes benefits. No explicit Pay or Schedule. Travel approx 15% is mentioned under responsibilities bullet list? Actually bullet list includes "Travel approximately 15 percent for customer meetings, kickoffs, and internal team sessions". That's under responsibilities. So schedule not given. Pay not given. Benefits: "What we offer…" includes bullet list of benefits. So we can include Benefits section. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. No Job ID. Remove boilerplate. We need to preserve all substantive information. Let's extract sections: About the role: paragraph(s) after "About the role". The text: "We are seeking a Contract Specialist to join the Sales Operations and Contracts team in North America. This role reports to the Director of Contracts and Sales Operations and works alongside our Sales Operations Specialist, who leads proposal development. Together, the team supports the full commercial cycle: sales support, proposal, contract, and hand-off. The Contract Specialist owns the contracting portion of that cycle and partners closely with Sales, Finance, outside counsel, and Project/Service Delivery to move agreements to signature without losing speed or accuracy. This is a coordination and execution role. No law degree is required. What is required is strong project management instinct, disciplined organization, excellent written and verbal communication, and the judgment to know when a commercial or schedule risk needs to be raised. You will also cross-train with the broader Sales Operations function, contributing to proposal responses, sales initiatives, and pipeline tracking as business needs shift." We can put that in

  . Responsibilities: bullet list after "As a Contract Specialist, you will…". The bullet list includes many items. We'll capture each bullet as

• . Also note the bullet about travel 15% is included there. Requirements: maybe "What is required is strong project management instinct..." but that is already in About the role. However we have a separate "Our ideal candidate…" which lists qualifications. That could be Requirements or Qualifications. The instruction says we can have sections Requirements, Qualifications, Skills. We need to decide based on content. The "Our ideal candidate…" includes bullet list of qualifications: degree, experience, project management skills, organization, written communication, verbal communication, ability to read agreement, Microsoft skills, experience with e-signature, Dynamics 365 CRM, contract lifecycle management tooling, exposure to software/SaaS/professional services/utility industry agreements, experience supporting RFP/proposal responses, self-motivator, travel 15% (but travel already in responsibilities). This seems like Qualifications. We could also have a Skills section for specific technical skills: Microsoft skills, e-signature, Dynamics 365 CRM, contract lifecycle management tooling. But we can incorporate those into Qualifications. Better to follow typical structure: About the role, Responsibilities, Qualifications, Benefits. Possibly also Requirements (maybe combine with Qualifications). Since we have both "What is required" and "Our ideal candidate…" we could treat "What is required" as Requirements (short paragraph) and "Our ideal candidate…" as Qualifications (list). But the instruction says prefer few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one section called Qualifications (or Requirements). However we need to use headings exactly as allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include only those with content. Let's see: - About the role: yes. - Responsibilities: yes. - Requirements: we have "What is required is strong project management instinct..." plus maybe the bullet list of qualifications could be considered requirements. But we have also Qualifications section. To avoid thin sections, we could put all candidate requirements under Qualifications and skip Requirements. Or we could put the short paragraph under Requirements and the bullet list under Qualifications. That would be two sections, each with content. That's acceptable. - Skills: we could extract specific skills: Microsoft Word with track changes, Excel, Outlook, Teams, SharePoint, DocuSign, Dynamics 365 CRM, contract lifecycle management tooling. That's a list. Could be Skills section. - Benefits: "What we offer…" bullet list. - Pay: not present -> omit. - Schedule: not present (travel% is not schedule) -> omit. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Now we need to ensure we don't repeat content. Let's draft. About the role: paragraph(s) as above. Requirements: short paragraph: "What is required is strong project management instinct, disciplined organization, excellent written and verbal communication, and the judgment to know when a commercial or schedule risk needs to be raised." Also maybe include "No law degree is required." but that's not a requirement; it's a note. Could include. Qualifications: bullet list from "Our ideal candidate…" including degree, experience, project management skills, organization, written communication, verbal communication, ability to read agreement, Microsoft skills, experience with e-signature, Dynamics 365 CRM, experience with contract lifecycle management tooling, exposure to software/SaaS/professional services/utility industry agreements, experience supporting RFP/proposal responses, self-motivator, travel 15% (though travel already in responsibilities, but we can keep). Might be duplicate but okay. Skills: bullet list of specific technical skills: Microsoft Word with track changes and comparison, Excel for tracking and reporting, Outlook, Teams, SharePoint for document management, experience with electronic signature platforms such as DocuSign, experience with Microsoft Dynamics 365 CRM, or a comparable CRM, experience with contract lifecycle management tooling, or a strong interest in helping select and implement one. But note that some of these overlap with Qualifications. To avoid duplication, we could keep Qualifications as broader (degree, experience, etc.) and Skills as specific technical proficiencies. That's fine. Benefits: bullet list from "What we offer…": Incredible work experience with a leading, award-winning international software vendor in the utilities sector; Working in a fast-changing, highly stable, AI-driven technology market; Working with a best-in-class A-Team of collaborative goal-minded individuals; Representing UMAX, a best-in-class and market leading tier one and tier two utility solution built on the Microsoft Dynamics 365 for Finance platform; Long term career development and opportunity for career advancement; An attractive and competitive compensation and benefits package. Now we need to output only HTML fragment, no extra text. Let's craft. We'll wrap each section in

  heading then content. For About the role:

  ...

  For Responsibilities:

  • ... each bullet

  For Requirements:

  ...

  For Qualifications:

  • ... each bullet

  For Skills:

  • ... each bullet

  For Benefits:

  • ... each bullet

  Make sure to preserve all substantive information. Let's extract bullet points exactly. Responsibilities bullets (from "As a Contract Specialist, you will…"): - Manage and track contracts from award through negotiation, execution, and hand-off to the project and field delivery teams, maintaining clear status and next-step visibility at every stage - Prepare, route, and track new customer agreements as well as amendments, change orders, extensions, renewals, support and maintenance agreements, statements of work, non-disclosure agreements, and teaming or subcontractor agreements - Work equally well on Itineris paper and on customer paper, including municipal and public-sector terms, and coordinate redlines between internal stakeholders and the customer - Maintain the contract repository and version control so that executed documents, signature records, and supporting correspondence are complete, current, and easy to retrieve - Track key dates and obligations, including effective dates, milestones, renewal and expiration windows, notice periods, insurance and bond requirements, and deliverable commitments - Identify, document, and communicate commercial, schedule, and delivery risks, and escalate items that require legal, finance, or executive review - Lead structured hand-off to the project team so that scope, pricing, payment terms, and customer commitments are understood before work begins - Serve as a responsive point of contact for contract-related questions after hand-off, researching executed terms and coordinating answers across internal teams and the customer - Partner with Finance on billing milestones, purchase orders, invoicing triggers, and contract value changes so that revenue recognition reflects the executed agreement - Maintain contract templates, clause libraries, checklists, and approval workflows, and recommend process improvements that shorten cycle time - Produce clear status reporting and metrics on contracts in flight, cycle times, and upcoming renewals for leadership review - Cross-train with the Sales Operations Specialist and assist with proposal and RFP responses, sales initiatives, and pipeline tracking and CRM hygiene during peak periods - Handle confidential customer, pricing, and company information with discretion and sound judgment - Travel approximately 15 percent for customer meetings, kickoffs, and internal team sessions Now Requirements paragraph: "What is required is strong project management instinct, disciplined organization, excellent written and verbal communication, and the judgment to know when a commercial or schedule risk needs to be raised." Also maybe include "No law degree is required." but that's not a requirement; it's a note. Could include as separate sentence: "No law degree is required." Might be okay. Qualifications bullets (from "Our ideal candidate…"): - a bachelor's degree in business administration, communications, supply chain, contract management, public administration, or a related field - a minimum of two years of experience in contracts, contract administration, procurement, or a closely related commercial function - demonstrated project management skills, with the ability to run multiple agreements on parallel timelines without losing track of commitments or deadlines - exceptional organization and follow-through, and comfort owning a process end to end with limited day-to-day direction - excellent written communication, including the ability to draft clear summaries, status updates, and customer correspondence that a non-specialist audience can act on - strong verbal communication and the confidence to facilitate discussions among sales, delivery, finance, counsel, and customer stakeholders - the ability to read an agreement closely, spot inconsistencies and missing terms, and raise questions and risks early rather than after signature - excellent Microsoft skills, including Word with track changes and comparison, Excel for tracking and reporting, Outlook, Teams, and SharePoint for document management - experience with electronic signature platforms such as DocuSign - experience with Microsoft Dynamics 365 CRM, or a comparable CRM - experience with contract lifecycle management tooling, or a strong interest in helping select and implement one - exposure to software, SaaS, professional services, or utility industry agreements, and to public-sector or municipal procurement processes - experience supporting RFP or proposal responses - a self-motivator willing to go the extra mile, with the ability to travel approximately 15 percent Note travel 15% appears again; we could keep but it's duplicate. Might be okay. Skills bullets: we could extract the specific technical skills from the qualifications list: Microsoft Word with track changes and comparison, Excel for tracking and reporting, Outlook, Teams, SharePoint for document management, experience with electronic signature platforms such as DocuSign, experience with Microsoft Dynamics 365 CRM, or a comparable CRM, experience with contract lifecycle management tooling, or a strong interest in helping select and implement one. But that overlaps with qualifications. To avoid duplication, maybe we don't need a separate Skills section; we could incorporate those into Qualifications.