Application Manager

We need to output HTML fragment with 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. Use

for headings. Use

• for lists. Use

  for prose. Remove boilerplate. We need to parse the posting. First part: "ODU-USA | Camarillo or San Diego, CA (On-Site) Turn Customer Opportunities into Market-Ready Solutions ..." That's description. We need sections: About the role (maybe the initial description). Responsibilities (list of duties). Requirements (maybe required qualifications). Qualifications (maybe preferred). Skills (maybe abilities). Benefits (benefits). Pay (salary range). Schedule (maybe not present). The posting does not mention schedule specifics, so we should not include Schedule section. We need to preserve all substantive info, not invent. Let's extract content. First paragraph: "ODU is a privately held global technology manufacturer headquartered in Germany, with operations in more than 50 countries worldwide. Our products support mission-critical applications across medical technology, industrial automation, aerospace, defense, and communications industries. As ODU continues to grow across North America, we are seeking a customer-focused professional to lead custom connector and cable assembly opportunities from concept through production launch. This is a highly visible role that combines customer engagement, project leadership, technical coordination, and commercial strategy. You'll work closely with customers, Regional Sales Managers, Engineering, Manufacturing, Supply Chain, and Quality teams to develop innovative solutions, drive successful project execution, and deliver an exceptional customer experience. From understanding application requirements and coordinating quotations to leading cross-functional project teams, you'll play a key role in helping customers bring new products to market. If you enjoy building relationships, solving complex challenges, coordinating teams, and turning opportunities into successful business outcomes, we'd love to hear from you." That's about the role. Then there is a heading "Project Management & Execution" with bullet list. Then "Quotation & Commercial Coordination" bullet list. Then "Process Improvement" bullet list. These are responsibilities. Then "What We're Looking For" with "Required Qualifications" bullet list and "Preferred Qualifications" bullet list. Then "About ODU" paragraph. Then "Why Join ODU?" paragraph. Then "Compensation" with salary range and benefits. Thus we need sections: - About the role: combine initial description and maybe About ODU? Actually "About the role" could be the initial description. "About ODU" could be separate but not required. We can include "About the role" as the initial description plus maybe the "About ODU" as part of role? But we need to avoid duplication. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have those headings. We need to decide content for each. Probably: - About the role: the initial paragraph(s) describing role and mission. - Responsibilities: combine the three bullet groups (Project Management & Execution, Quotation & Commercial Coordination, Process Improvement) into a single list? Or separate subheadings? The instruction says use

  for section headings, and

  • for any list of duties/requirements/benefits. So we can have one Responsibilities section with a
    containing all duties. - Requirements: maybe the "Required Qualifications" list. - Qualifications: maybe the "Preferred Qualifications" list. - Skills: maybe the abilities listed in required qualifications (strong organizational, communication, etc.) but we could also put them under Skills. However we already have Required Qualifications and Preferred Qualifications; we could treat Required as Requirements, Preferred as Qualifications, and Skills maybe from the bullet list of abilities (like ability to translate technical and business requirements, proven ability to work within cross-functional teams). But we could also combine. Better to follow the example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Thus we need to map: - About the role: initial description. - Responsibilities: duties from the three sections. - Requirements: Required Qualifications bullet list. - Qualifications: Preferred Qualifications bullet list. - Skills: maybe the abilities like "Strong organizational, communication, and customer relationship skills.", "Ability to translate technical and business requirements into actionable project plans.", "Proven ability to work effectively within cross-functional teams in a fast-paced environment." These are already in Required Qualifications but we could still list them under Skills. However we must not duplicate content? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but better to avoid duplication. We could put those abilities under Skills and keep Required Qualifications as just education/experience. But the Required Qualifications bullet list includes those abilities as separate bullets. Let's examine Required Qualifications bullets: - Bachelor's degree in Engineering, Business, Project Management, or a related field preferred. - Experience in project management, technical sales, application engineering, operations, manufacturing, or a similar cross-functional role. - Demonstrated ability to manage multiple projects, priorities, and stakeholders simultaneously. - Strong organizational, communication, and customer relationship skills. - Ability to translate technical and business requirements into actionable project plans. - Proven ability to work effectively within cross-functional teams in a fast-paced environment. Thus we could split: Requirements: education and experience (first two bullets). Qualifications: maybe the rest? But the instruction separate Requirements and Qualifications. Could treat Requirements as the education/experience, Qualifications as the abilities/skills. But we also have a separate Skills heading. Might be redundant. Better to follow typical pattern: Requirements = required qualifications (including education, experience, abilities). Qualifications = preferred qualifications. Skills maybe not needed if we already covered abilities. But we need to include a Skills section only if there is real specific content. We could extract skills from the posting: "Strong organizational, communication, and customer relationship skills.", "Ability to translate technical and business requirements into actionable project plans.", "Proven ability to work effectively within cross-functional teams in a fast-paced environment." Those are skills. So we can put them under Skills. Thus: - Requirements: education and experience bullets. - Qualifications: preferred qualifications bullets. - Skills: the three ability bullets. Check if any other skills: maybe "Experience coordinating projects across multiple departments and global teams." That's in preferred qualifications. Already there. Now Benefits: from Compensation paragraph: "In addition to base pay, ODU offers a comprehensive benefits package that includes medical, dental, vision, 401(k), paid time off, and other employee programs." Pay: salary range: "$95,000 to $115,000 annually, depending on experience, skills, education, and other job-related factors." Schedule: not present, so omit. Now About the role: we need to include the initial description plus maybe the "About ODU" and "Why Join ODU?"? Those are about company, not role. Could be included under About the role? But the heading "About the role" is for role description. The "About ODU" and "Why Join ODU?" are more about company culture. Could be placed under About the role? Might be okay but could be considered not role-specific. However we have no other heading for company info. The instruction says include a section ONLY when the posting has real, specific content for it. It doesn't forbid including company info under About the role. But we could also create a separate section like "About ODU" but not in the list of allowed headings. The allowed headings are limited to those examples; we could still add other headings? The instruction says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive list. But safer to stick to those. We could put company info under About the role as part of role description. Thus About the role content: combine the initial paragraphs describing role, plus maybe the "About ODU" and "Why Join ODU?" paragraphs. But that may be too much. However we need to preserve ALL substantive information. If we omit About ODU and Why Join ODU, we lose substantive info about company. So we should include them somewhere. Could put them under About the role as well. Thus About the role will contain: - First paragraph(s) about role. - Then "About ODU" paragraph. - Then "Why Join ODU?" paragraph. We need to ensure we don't repeat content. Now we need to format. Let's craft HTML. We'll start with

    About the role

    then

    ...

    containing multiple sentences; we can combine into one

    or multiple

    . Use

    for prose. We'll need to escape any HTML special characters? Not needed. Now Responsibilities:

    Responsibilities

    then
    • ... each duty. We need to list all duties from the three sections. Let's extract duties: Project Management & Execution: - Lead custom application opportunities from initial concept through production launch. - Coordinate activities across Engineering, Manufacturing, Supply Chain, Quality, and Sales teams. - Develop and maintain project plans, timelines, milestones, and deliverables. - Monitor project progress, identify risks, and proactively drive issue resolution. - Facilitate project reviews, status updates, and stakeholder communications. - Manage project scope changes and ensure alignment on customer expectations and business commitments. - Coordinate with global ODU teams as required to support project execution and successful outcomes. Quotation & Commercial Coordination: - Lead the quotation process for custom connector and cable assembly opportunities. - Coordinate cross-functional input to develop accurate, competitive, and profitable proposals. - Review project costs, assumptions, timelines, risks, and margin expectations. - Maintain clear documentation of customer requirements, project commitments, and commercial assumptions. - Support opportunity planning and successful transition into production. Process Improvement: - Identify opportunities to improve project visibility, communication, and cross-functional collaboration. - Support implementation of tools, systems, and processes that improve project execution and customer experience. - Contribute to best practices for managing custom opportunities from intake through production launch. Now Requirements (education/experience): - Bachelor's degree in Engineering, Business, Project Management, or a related field preferred. - Experience in project management, technical sales, application engineering, operations, manufacturing, or a similar cross-functional role. Qualifications (preferred): - Experience in manufacturing, industrial, electronics, engineered products, connectors, or cable assemblies. - Experience managing customer-facing projects involving custom solutions or new product introductions. - Exposure to quotations, pricing, cost analysis, or commercial project evaluation. - Experience coordinating projects across multiple departments and global teams. - Project Management Professional (PMP) certification or similar project management training is a plus. Skills: - Demonstrated ability to manage multiple projects, priorities, and stakeholders simultaneously. - Strong organizational, communication, and customer relationship skills. - Ability to translate technical and business requirements into actionable project plans. - Proven ability to work effectively within cross-functional teams in a fast-paced environment. Now Benefits: - medical, dental, vision, 401(k), paid time off, and other employee programs. We need to phrase as list? Could be
      • Medical
      etc. But we can just put a

      with list. The instruction: Use

      • for any list of duties/requirements/benefits. So benefits list should be
        • . Thus Benefits:
          • Medical
          • Dental
          • Vision
          • 401(k)
          • Paid time off
          • Other employee programs
          . Pay: we can put as

          The anticipated salary range for this California-based position is $95,000 to $115,000 annually, depending on experience, skills, education, and other job-related factors.

          Now About the