Service Level Manager

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. We must not repeat job title. Must not include Job ID etc. Remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Sections present: - Who We Are (company description) – could be "About the role"? Actually "Who We Are" is about company, not role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - What You Get To Do (description of role) – could be "About the role" or "Responsibilities"? Actually "What You Get To Do" describes duties. Could be placed under "Responsibilities". Also there is a list "Essential Functions and Responsibilities:" with bullet points. - What You Have (education/experience) – could be "Requirements" or "Qualifications". Also "Working Conditions and Environment" includes some requirements (authorization to work, travel, physical). Might be part of Requirements. - What You Will Get (benefits) – list of benefits. We also have "Working Conditions and Environment" includes travel, physical requirements, authorization to work, passport, office etiquette. That could be part of "Requirements" or maybe separate but we only have set headings. Could include under "Requirements" or maybe "Skills"? Probably "Requirements". We have no explicit Pay or Schedule info besides "2 remote days per week", "Half day Fridays". That's schedule info. So we can create a Schedule section with those. Pay: "Industry competitive compensation" – that's vague but it's a statement. The instruction says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "Industry competitive compensation" is somewhat vague but it's a statement about pay. Is that considered filler? It's not a specific number but it's a statement. The instruction says avoid filler like "commensurate with experience". "Industry competitive compensation" is similar vague. Might be considered filler. Safer to not create Pay section unless we have specific pay info. We don't have numbers. So omit Pay. Benefits: we have a list: 2 remote days per week, Half day Fridays, beautiful new office, industry competitive compensation (maybe skip), great benefits..., 401k..., Paid Vacation & Holidays, Profit Sharing, Paid Parental Leave, Subsidized Daycare, Tuition Reimbursement, Pet Insurance, Subsidized food delivery, Monthly celebrations, Quarterly employee events, Corporate Social Responsibility including recycling, sustainability and volunteering. Also "Half day Fridays" and "2 remote days per week" are schedule but could be benefits. We'll put schedule separate. Thus we will have sections: - About the role (maybe from "Who We Are"? Actually "Who We Are" is company overview. Could be placed under About the role? The instruction says About the role heading for section headings (e.g. About the role, Responsibilities...). So we can put company description under About the role? Might be weird but we need to use headings only when posting has real specific content for it. The posting has "Who We Are" describing company. That's not exactly about the role but could be considered About the role? Better to put under "About the role" a brief description of the role? But we have "What You Get To Do" which describes role. So we could put that under About the role. Or we could put under Responsibilities. The instruction says prefer a few substantive sections over many thin ones. So we could combine. Let's decide: Section: About the role – include a brief summary of the role: "A Service Level Manager is responsible for Customer Service contract management in their defined area. That can include negotiating a new contract with a customer, ...". Actually that's from "What You Get To Do". We'll put that as prose. Section: Responsibilities – list the essential functions and responsibilities bullet points. Section: Requirements – include education/experience, working conditions (authorization to work, travel, physical requirements). Could also include "Working Conditions and Environment". Section: Qualifications – maybe we can combine with Requirements? But we need to avoid thin sections. Could merge Requirements and Qualifications into one? But we have both headings allowed. To avoid thin, we could put education/experience under Requirements, and skills under Skills. Qualifications maybe not needed. Let's see. We have: - Bachelor’s degree, preferably in business administration, legal studies or related field or equivalent combination of education, training and experience. - 0-3 years of experience as a contract administrator or manager preferred. - Ability to draft/review contract agreements for final approval. - Basic knowledge of laws, regulations, and contract trends that will impact the businesses' goals and objectives. - Working knowledge of intralogistics systems is a plus. - Ability to work independently and on a team. - Proficient knowledge of Microsoft Office or related software. - SAP knowledge is a plus. - Excellent communication skills both written and verbal. - Strong presentation skills. These are qualifications/skills. Could split into Requirements (education/experience) and Skills (the rest). Then we have Working Conditions and Environment (authorization to work, travel, physical requirements, office etiquette). Could be part of Requirements or separate but we don't have a heading for that. Could add under Requirements as additional bullets. Thus sections: - About the role (prose) - Responsibilities (ul li) - Requirements (ul li) – education/experience, authorization to work, travel, physical requirements, office etiquette. - Skills (ul li) – abilities, knowledge, software, communication, presentation. - Benefits (ul li) – list of benefits (excluding schedule items? We'll include remote days and half day Fridays under Schedule maybe.) - Schedule (ul li) – 2 remote days per week, Half day Fridays. We must not create Pay section. We must not include boilerplate like EEO, drug-free workplace, etc. Remove those. Now ensure we preserve all substantive information. Let's extract. From Who We Are: description of KNAPP. Should we include? It's substantive but not about role. The instruction says we can include sections only when posting has real specific content for it. We have no heading for company overview. Could we include it under About the role? Might be misrepresenting. But we could add a brief paragraph about company under About the role? The heading is About the role, not About the company. However we could treat About the role as including company context? Might be okay. But maybe better to omit company description because we don't have a heading for it and we shouldn't invent a 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, but says use those for section headings. It doesn't say we cannot have other headings, but we should follow the pattern. It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those headings only. So we need to map content to those headings. If we have content that doesn't fit, we could either omit or put under the closest. The company description could go under About the role? Not ideal but maybe acceptable. However the instruction says "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 adding other headings besides those examples, but the examples are given. Safer to stick to those headings. Thus we will try to fit company description under About the role as a brief intro: "KNAPP brings new technology to warehouse automation..." etc. Now let's gather content. About the role: combine Who We Are and What You Get To Do? Actually Who We Are is company, not role. But we can include both: first paragraph about company, second about role. That's okay. Responsibilities: list from Essential Functions and Responsibilities. Let's extract bullet points: - Negotiate and draft service contracts based on company’s standard templates and in partnership with Corporate Counsel and company leadership. - Perform Independent and committed contract related support of new and existing customers. This includes but is not limited to answering customer and internal questions related to contracts, amendments, billing plans, monitoring project deadlines and service provision dates. - Acts as main point of contact for questions regarding contract structures and contractual services for customers, internal departments, and other KNAPP subsidiaries. This Includes close communication and coordination internally and with parent company in Austria. - Optimize and adapt existing service contracts, in document form and SAP, based on customer requirements. - Add offers and contracts to ERP system. - Support Management team in new business initiatives when required. - Perform all other tasks and duties assigned. Also earlier: "A Service Level Manager is responsible for Customer Service contract management in their defined area. That can include negotiating a new contract with a customer, which is done with support of Corporate Counsel, Customer Service Management and Department leadership, as well as minor amendments, side letters or LOIs. Further the Service Level Manager is able use the SAP contract tool to set up or administrate contracts in the system. Focus is contract related long-term care for new and existing customers with considerable processes and existing and defined work orders." We could incorporate that as prose before list, but we already have list. Might be duplicate. We'll keep list as responsibilities; we can also include a brief intro paragraph. Now Requirements: - Bachelor’s degree, preferably in business administration, legal studies or related field or equivalent combination of education, training and experience. - 0-3 years of experience as a contract administrator or manager preferred. - Authorization to work in the U.S. Passport or ability to obtain passport. - Professional office etiquette is required at all times. - Travel required up to 30%. - Physical requirements: sitting for long periods of time, standing, walking, speaking, visual acuity, finger dexterity, listening, reaching at arm’s length, and lifting up to 25 pounds. Also maybe "Working Conditions and Environment" includes those. Now Skills: - Ability to draft/review contract agreements for final approval. - Basic knowledge of laws, regulations, and contract trends that will impact the businesses' goals and objectives. - Working knowledge of intralogistics systems is a plus. - Ability to work independently and on a team. - Proficient knowledge of Microsoft Office or related software. - SAP knowledge is a plus. - Excellent communication skills both written and verbal. - Strong presentation skills. Now Benefits: - 2 remote days per week (but that's schedule; we might move to Schedule) - Half day Fridays (schedule) - A beautiful new, state-of-the-art office complex in Kennesaw, GA - Industry competitive compensation (maybe skip as filler) - Great benefits with better than average employer contributions, including health, dental, vision, life insurance, Flexible Spending Accounts, Short & Long Term Disability and more! - 401k with a very generous employer match and no vesting! - Paid Vacation & Holidays - Profit Sharing - Paid Parental Leave - Subsidized Daycare - Tuition Reimbursement - Pet Insurance - Subsidized food delivery - Monthly celebrations - Quarterly employee events - Corporate Social Responsibility including recycling, sustainability and volunteering We could keep "Industry competitive compensation" as a benefit line but it's vague. Might be considered filler. Safer to omit. Now Schedule: - 2 remote days per week - Half day Fridays Now we need to output HTML fragment with

headings and