Senior Contracts Manager

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes: Work Mode: Hybrid 3+ day per week in our Salt Lake City office (that's schedule? maybe schedule). Department: Legal (maybe not needed). About The Company (prose). About The Team (prose). About The Opportunity (prose). Then "In Addition, You’ll Be Responsible For" with bullet list of responsibilities (Commercial Contracting & Negotiation, Business Partnership & Commercial Judgement, Contracting Operations & Scalability, Cross-Functional Support). Then "Skills & Experience Must-Haves" list. Then "Nice-to-Haves". Then "Why choose LearnUpon?" (benefits). Then "Hiring Process" (maybe not needed). Then note about AI etc (boilerplate to remove). Also "Work Mode: Hybrid 3+ day per week in our Salt Lake City office" could be schedule or maybe location. Since we have schedule section only if posting actually states schedule. It does: Hybrid 3+ day per week in Salt Lake City office. So we can include a Schedule section with that. Pay: not mentioned, so omit. Benefits: "Why choose LearnUpon?" includes comprehensive rewards, generous time off, meaningful investment in growth and development. That's benefits. So include Benefits section. Qualifications: Might be covered by Skills & Experience Must-Haves (experience, degree). Could treat as Qualifications. But we have Skills section for skills. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map content accordingly. We have About the role? The posting includes About The Opportunity (role description). Could map to About the role. Responsibilities: the bullet list under "In Addition, You’ll Be Responsible For". Requirements: maybe the Must-Haves? Could be Requirements. Qualifications: maybe degree or equivalent? Could be separate but we can combine. Skills: maybe the skills listed (commercial judgement, drafting, communication, etc). Could be separate. But we must not create thin sections. Prefer few substantive sections. Could combine Must-Haves and Nice-to-Haves into Requirements/Qualifications/Skills. Better to have sections: About the role (About The Opportunity), Responsibilities (the bullet list), Requirements (Must-Haves), Qualifications (maybe degree?), Skills (maybe the skill bullet points?), Benefits (Why choose LearnUpon?), Schedule (Hybrid 3+ day per week...). But we need to avoid duplication. Let's extract content. About The Company: prose about LearnUpon. Could be part of About the role? Might be separate but we could include as About the role? The instruction: About the role heading for role description. But we have About The Company and About The Team and About The Opportunity. Could combine into About the role? Might be too much. However we need to preserve all substantive information. We could create sections: About the company, About the team, About the role. But headings limited to given list; we could use About the role for the opportunity description, and maybe include company/team within that? But we risk losing info. However we could treat About the company and About the team as prose under About the role heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should map content to those headings. Thus we need to decide which headings to include based on content. We have: - About the role: could include About The Opportunity (role description) plus maybe About The Team and About The Company as context? Might be okay. - Responsibilities: the bullet list under "In Addition, You’ll Be Responsible For". - Requirements: the Must-Haves list. - Qualifications: maybe the Nice-to-Haves? Or degree requirement? Could treat Nice-to-Haves as Qualifications? Or we could skip Qualifications if not distinct. - Skills: maybe the skill bullet points like "Strong working knowledge of key SaaS contracting concepts..." etc. Those are part of Must-Haves actually. Could split. But to avoid thin sections, we could combine Requirements and Qualifications into one section called Requirements (or Qualifications). But we need to follow instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all; we can choose subset. Thus we could have:

About the role

(includes About The Company, About The Team, About The Opportunity)

Responsibilities

(list)

Requirements

(Must-Haves)

Skills

(maybe the skill-based items like commercial judgement, drafting, communication, etc.) But those are already in Must-Haves. Could instead have

Qualifications

for Nice-to-Haves.

Benefits

(Why choose LearnUpon?)

Schedule

(Hybrid 3+ day per week in Salt Lake City office) We must not include Pay. Now we need to extract exact prose, preserving all substantive information, not inventing or summarizing away detail. Let's gather content. About The Company: "LearnUpon partners with over 1,600 organisations globally to unlock the potential of employees, customers & members through learning that’s easy, scalable and focused on results. Read more about life at LearnUpon here." We should keep the sentence, maybe drop "Read more about life at LearnUpon here." as it's a link instruction? It's not boilerplate? It's a call to action but maybe considered navigation? It's not EEO etc. It's a link to learn more; could be considered boilerplate? It's not explicitly listed as boilerplate to remove, but it's a promotional link. Might be okay to keep. However we should avoid navigation/link instructions? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Read more about life at LearnUpon here." is not navigation per se, but it's a link. Might be considered navigation? Safer to keep? It's not essential substantive info about the role; it's just a reference. Could drop as it's not substantive. I'd drop it. About The Team: "The Legal team at LearnUpon functions as a strategic partner to the business, ensuring we can negotiate commercial agreements efficiently while managing contractual risk. By taking end-to-end ownership of customer and vendor contracting, maintaining established legal positions, and supporting cross-functional teams like Sales and Finance, the Legal team enables LearnUpon to execute deals smoothly and meet our most ambitious growth targets securely." Keep that. About The Opportunity: "As our Senior Contracts Manager reporting to the Commercial Counsel, you will serve as a key individual contributor driving end-to-end commercial contracting across LearnUpon. By independently managing complex SaaS customer negotiations, vendor agreements, and contracting workflows, you will accelerate revenue execution and build scalable legal operations. Your expertise and commercial judgement will act as a catalyst for our North Star by enabling fast, low-risk business growth in our global markets." Keep that. Now Responsibilities bullet list: The text after "In Addition, You’ll Be Responsible For" includes four bold headings with descriptions. We need to convert to

• items. Each heading could be a list item with its description. Let's extract: 1. Commercial Contracting & Negotiation: Independently drafting, reviewing, and negotiating customer and vendor commercial agreements (including SaaS subscription agreements, MSAs, DPAs, NDAs, and order forms); leading end-to-end enterprise negotiations directly with procurement and external legal counsel; and analysing key SaaS issues such as limitation of liability, IP, DPAs, and service levels. 2. Business Partnership & Commercial Judgement: Partnering closely with Sales, Finance, and Security to provide practical guidance; exercising independent judgement to resolve issues within established playbooks; and escalating material or novel risks appropriately to the Commercial Counsel. 3. Contracting Operations & Scalability: Reinforcing established contracting processes, templates, and escalation pathways; maintaining accurate contract records; contributing to clause libraries and playbooks; and helping drive adoption of CLM and contracting technology. 4. Cross-Functional Support: Collaborating with Security/Privacy on data protection requirements and assisting Finance on commercial terms, and developing contracting guidance/training for business teams. We need to preserve all detail. Now Requirements (Must-Haves): List: - 7+ years of relevant commercial contracting experience, preferably within an in-house SaaS, software, or technology environment. - Demonstrated experience independently drafting and negotiating complex customer-facing agreements, including enterprise SaaS agreements, MSAs, DPAs, order forms, and vendor agreements. - Strong working knowledge of key SaaS contracting concepts (limitation of liability, indemnification, IP, confidentiality, warranties, data protection, security, SLAs). - Proven ability to lead direct negotiations with sophisticated customers, procurement teams, and external legal counsel. - Excellent commercial judgement, drafting, and communication skills with the ability to translate complex legal issues into pragmatic, business-friendly guidance. - Bachelor’s degree or equivalent relevant professional experience. - Experience using AI tools to streamline tasks and improve efficiencies. - Experience with Contract Lifecycle Management (CLM) systems and integrated CRM/CLM environments. We need to keep each as
• . Now Nice-to-Haves (could be Qualifications): - Legal qualification, paralegal qualification, or recognised contracts management credential. - If you don’t tick every box but believe this role is a mutually good fit, please don’t hesitate to apply. We’d love to hear from you. The second sentence is encouragement to apply; maybe considered application instruction? It's not exactly instruction to apply but encouragement. Might be considered boilerplate? It's not EEO etc. Could keep as part of Qualifications? It's not a qualification. Might be better to omit as it's not a qualification. The instruction says remove application instructions. This is encouraging to apply, maybe considered application instruction. Safer to drop that sentence. Keep only the qualification bullet. Thus Qualifications section: Legal qualification, paralegal qualification, or recognised contracts management credential. Now Benefits section: "Why choose LearnUpon? From comprehensive rewards and generous time off to meaningful investment in your growth and development, LearnUpon gives you the support, trust, and opportunity to do the most impactful work of your career. Learn more here." We should keep the substantive info: comprehensive rewards, generous time off, meaningful investment in growth and development, support, trust, opportunity to do most impactful work. The "Learn more here." is a link; could drop as navigation? Might be considered navigation. Safer to drop. Thus Benefits: comprehensive rewards and generous time off; meaningful investment in your growth and development; support, trust, and opportunity to do the most impactful work of your career. Now Schedule: "Hybrid 3+ day per week in our Salt Lake City office". Also Work Mode: Hybrid 3+ day per week in our Salt Lake City office. So schedule: Hybrid 3+ day per week in Salt Lake City office. Now we need to output HTML fragment only, no /, no markdown. We'll produce:

  About the role

  LearnUpon partners with over 1,600 organisations globally to unlock the potential of employees, customers & members through learning that’s easy, scalable and focused on results.

  The Legal team at LearnUpon functions as a strategic partner to the business, ensuring we can negotiate commercial agreements efficiently while managing contractual risk. By taking end-to-end ownership of customer and vendor contracting, maintaining established legal positions, and supporting cross-functional teams like Sales