Team Lead CS Project Management
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Thus we need to decide which sections have real content. We have: - About the role: Could be "What You Get To Do" description. That's about role responsibilities. Could map to "Responsibilities". But we also have "What You Get To Do" which is essentially responsibilities. So we can put that under
Responsibilities
. - "Who We Are" is company overview, could be "About the role"? Actually "About the role" is about the role, not company. The posting includes "Who We Are" which is company description. Might be considered "About the role"? Not exactly. But we could include a section "About the role" with description of role? The posting includes "What You Get To Do" which is role description. So we can put that under Responsibilities. - Requirements: The posting includes "What You Have" which lists qualifications: Bachelor's degree, 7 years experience, etc. That's requirements/qualifications. Could be under Requirements or Qualifications. We need to decide which sections to include. The instruction says prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But they are separate headings allowed. However we should only include sections with real content. We have content for both Requirements and Qualifications (they overlap). Could combine into one heading like "Requirements" and include all. Or we could have both but they'd be similar. Better to have one section "Requirements" covering education, experience, skills. - Skills: The posting includes specific skills: WMS, WCS, WES, controls integration, automated material handling equipment, leadership, communication, executive-level presentation, managing escalations, prioritize demands, judgment. Those could be under Skills. - Benefits: The posting includes "What You Will Get" with many benefits: remote days, half day Fridays, office, compensation, benefits, 401k, vacation, holidays, profit sharing, parental leave, subsidized daycare, tuition reimbursement, pet insurance, subsidized food delivery, monthly celebrations, quarterly events, CSR. Also mentions "Industry competitive compensation". No specific pay numbers. So we can include Benefits section. - Pay: The posting does not give specific salary numbers, only "Industry competitive compensation". That's vague; not a specific number. According to instruction: never create Pay section unless posting actually states them. It states "Industry competitive compensation" but not a specific figure. Is that considered stating? It's generic. Likely we should not create Pay section because it's not specific. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have specific items, so we can include Benefits. Pay we have only generic statement, maybe we should omit Pay section. - Schedule: The posting includes "2 remote days per week", "Half day Fridays". That's schedule info. So we can include Schedule section. Thus sections: Responsibilities, Requirements (or Qualifications), Skills, Benefits, Schedule. Possibly also About the role? But we already have Responsibilities covering role description. Could also include About the role as company overview? But instruction says use headings e.g. About the role, Responsibilities, etc. Could include About the role with company description "Who We Are". That is substantive. So we could have About the role section with company overview. Then Responsibilities with "What You Get To Do". Then Requirements with "What You Have". Then Skills with specific technical/leadership skills. Then Benefits with "What You Will Get". Then Schedule with remote days and half day Fridays. We must not repeat job title as heading. Not include metadata like Work Conditions? Actually "Working Conditions and Environment:" includes authorization to work in US, travel, passport, office etiquette, travel ability, physical requirements. That could be part of Requirements or maybe a separate section? But we have limited headings; we could fold into Requirements or maybe a separate section like "Working Conditions". Not in allowed list but we could incorporate into Requirements or maybe not needed as separate heading. The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but 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 of those headings have content.
- About the role: Could be company description "Who We Are". That's about the role? Slightly off but we can treat as About the role (overview of company and role). We'll include.
- Responsibilities: "What You Get To Do" and the bullet list of essential functions.
- Requirements: "What You Have" (education, experience, etc.) plus maybe working conditions? But we can keep requirements as education/experience.
- Qualifications: Could be same as Requirements; but we might not need both. To avoid thin sections, we could combine Requirements and Qualifications into one heading, but we need to pick one. Since they ask to prefer few substantive sections, we could omit Qualifications and put all under Requirements. Or we could omit Requirements and put under Qualifications. Which is more appropriate? The posting includes "What You Have" which is qualifications. So we could use Qualifications heading. But we also have Requirements maybe not needed. Let's choose Qualifications.
- Skills: specific technical skills and leadership skills.
- Benefits: "What You Will Get".
- Schedule: remote days, half day Fridays.
- Pay: not specific, omit.
Thus we will output sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Schedule.
Now we need to format: About the role
then
...
for prose, and- for any list of duties/requirements/benefits.
We need to preserve ALL substantive information, not invent or summarize away detail. So we need to include all details from each section.
Let's extract content.
About the role (Who We Are):
"KNAPP brings new technology to warehouse automation. The KNAPP Group is a global provider of intelligent automation solutions for intralogistics and manufacturing, specializing in the sectors healthcare, fashion/apparel, general retail, food retail, industry and service. We live and breathe automation. We, more than 8,000 employees of the KNAPP Group across over 60 locations worldwide, shaping the future-oriented intralogistics industry, are dedicated to making complexity simple. One of KNAPP’s primary goals is to use continuous innovation to drive warehouse automation forward, always with the specific needs of the customers in mind. KNAPP Group’s unrelenting development activity is evident in everything from automated order picking systems and continuing refinement of container handling technology to its state-of-the-art, industry leading software solutions."
We need to keep that as prose (
). Possibly we could break into multiple paragraphs but one
is fine. Responsibilities: "What You Get To Do" paragraph plus the bullet list under Essential Functions and Responsibilities. Paragraph: "The Team Lead CS Project Management is accountable for leading and developing a team of Customer Service Project Managers while ensuring the successful execution of a portfolio of customer‑facing projects. This role combines people leadership, portfolio oversight, and advanced project management expertise to ensure delivery aligned with KNAPP standards for quality, safety, cost, and schedule. The Team Lead exercises independent judgment, provides escalation leadership, and serves as a primary interface between customers, cross‑functional internal teams, and management." Then bullet list: People Leadership & Team Management (with sub-bullets), Project & Portfolio Oversight, Cross‑Functional & Customer Collaboration. We need to preserve all details. So we need to include each bullet as
- . The sub-bullets are sentences; we can keep them as part of the
- text.
Thus we will have
- with
- for each top-level bullet, and inside each
- we can include the sentences.
We must not add extra headings inside.
Qualifications: "What You Have" paragraph plus bullet list.
Paragraph: "Bachelor’s degree or equivalent combination of education and relevant work experience. Minimum of 7 years of project or program management experience within warehouse automation, intralogistics, or material handling environments. Demonstrated success managing complex, customer‑facing, multi‑disciplinary projects. Demonstrated experience leading or supervising professional staff. Demonstrated working knowledge of WMS, WCS, WES systems, controls integration, and automated material handling equipment (e.g., AS/RS, conveyors, robotics). Demonstrated leadership, communication, and executive‑level presentation skills. Demonstrated ability to manage escalations, prioritize competing demands, and exercise sound judgment in dynamic environments."
That's all in one paragraph? Actually it's a series of sentences separated by periods. We'll keep as
. Skills: The posting includes specific skills: "Demonstrated working knowledge of WMS, WCS, WES systems, controls integration, and automated material handling equipment (e.g., AS/RS, conveyors, robotics). Demonstrated leadership, communication, and executive‑level presentation skills. Demonstrated ability to manage escalations, prioritize competing demands, and exercise sound judgment in dynamic environments." Those are already in Qualifications. But we might separate skills: technical skills (WMS, WCS, WES, controls integration, AS/RS, conveyors, robotics) and soft skills (leadership, communication, executive-level presentation, managing escalations, prioritize demands, judgment). However we already included them in Qualifications. To avoid duplication, we could move those to Skills section and keep Qualifications more about education/experience. Let's parse: The "What You Have" includes both education/experience and skills. We could split: Qualifications: education and experience (Bachelor's degree, 7 years experience, success managing complex projects, experience leading/supervising staff). Skills: technical and soft skills (WMS/WCS/WES, controls integration, automated material handling equipment, leadership, communication, executive-level presentation, managing escalations, prioritize demands, judgment). That seems reasonable. Thus Qualifications section will contain: - Bachelor’s degree or equivalent combination of education and relevant work experience. - Minimum of 7 years of project or program management experience within warehouse automation, intralogistics, or material handling environments. - Demonstrated success managing complex, customer‑facing, multi‑disciplinary projects. - Demonstrated experience leading or supervising professional staff. Skills section will contain: - Demonstrated working knowledge of WMS, WCS, WES systems, controls integration, and automated material handling equipment (e.g., AS/RS, conveyors, robotics). - Demonstrated leadership, communication, and executive‑level presentation skills. - Demonstrated ability to manage escalations, prioritize competing demands