Project Manager II

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. Preserve all substantive info. Remove boilerplate: cookie/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 followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Key sections: - Core Purpose and Core Values: maybe "About the role"? Actually "About the role" could be summary of purpose and values. Could also be "Our Company". But we need to decide which sections to include. We have: - Core Purpose: Building enduring relationships and strong communities - Core Values: list (Integrity, Commitment, Teamwork, Value People) - Our Company: description (founded 1897, etc.) - Summary: description of position responsibilities (planning, directing, coordinating activities) - Essential Duties and Responsibilities: long list of duties - Required Knowledge, Skills And Abilities: list - Preferred Knowledge, Skills And Abilities: list (ViewPoint software, driver's license, travel 25-75%) - Physical Demands: description - Salary Range: $102,000 to $140,000 annually, plus auto allowance and discretionary incentive program. - Why KA?: benefits description (Total Rewards package) - Also "Make A Positive Impact EOE / Vets / Disabled" is boilerplate EEO; remove. We need to decide sections: maybe "About the role" (core purpose/values/company summary), "Responsibilities" (essential duties), "Requirements" (required knowledge/skills/abilities), "Qualifications" maybe combine required and preferred? But we can have "Qualifications" for required, and "Preferred Qualifications" maybe not needed as separate heading? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose among those. We need to avoid filler. We have Pay: salary range given. So we can have

  Pay

  with

  Salary Range: $102,000 to $140,000 annually, plus auto allowance and discretionary incentive program.

  We have Benefits: description of Total Rewards package. So

  Benefits

  with
  • items. We have Schedule? Not given explicitly. Travel 25-75% maybe schedule? But schedule heading only if posting actually states schedule. It mentions travel percentage, not schedule. So we should not create Schedule section. We have Skills? Could be part of Requirements/Qualifications. But we could have a Skills section if we list skills. However we have Required Knowledge, Skills And Abilities and Preferred Knowledge, Skills And Abilities. Could combine into Requirements and Qualifications. But we need to avoid thin sections. Perhaps we make one section "Requirements" that includes both required and preferred? But we need to preserve all info. Could separate Required and Preferred as subheadings? Not allowed because only those headings list. Could use

    Requirements

    for required, and

    Qualifications

    for preferred? But Qualifications might be similar. However we need to avoid filler. Let's think. We have: - Required Knowledge, Skills And Abilities: Bachelor's degree, 7 years experience, computer proficiency, communication skills, ability to work under pressure, time management, compliance, work ethic, confidence, feedback, inspire/motivate, team experience, problem solving, continuous improvement. - Preferred Knowledge, Skills And Abilities: Knowledge of ViewPoint software, Valid Driver's License, ability to maintain satisfactory MVR, adhere to KA Motor Vehicle Policy, Travel 25-75%. We could make a section "Requirements" for required, and another "Qualifications" for preferred (or skills). But we need to avoid duplication. The instruction says prefer a few substantive sections over many thin ones. Having both Requirements and Qualifications might be okay if each has substantive content. We also have "Physical Demands". Could be part of Requirements? But we could make a separate section "Requirements" includes physical demands? However physical demands is not a skill/knowledge but a demand. Could be part of Requirements. But we might create a section "Requirements" that includes required knowledge, skills, abilities, and physical demands. That would be substantive. Alternatively, we could have "Requirements" for required knowledge/skills, "Qualifications" for preferred, and "Physical Demands" maybe not needed as separate heading because not in list. But we could incorporate physical demands into Requirements. We also have "About the role": could include core purpose, core values, company description, summary. That seems substantive. Thus sections: - About the role (core purpose, values, company, summary) - Responsibilities (essential duties) - Requirements (required knowledge/skills/abilities + physical demands) - Qualifications (preferred knowledge/skills/abilities) - Benefits - Pay We should not include Schedule. Now we need to format. For each section:

    About the role

    ...

    maybe include multiple paragraphs? Could combine core purpose, values, company, summary into one paragraph or multiple

    . The instruction: use

    for prose. So we can have multiple

    elements. We need to preserve all substantive info, not invent or summarize away detail. So we need to include the exact sentences? We can paraphrase? It says preserve ALL substantive information; do NOT invent or summarize away detail. That suggests we should keep the information but we can rephrase? Safer to keep the original wording but maybe break into bullet lists where appropriate. For About the role: we have Core Purpose, Core Values list, Our Company description, Summary. We'll include them as paragraphs. We need to avoid boilerplate like "Core Purpose: Building enduring relationships and strong communities". Keep that sentence. Core Values: list each value with description. Could be

    • Integrity – Do the right thing…always be respectful, honest and fair
    etc. Our Company: paragraph. Summary: paragraph. Now Responsibilities: we have Essential Duties and Responsibilities list (many items). We'll output as
    • each duty. We need to ensure we don't include duplicated lines. The list includes some repeated sentences like "Reviews project proposal, plans and specifications..." appears twice (once in Essential Duties and again in "Assists in proposal writing..."). Actually there is duplication: "Reviews project proposal, plans and specifications to determine time frame, funding limitations, procedures for accomplishing project, staffing requirements and allotment of available resources to various phases of project." appears both in Essential Duties and later in "Assists in proposal writing...". We need to preserve all substantive info but remove duplicated lines. So we should include each unique duty only once. We need to deduplicate. Let's extract the duties from the text: Essential Duties and Responsibilities include the following. Other duties may be assigned. List: 1. Reviews project proposal, plans and specifications to determine time frame, funding limitations, procedures for accomplishing project, staffing requirements and allotment of available resources to various phases of project. 2. Establishes work plan, scheduling and staffing for each phase of project and arrangement for recruitment or assignment of project personnel as needed. 3. Reads and understands drawings and specifications. 4. Establishes a growing network of business associates, subcontractors and related vendors. 5. Confers with team leader or project staff to outline work plans, assign duties, responsibilities and scope of authority. 6. Coordinates activities with project staff to ensure project progress within prescribed budget and provides technical advice to resolve problems. 7. Negotiates with the Owner and subcontractors on projects in order to maintain an efficient and well-run project. 8. Works with actual billings on projects and works with Finance to ensure a smooth process on all projects. 9. Prepares project reports for management, clients and others and reviews status reports prepared by project personnel and modifies schedules or plans as required. 10. Coordinates project activities with activities of governmental regulatory or other governmental agencies. 11. Works with Project Superintendents, Project Assistants, clients and subcontractors. 12. Supervises Project Assistant assigned to projects including planning, assigning work, providing feedback and appraising performance. 13. Assists in proposal writing, reviews project proposal, drawings and plans to determine time frame, funding limitations, procedures for accomplishing project, staffing requirements and allotment of available resources to various phases of project. (duplicate of #1) 14. Assist in the mentoring and development of internal talent 15. Establishes and maintains relationships with Owners and other project partners 16. Assists in directing strategic planning and provides leadership role in business development and client relations. 17. Assist the Safety Department in an effort to enforce the corporate safety and health policies and procedures 18. Performs other duties as assigned. We need to remove duplicate #13 (same as #1). Also #14 "Assist in the mentoring and development of internal talent" maybe should be "Assists". Keep. Now Required Knowledge, Skills And Abilities list: - Bachelor’s degree from four year college/university or equivalent. - Minimum of 7 years related work experience. - Demonstrated computer proficiency (MS Office – Word, Excel and Outlook) and knowledge of project management software - Excellent verbal and written communication skills, including ability to effectively communicate with internal and external customers - Ability to work under pressure and meet deadlines, while maintaining a positive attitude and providing exemplary customer service - Ability to use time productively, maximize efficiency and meet challenging work goals - Ability to maintain compliance with all company policies and procedures - Ability to possess and maintain exceptional work ethic as well as uphold company values and demand the highest standard of conduct from self and others - Exhibits confidence in self and others - Accepts feedback from others as well as provides feedback - Inspires and motivates self and team to perform well - Contributes to building a positive team experience - Identifies and resolves problems in a timely manner, while looking for way to continuously improve. We could turn each into
    • . Preferred Knowledge, Skills And Abilities: - Knowledge of ViewPoint software - Other Valid Driver's License, ability to maintain a satisfactory Motor Vehicle Record, and ability to adhere to the KA Motor Vehicle Policy. - Travel 25-75%; depending on job We need to keep "Other Valid Driver's License" maybe it's a typo; keep as is. Physical Demands: - Ability To Clearly communicate information (both written and verbal) to colleagues and key stakeholders - Stand and/or sit in a stationary position for extended periods of time; 50%+ - Use a computer/laptop/iPad in open office environment with natural and/or florescent lighting - Navigate between office building floors, and on occasion, attend off-site meetings - Lift up to 25 lbs. unassisted We could incorporate physical demands into Requirements section as a sublist maybe under a heading? But we only have headings list; we could add a

      Physical Demands

      but not in allowed list? The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list? 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 not create Physical Dem