Jobs · Oregon

Knowledge Manager

PAE · Portland, OR · 1 mo ago
Hybrid$91k–$122k/yrFull-time
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use
  • for any list of duties/requirements/benefits, and

    for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading with filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting and extract relevant content. The posting includes: - The Opportunity: description of role (knowledge manager). This is like "About the role" maybe. - Who We Are: description of company. - What You'll Do: responsibilities. - What You Bring: qualifications/requirements/skills. - What We Offer: benefits, pay, schedule. - What We’re Made Of: company history, maybe not needed? Could be part of About the role? Might be considered boilerplate? It's about company but not role specifics. Might be considered optional; but we can include as part of "About the company" maybe not required. The instruction: include a section ONLY when posting has real, specific content for it. The "What We’re Made Of" is specific content about company. Could be part of "About the role"? But we have "Who We Are" already. Could combine. We need sections: maybe "About the role", "Responsibilities", "Qualifications", "Benefits", "Pay". Schedule: they mention hybrid work schedule. So schedule is present. We need to avoid filler like "commensurate with experience" etc. Not present. We need to use

    for each section heading. We need to use
    • for any list of duties/requirements/benefits. We need to use

      for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we need to strip out: - "Fine Print" about third party recruiters etc. That's legal boilerplate; remove. - EEO statement: "In order to provide equal employment..." remove. - "What We’re Made Of" maybe not boilerplate but could be considered company description; but we already have "Who Are". Might keep as part of "About the company" but we can combine. - "To learn more about our comprehensive benefits package, visit ..." maybe keep as link? It's part of benefits. Could keep as

      with link. - "This information is provided per the Equal Pay Act" maybe legal; remove. - "Our commitment to pay equity ..." maybe legal; remove. - "To learn more about pay equity..." remove. - "Living Future: Just Label Certification." remove. - "To find out more visit our website." remove. - "What We’re Made Of" maybe keep as part of "About the company" but we already have "Who We Are". Could merge. - "Founded in 1967..." etc. Might be considered company description; could be part of "About the company". Might keep as prose under "About the company". But we need to decide sections. We have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine some: maybe "About the role" includes Who We Are and The Opportunity? But The Opportunity is role description. Who We Are is company. Could be separate "About the company". But not in list; we could use "About the role" for role description and "About the company" not in allowed headings? The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we could also use other headings? Probably stick to those. So we can use About the role for role description and maybe include company info there? Or we could use About the role for role description and maybe not include company description at all (since not required). But we need to preserve ALL substantive information; we cannot omit company description if it's substantive. However, maybe "Who We Are" is considered boilerplate? It's describing the firm; could be considered substantive about the employer. Might be needed. We could create a section "About the company" but not in the list; but instruction says use those as examples, not exclusive. It says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use other headings as long as they are appropriate. But to be safe, we could incorporate company description into About the role section. Thus About the role will contain both The Opportunity and Who We Are (company description). That preserves info. Responsibilities: from "What You'll Do". That's a list of duties; we can turn into
      • . Qualifications/Requirements/Skills: from "What You Bring". This includes education, experience, skills, certifications. We could split into Requirements (education/experience) and Skills (specific abilities). But we can combine into one section "Requirements" or "Qualifications". The instruction says prefer few substantive sections over many thin ones. So maybe one section "Qualifications" that includes education, experience, skills, certifications. Benefits: from "What We Offer" includes benefits list. We'll make Benefits section. Pay: from "What We Offer" includes hiring base salary range and overtime eligibility. We'll make Pay section. Schedule: from "What We Offer" includes hybrid work schedule. We'll make Schedule section. We need to avoid duplication: The benefits list includes many items; we need to list them as
        • . We need to preserve all substantive information: include details like base salary range, overtime eligibility, health insurance, 401k profit sharing, professional development reimbursements, commuter/parking stipend, cell phone stipend, life insurance, disability benefits, hybrid work schedule, Employee Assistance Program, 9 paid holidays including additional employee-selected day, PTO for sick leave, family leave, community service, holidays and vacation. Also note: "To learn more about our comprehensive benefits package, visit https://www.pae-engineers.com/careers/benefits." Keep as a link. Also note: "The base salary is one component of PAE’s competitive compensation package for employees. We take into consideration a variety of factors including but not limited to skills, abilities, experience, education, credentials, internal equity and geographic location in determining exact salary offered. At PAE, employees are eligible for annual compensation reviews based on performance and business needs. The above range represents PAE's good faith and reasonable estimate of the range of possible compensation at the time of posting." This is substantive about pay; we can include in Pay section as prose. Also note: "This position is eligible for time and a half overtime pay." Include. Also note: "In addition, PAE offers a comprehensive benefits package which includes the following:" then list. Now we need to remove boilerplate: The "Fine Print", EEO, pay equity statements, JUST label, etc. Also remove duplicated lines: I don't see duplicates. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

          About the role

          ... combine The Opportunity and Who We Are ...

          Responsibilities

          • ... each duty ...

          Qualifications

          ... education, experience, skills, certifications ... maybe use

            for list? The instruction: use
            • for any list of duties/requirements/benefits. So qualifications is a list of requirements; we should use
              • . Similarly skills could be list but we can combine. Thus Qualifications section will have
                • for each requirement/skill. But we need to preserve all detail; we can break into items. Let's extract from "What You Bring": - Bachelor's degree or equivalent combination of education and relevant professional experience. - 5+ years of experience in knowledge management, learning and development, organizational learning, instructional design, employee enablement, content strategy, or related field. - Demonstrated experience in Learning & Development or organizational learning, including experience connecting knowledge resources to employee learning, performance, or development. - Advanced experience developing or improving enterprise knowledge management practices and implementing or managing an intranet, knowledge platform, digital workplace, or similar employee technology - Strong project and change management capabilities with effective written, verbal, facilitation, and stakeholder-management skills. - Ability to translate complex organizational needs into practical processes and employee experiences and use data to inform decisions. - Experience in architecture, engineering, consulting, professional services, or another knowledge-intensive organization preferred. - Experience with Microsoft 365, SharePoint, Teams, enterprise search, or comparable knowledge and collaboration platforms. - Proven experience implementing or supporting AI-enabled enterprise search, copilots, assistants, or retrieval-based knowledge solutions. - Knowledge management, change management, project management, information architecture, or related professional certification preferred. - Knowledge management and organizational learning principles. - Understanding of adult learning and performance-support principles. - Information architecture, taxonomy, and content governance. - Knowledge capture and facilitation. - Ability to translate complex information into accessible, reusable resources. - Strong systems thinking and information organization. - Consulting and stakeholder partnership. - Change management and adoption. - Project and process management. - Strong written and verbal communication. - Understanding of enterprise search and AI-enabled knowledge retrieval. - Ability to influence and build networks across functions. That's many items; we can list each as
                • . Now Benefits section: list items from "What We Offer": - Employer paid health insurance (medical, dental, vision) - Annual 401k profit sharing based on company profit for the year and account contribution - Professional development reimbursements including state registration and professional association dues - Employer paid commuter/parking stipend - Cell phone stipend - Life insurance and disability benefits - Hybrid work schedule (but schedule separate) - Employee Assistance Program - 9 paid holidays including an additional employee-selected day - Paid time off for sick leave, family leave, community service, holidays and vacation - To learn more about our comprehensive benefits package, visit https://www.pae-engineers.com/careers/benefits. We could keep hybrid work schedule in Benefits or Schedule; but we have Schedule section separate. Pay section: include base salary range, overtime eligibility, description of compensation factors, annual compensation reviews, good faith estimate. Schedule section: hybrid work schedule. Now About the role: combine The Opportunity and Who We Are. The Opportunity paragraph: "The Knowledge Manager advances PAE's learning and knowledge strategy by helping employees access, share, and apply the collective expertise of the firm. The role leads PAE's approach to capturing, organizing, governing, and leveraging organizational knowledge and serves as the business owner for PAE's enterprise knowledge platform/intranet. Working as part of the Learning & Development function, the Knowledge Manager partners with L&D colleagues, Communications, Information Systems (IS), technical leaders, subject matter experts, project teams, and other business functions to connect formal learning with knowledge available in the flow of work. The role helps PAE scale its collective expertise by making trusted knowledge and learning resources easier to find, share, reuse, and maintain. A key priority is preparing PAE's knowledge ecosystem for AI-powered search, assistants, and emerging technologies while preserving institutional knowledge, accelerating employee learning, and reducing duplication of effort." Who We Are: "PAE is an engineering and design firm that turns complex challenges into reality. By leveraging the latest technologies, we solve problems in unique ways, and our designs enable buildings and communities to be more resilient and efficient. PAE is trusted by our

Similar jobs

Knowledge Manager

Phoenix Group of VirginiaBremerton, WA· 1 wk ago
Information Technologyapply on workforcenow.adp.com

Knowledge Manager

HonorVet TechnologiesRaleigh, NC· 2 wk ago
apply on www1.jobdiva.com

Knowledge Manager

SHP Legal ServicesNashville, TN· 3 wk ago
apply on lssstrategicpartners.careers.hibob.com

Knowledge Manager

Strategy Consulting Team, LLCArlington, VA· 1 mo ago
Information Technology$100k–$108k/yrapply on grnh.se