Project Manager I

We need to output HTML fragment with sections: About the role? Actually we have description: Corporate Summary (company info) maybe not needed? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. 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. We need to decide which sections to include based on content. We have: - Corporate Summary (company description) maybe could be "About the role"? Actually "About the role" is generic; but we have corporate summary about company. Could be "About the Company". But instruction only lists example headings; we can use other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are typical but not exclusive? Probably we should stick to those headings where applicable. We have content: Position Summary (what the role does) could be "About the role". Responsibilities: we have Project Coordination & Execution, Communication & Reporting, Process Improvement, Essential Responsibilities For All Beacon EmbeddedWorks Employees. Could combine into Responsibilities. Requirements: Minimum Qualifications, Preferred Qualifications. Skills: maybe not separate; could be part of Requirements. Benefits: we have "Multiple options for medical and dental coverages", "Paid life insurance and disability coverage", "401k with match", "128 hours of time off per year to start", "Paid holidays". Also "Working for a company that helps save lives with some of our products". Also "Top 200 Workplace". So we have benefits. Pay: Starting Salary Information: $68,000+. Schedule: Position Type/Expected Hours of Work: full-time, Monday-Friday 8am-5pm, some flexibility, may need >40 hours. Thus we have content for About the role (Position Summary), Responsibilities, Requirements (Minimum Qualifications, Preferred Qualifications), Benefits, Pay, Schedule. We should not include sections with filler. All have real content. We need to output only HTML fragment, no /, no markdown fences. We need to use

  for each section heading. Inside sections, use

  for prose,

  • for lists. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: EEO, etc. Also remove "Work Authorization", "Physical Demands", "Work Environment"? Those are substantive? They are part of job description but not in the list of headings. Should we include them? The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't restrict to only those example headings; we could add other headings like "Physical Demands", "Work Environment", "Work Authorization". But the instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It may imply we should use those headings where applicable, but we could also add others if needed. However, to be safe, we could incorporate those details into existing sections: Physical Demands could go under Responsibilities? Not really. Work Environment could go under About the role? Might be odd. Better to create sections for them if they have content. But the instruction didn't forbid other headings; just gave examples. However, they said "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests those are the expected headings; but not strictly limited. However, they also say "Prefer a few substantive sections over many thin ones." So we should avoid creating many thin sections. Physical Demands and Work Environment are relatively short; maybe we can incorporate them into a "Working Conditions" section? Not in list. Could fold into About the role or Responsibilities? Might be okay to add a "Working Conditions" heading but not in examples. Safer to follow examples and not create extra sections; we can incorporate those details into existing sections like Responsibilities (maybe under a sublist). But we need to preserve all substantive information; we can include them as

    paragraphs within Responsibilities or a new section like "Additional Information". However, that might be considered a thin section. Given the instruction to prefer few substantive sections, we could create sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Within Responsibilities we can include the bullet lists of duties (Project Coordination & Execution, Communication & Reporting, Process Improvement, Essential Responsibilities). Also we can include Physical Demands and Work Environment as additional bullet points under Responsibilities or as a separate subsection? Might be okay to add a "Working Conditions" subsection but not a top-level heading. Better: Keep top-level sections as per examples; include all info within them. Thus:

    About the role

    Position Summary: The Project Manager I coordinates internal Beacon execution projects between Design Engineering, Manufacturing Engineering, Supply Chain, and Operations. This role keeps internal initiatives organized, on schedule, and moving forward by facilitating communication and tracking progress across cross-functional teams. This is an entry-level position: candidates fresh out of school are welcome to apply, and candidates with up to two (2) years of relevant experience are ideal. The Project Manager I reports to the VP of Operations and offers a strong foundation for growth into larger-scope program management roles over time.

    Location: Eden Prairie, MN office.

    Corporate Summary: Beacon EmbeddedWorks is a full-service provider of embedded solutions... (the corporate summary paragraph). We need to include that content. Should we put it under About the role? Might be okay as "About the company". But we can include as a paragraph. But we need to preserve all substantive information; corporate summary is substantive. We'll include it. Then Responsibilities: we need to list duties. We'll create

    with items for each major duty: maybe break down each bullet. We have: Project Coordination & Execution: - Coordinate internal Beacon execution projects between Design Engineering, Manufacturing Engineering, Supply Chain, and Operations - Support the development and maintenance of project plans, schedules, and milestones for assigned internal initiatives - Track project tasks, deliverables, and deadlines, flagging risks and delays to appropriate stakeholders - Schedule and facilitate cross-functional project meetings; prepare agendas and publish meeting notes and action items - Monitor task completion status and follow up with team members to keep projects on track - Maintain accurate and up-to-date project documentation according to established requirements - Assist in identifying resource needs and constraints across engineering, manufacturing, and supply chain functions Communication & Reporting: - Serve as a point of contact between Design Engineering, Manufacturing Engineering, Supply Chain, and Operations for assigned projects - Prepare and distribute regular project status updates, including progress, risks, and action items - Effectively escalate issues in a timely manner to the VP of Operations or relevant stakeholders - Support the development of return-to-green plans when projects fall behind commitments Process Improvement: - Identify opportunities to improve internal project coordination processes and workflows - Support the implementation of process improvements identified by senior team members - Participate in continuous improvement initiatives related to project execution Essential Responsibilities For All Beacon EmbeddedWorks Employees: - Support and demonstrate our core values - Interact positively and professionally with all employees - Perform work safely and adhere to all safety requirements - Maintain reliable attendance - Perform other duties as assigned Physical Demands: - While performing the duties of this job, the employee is regularly required to use hands and fingers to handle, feel, or operate objects, tools or controls, and reach with hands and arms - The employee may occasionally lift and/or move up to ten pounds Work Environment: - This position will be on site at our Eden Prairie, MN location - The noise level in the work environment is usually quiet, that of an office environment. However, on some instances this job may require work in areas where eye protection is necessary - Travel may be required, infrequently We could include Physical Demands and Work Environment as part of Responsibilities as additional bullet groups, or as separate subheadings inside Responsibilities using

    ? But we only allowed

    for section headings. Could we use

    inside? Not specified; but we can just include them as

    paragraphs. Better: Keep Responsibilities as a

    with all duty items; we can add sub-items as nested
    maybe. But we need to preserve all detail; we can just list each bullet as a
    • . That will be many items but okay. Alternatively, we could group them under headings using inside
    • . That's acceptable. Thus Responsibilities
      • ...
      etc. Now Requirements: Minimum Qualifications and Preferred Qualifications. We can make a
      for Minimum Qualifications and another for Preferred Qualifications. Minimum Qualifications: - Bachelor’s degree in engineering, business, supply chain, or a related field, or equivalent combination of education and experience - Entry-level candidates are welcome to apply; up to two (2) years of project coordination or project management experience is ideal, preferably in a manufacturing or engineering environment - Strong organizational skills with the ability to manage multiple tasks and priorities simultaneously - Clear written and verbal communication skills, with comfort presenting status updates to cross-functional teams - Proficiency with Microsoft Office (Excel, PowerPoint, Word) and familiarity with project management tools (e.g. MS Project, Smartsheet, or similar) - Ability to work collaboratively across Design Engineering, Manufacturing Engineering, Supply Chain, and Operations Preferred Qualifications: - Coursework, internship, or co-op experience in project management, engineering, or manufacturing - Interest in pursuing a project management certification (CAPM, PMP, Six Sigma, etc.) - Familiarity with Lean manufacturing principles such as 5S and Kaizen - Exposure to an Enterprise Resource Planning (ERP) system such as Intuitive, Empower, OpenAir, or similar We could also include "Skills" section but we already have skills in Requirements; maybe we can omit separate Skills. Benefits: list: - Multiple options for medical and dental coverages - Paid life insurance and disability coverage - 401k with match - 128 hours of time off per year to start - Paid holidays - Working for a company that helps save lives with some of our products - Top 200 Workplace as voted by employees Pay: Starting Salary Information: $68,000+. Schedule: Position Type/Expected Hours of Work: This is a full-time position; Typical day and hours of work are Monday through Friday, 8:00am to 5:00pm, but does allow for some flexibility; It may be necessary to work more than 40 hours per week at times to produce the required results. We also have Work Authorization: "The incumbent must meet the definition of “US Person” under ITAR/EAR regulations". This is substantive; we need to preserve it. Where to put? Could be under Requirements as a bullet?